Value Proposition Capstone — Claude Code Guide

A value proposition is not a slogan

A value proposition connects a specific user, their situation, an inconvenient alternative, and an outcome that can be checked. “AI helps everyone work better” sets neither a boundary nor a way to evaluate it.

For a capstone, separate promise and evidence: the promise describes expected benefit, while the evidence plan shows which observations could confirm or disprove it. Until actual verification, such statements have the status of assumptions or Unknown.

Value proposition components

• problem: what repeated loss of time, quality, or confidence occurs;
• audience: who experiences the problem and decides whether to use it;
• alternative: how the user solves it now, including manual work;
• promised outcome: what should change in behavior or result;
• proof plan: what signal can be observed and under which constraints;
• limits: which claims cannot be made without user validation or production evidence.

Checking the formulation

# VALUE_PROPOSITION.md
User: reviewer of a bounded repository change
Problem: evidence is scattered across notes and command output
Alternative: manual search through the diff and task thread
Promise: produce one reviewable evidence outline before implementation
Proof signal: reviewer can locate scope, checks and Unknowns in one pass
Status: documented example; user validation and outcome are Unknown.