1.1.3 - The One-Line Promise That Keeps Your Build Honest Throughout

user.md and problem.md describe the gap between where the user is and where they want to be. promise.md is the shape of what fills it: one promised outcome to one user with one explicit boundary on what this is deliberately NOT trying to do.

One-line promise

Is your one-line promise clear enough to keep decisions honest?

The call

Write the promise first. Otherwise AI generates options that sound right but pull the product in different directions.

Explainer

A one-line promise is not a slogan. It is the shortest honest statement of who this is for, what outcome it creates and where the boundary sits. Until you can say the promise without piling on extra claims, the product direction is too soft. AI can help produce options, but it cannot decide what should and should not be promised.

Make the one-line promise concrete

Compare the broad version with a version you can actually test.

• Too vague: This helps people get better results from AI search.
• Concrete enough to test: This helps a content creator find gaps in what they have already published so they can decide what to write next, without giving generic content advice.

The second version lets two people position the product the same way from it.

Check the one-line promise

• Pass: You can say who it is for, what result it creates and what it is deliberately not trying to do.
• Fail: If the sentence still works after swapping in words like better, smarter or easier, the promise is still vague.

Do not move into messaging, scope or build work until this passes.

What you'll walk away with

In the members-only section below we put this into practice. You'll come out with a one-line promise clear enough that every later decision flows from it. Positioning, scope, success criteria, what you cut and the prompts you write to AI all inherit that clarity.

How it fits together

This is how the work is done in practice on the Cloudflare Workers stack with AI-assisted coding tools. The thoughts and ideas apply equally on any other platform.

The project is a monorepo so the one-line promise (alongside the rest of the framework files) lives in one shared knowledge-base/ folder that every app, every package and every AI prompt reads from. The three products in the vibe2value build-in-public stack (subCancel, ghostMarketingFlow and flowRun) each carry this layout, so look at any of them to see the structure in practice.

If you sign up, this idea continues with how it all fits together, a worked example, how to use it with AI, how to evaluate it on a real change, the risks worth naming and how to mitigate them, the key takeaways and a copy-paste AI prompt you can drop straight into your next chat. Examples are shown on the Cloudflare Workers stack with AI-assisted coding tools; the ideas apply equally on any other platform.