# PRD structure

A reusable skill the "Go from rough idea to buildable PRD" recipe pulls in. Add it once and every agent on the team can use it.

Draft the PRD in the team's standard shape — Problem, Goals, Requirements, Non-goals — every time.

## Method
1. Start from the rough idea and state the Problem first: who has it, what it costs them today.
2. Write the Goals section: the outcome this PRD is meant to produce, in outcome language, not feature language.
3. Write the Requirements section: what the solution must do, ordered by priority (P0 first).
4. Write the Non-goals section before moving on — list what this PRD explicitly will not solve, and why.
5. Add any sections the team's template requires beyond these four (set on first run, then stored in memory).
6. Re-read the draft end to end and confirm each section answers its own question, not a neighboring one.

## Rules
- Non-goals is mandatory — do not proceed to Requirements until it's filled in with real content.
- Problem comes before solution; do not open with a proposed feature before the problem is stated.
- Requirements are ordered by priority, not by the order ideas occurred to the drafter.
- Keep sections in the fixed order — Problem, Goals, Requirements, Non-goals — so every PRD reads the same way.

## Output
A structured PRD document with Problem, Goals, Requirements, and Non-goals sections, plus any team-required extra sections, saved to `prds/`.