Step 01 of 9 20 min· intermediate
Step 1: Capture the Problem & Write a PRD
Turn your one-liner into a structured Product Requirements Document.
Recommended prompts
Use one of these to do the work in your IDE
Open the template to read it in full. Click Copy prompt to grab it (with your stack values pre-filled where they apply) — then paste into Claude Code, Cursor, or wherever you build.
When you're done
Verify these in your own work before moving on
This is a checklist for you to mentally tick off in your repo and IDE — the site doesn't track it, you do.
- PRD has all 11 sections (overview through open questions)
- Goals are measurable — numbers, not adjectives
- Out-of-scope list explicitly names what you're NOT building
- PRD lives in your repo at /docs/PRD.md and reads coherently to someone outside the team
Common pitfalls
What goes wrong at this step
- Writing aspirational goals instead of measurable ones
- Skipping the out-of-scope section — it's the cheapest scope-creep prevention you'll ever do