What is a Build Brief?
A Build Brief is a focused requirements document designed specifically for AI-assisted rapid prototyping. Unlike traditional PRDs that run 20-50 pages, a Build Brief is 2-5 pages and contains just enough context for an AI coding agent to build a working prototype.
Think of it as a creative brief, but for an AI developer.
Build Brief Template
Copy this template
# Build Brief: [Product Name]
**Version:** 0.1 — Prototype
**Date:** [Date]
**Author:** [Your name]
---
## 1. Persona
**Role:** [Specific title — not a demographic]
**Daily reality:** [What do they do every day? What tools?]
**Technical comfort:** [Phone-only? Desktop apps? Power user?]
**Current workflow:** [How do they handle this problem now?]
**Success definition:** They open the app and feel ___ within 5 seconds.
---
## 2. Problem
| Problem Area | Impact | Current Workaround |
|-------------|--------|-------------------|
| [Problem 1] | [Quantified impact] | [What they do today] |
| [Problem 2] | [Quantified impact] | [What they do today] |
### Jobs To Be Done
| Job ID | Job Statement | Trigger Situation | Desired Outcome |
|--------|--------------|-------------------|----------------|
| JTBD-1 | [What they're trying to accomplish] | [When the need arises] | [What 'done' looks like] |
---
## 3. Product
### Feature Overview
| Feature | Core Problem It Solves | Priority |
|---------|----------------------|----------|
| [Feature 1] | [From Problem table] | P0 |
| [Feature 2] | [From Problem table] | P0 |
| [Feature 3] | [From Problem table] | P1 |
### User Stories
| ID | User Story | Acceptance Criteria | Priority |
|----|-----------|--------------------|---------|
| US-1 | As a [persona], I want [action], so that [value] | • [Criterion 1] • [Criterion 2] | P0 |
### Non-Goals (Out of Scope)
- User authentication (use hardcoded demo user)
- [Other things you are NOT building]
### Mock Data Guidance
Use realistic sample data:
- **Names:** [Examples relevant to persona]
- **Amounts:** [Realistic ranges]
- **Dates:** [Realistic timeframes]
---
## 4. Proposition
**Value Proposition:**
For [persona] who [problem], [product] is a [category] that [benefit]. Unlike [alternative], we [differentiator].
**Headline:** [10 words or fewer]
**Subheadline:** [One sentence]
**Key Benefits:**
1. **[Benefit]** — [One sentence]
2. **[Benefit]** — [One sentence]
3. **[Benefit]** — [One sentence]
**CTA:** [Try it free / See how it works]Quick Reference Checklist
Before handing to an AI coding agent, verify:
- Persona — Specific role, technical comfort, success criteria defined
- Problem — Problems are quantified, trigger moments described
- Product — 3-5 P0 features max, each has acceptance criteria
- Proposition — Headline, 3 benefits, clear differentiator
- Non-Goals — Out of scope features explicitly listed
- Mock Data — Realistic examples described (no Lorem Ipsum)
Using Your Build Brief
With Cursor or Claude Code:
- Save as BUILD-BRIEF.md in your project root
- First prompt: 'Read BUILD-BRIEF.md. Plan the approach — don't write code yet.'
- Review the plan, then: 'Build the first screen described in the Build Brief.'
- Build one feature at a time, testing each before moving to the next
- Update the Build Brief as you learn
The Build Brief is intentionally disposable — it's a tool for learning, not a spec for production. Build the prototype, learn from it, then write the real requirements based on what you learned.