> ## Content Index > Fetch the complete content index at: https://vibe2value.com/llms.txt > Use this file to discover other available public pages before exploring further. # 1.1.3 - The One-Line Promise That Keeps Your Build Honest Throughout - URL: https://vibe2value.com/the-one-line-promise-that-keeps-you-honest/ - Published: 2026-01-06T11:26:03.000Z - Updated: 2026-09-07T05:58:05.000Z - Description: Write the one-line promise: say who it is for, what result it creates and what it is deliberately not trying to do. - Author: vibe2value - Tags: shape, problem, promise, alignment, making decisions, shape+build+launch+run+close `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. ## Sharpen the one-line promise with AI This is a Shape idea, so the AI move is to **Sharpen** the one-line promise: run your draft through the prompt below until two people would make the same decision from it. Build and Launch ideas have their own AI moves, building and running the code. **New here? Let your AI do this with you.** Paste your problem into [Guide me](https://vibe2value.com/guide-me/) and it builds a prompt that walks you through this in ChatGPT or Claude. You do not need to know how to prompt. Prefer to drive the AI yourself? Give ChatGPT or Claude this page and ask it to help. For skill.txt, the Claude Code plugin and other ways in, see [how to use vibe2value](https://vibe2value.com/how-to-use/). Or copy this prompt into AI chat, replace the bracketed lines with your real one-line promise and keep the instruction exactly as visible here. It helps you put your promise.md together by refining your three lines until two people would make the same product decision from them. ``` You are checking whether the one-line promise is clear enough before you decide what to build. Constraint: The one-line promise must be specific enough that two people would position the product the same way from it. Example of the standard: Vague: "This helps people publish more." Sharp: "This helps someone with more material than published work: email it a line when the thought lands and get back what is worth writing. It never writes the post, schedules it or publishes it." The sharp version is specific enough that two people would position the product the same way. The vague one is not. Context: User: [name one real user] Promised outcome: [name one promised outcome] Boundary: [name one thing this does not promise] Task: Decide whether this one-line promise is clear enough to guide the product. If it already is, say so. If it is vague, rewrite it so you can name one user, one promised outcome and one clear boundary on what is not promised. Check: - Does it name one real user instead of a broad audience? - Is the promised outcome specific enough that two people would describe the same value from it? - Is the boundary clear enough to stop the promise from expanding? Return: - Verdict: clear, or needs work - The corrected one-line promise, the three lines, or the original if already clear - What was vague, and the one change that fixed it ``` Copy this into AI chat. Replace the bracketed parts. Keep the rest unchanged. AI will likely suggest refinements based on what you enter. Use those to sharpen your thinking, not replace it. A promise that has to hold throughout is not something you get sharp once. It has to survive every future session, which makes it project context rather than a conversation. That is [Project memory and rules](https://vibe2value.com/project-memory-and-rules/), one of the ways to set AI up to help. ## The same idea on a recipe card Think of the one line at the top of a recipe that tells you what you will end up with. "A warm, filling bowl for two on a cold night" is a promise you can hold the cook to. A card that promises healthy and quick and fancy and cheap and impressive all at once promises everything and delivers nothing in particular. Your one-line promise is that top line. Say who it feeds, the one outcome it creates and where it stops, then keep it to a single honest line. Every later choice now has something to answer to, the same way a cook keeps checking the dish against "warm and filling for two". The recipe card is just a simple example, using everyday cooking ideas everyone understands, to make the concept clear. See [the recipe card](https://vibe2value.com/project/recipecard/). ## What it really means 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 publish more. - **Concrete enough to test:** This helps someone with more material than published work: email it a line when the thought lands and get back what is worth writing. It never writes the post, schedules it or publishes it. The second version lets two people position the product the same way from it. Both versions come from **consideredContent**, the one project carried through all 35 ideas. [See the project](https://vibe2value.com/project/considered-content/). one line, three partsFORan organic paid userI PROMISEto find their content gapsBUT NOTgeneric advice A one-line promise keeps you honest because it is one line: who it is for, the single outcome you promise, and the boundary on what it deliberately will not do. If it needs a paragraph, it is not a promise yet. ## 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 You put this into practice with the prompt above. 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. ## Write it down Your `promise.md` is a real file in your project. The AI forgets everything between sessions. It reads this file each time to pick up what you already decided, on this idea or another part of the build. Write it down once instead of explaining it again. `knowledge-base/framework/shape/promise.md` is just a suggested name and place for this information. The name and the location are just how we organise this type of documentation, not something you have to follow. Call the file and put it wherever suits your project. What matters is that it is written down in a format that is easily understood by both people and the AI. The `.md` ending is markdown, a plain text format often used for documents kept in a code repository like GitHub. It is just the common way people store this kind of writing alongside their code. Writing it down is how you keep good context for your AI. See [Keep the signal, not the noise](https://vibe2value.com/your-context/) for why this matters across a whole build. ## Risk and mitigation - **Risk:** Writing a vague promise that sounds inspiring but allows conflicting interpretations, which increases scope drift and rework. - **Mitigation:** Define one measurable outcome in the promise and reject changes that do not improve that outcome. ## Key takeaway Do not move forward until you can say who it is for, what result it creates and what it is deliberately not trying to do. ## How to document your one-line promise Write your one-line promise up in full so your AI has the whole picture: the answer, why you believe it, what you are optimising for, where you might be wrong and the standing instruction it should follow. Keep it in a file with your project like this. ``` # One-line promise ## Answer User: [name one real user] Promised outcome: [name one promised outcome] Boundary: [name one thing this does not promise] ## Evidence Why you believe this. Conversations, examples, tickets, your own experience. ## Decision What you are optimising for and what you are saying no to. ## Risk Where you might be wrong and what would tell you. ## AI instruction The standing note your AI reads on this project. ``` Here is one filled in so you can see what good looks like, grounded in the recipe card idea from earlier. ``` ## Answer User: Two people on a cold night Promised outcome: A warm, filling bowl Boundary: Not healthy or quick or fancy, just warm and filling ## Evidence They arrived cold and tired and asked for nothing fancy, just something hot to hold. ## Decision Optimising for warm and filling. Saying no to healthy, quick or fancy when it gets in the way of that. ## Risk I might drift into making it impressive instead of comforting. If a choice adds flair but not warmth, drop it. ## AI instruction The promise is a warm, filling bowl for two on a cold night. Judge every choice against warm and filling, not healthy, quick or fancy. ```