Back to Prompts
generationRecommended
Build Brief Generator
Generate a complete Build Brief from your rough idea, persona, and problem observations.
Prompt Template
I'm building a prototype for a product idea. Help me create a Build Brief — a 2–5 page structured requirements document optimized for an AI coding agent (Cursor, Claude Code) to build a working prototype. Here's what I know so far: **My rough idea:** [Describe your idea in 2–3 sentences. Be as specific or vague as you are right now — that's fine.] **Who I think this is for:** [Describe the person. What's their role? What do they do day-to-day? If you don't know yet, say so.] **The pain I've observed or heard about:** [What specific frustration, cost, or workaround have you seen? Include quotes from conversations if you have them.] **What I think the core feature is:** [What's the one thing this tool does? If you're not sure, describe the outcome you want for the user.] --- Structure the Build Brief using these four sections: ### 1. Persona Create an operator profile (not a marketing avatar). Include: - Role and daily context - Technical comfort level - Current workflow and tools - Success definition: "They open the app and feel ___ within 5 seconds" ### 2. Problem Structure as a table with columns: Problem Area | Impact | Current Workaround. Then write 2–3 Jobs To Be Done in this format: Job ID | Job Statement | Trigger Situation | Desired Outcome. Every problem must pass the "show me the pain" test — quantified or described as a specific frustrating moment. ### 3. Product - List 3–5 features maximum, each tied to a specific problem from Section 2 - Write user stories in "As a [persona], I want [action], so that [value]" format - Include concrete acceptance criteria for each story (bullet points the AI can check against) - Mark each feature P0 (must work in prototype), P1 (visible but not fully built), or P2 (explicitly out of scope) - Include a "Non-Goals" section listing what we are NOT building (auth, mobile app, real integrations, etc.) ### 4. Proposition Write draft landing page copy: - One-sentence value proposition using: "For [persona] who [problem], [product] is a [category] that [benefit]. Unlike [alternative], we [differentiator]." - Headline (10 words or fewer) - Subheadline (one sentence) - 3 key benefits (one line each) - A social proof hook (a quote a future user might say) - CTA text --- Additional rules: - Keep the total Build Brief under 5 pages - Use tables and structured formatting — this document will be read by an AI, not presented in a meeting - Include guidance for realistic mock data (names, amounts, dates that make the demo feel real — no Lorem Ipsum) - Write it so that a developer or AI agent with NO other context could build the prototype from this document alone - Flag anywhere my input is too vague and ask me to clarify before finalizing
Variables to customize:
Describe your idea in 2–3 sentencesDescribe the personWhat specific frustration, cost, or workaround have you seenWhat's the one thing this tool does
Tags
build-briefgeneratorprototypingrequirementsdocumentation