skills/hackathon-map/references/content/learning/prd.md

# Write the product requirements

PRD stands for **Product Requirements Document**. It's non-technical but really specific: it pins down exactly what the project should do and how it should feel to use, before anyone thinks about code structure.

It's the second of four documents the guided build produces, each with its own job:

- **Scope** helps you come up with the idea and settle on something that fits your time frame and resources.
- **PRD** (this one) is non-technical but really specific — what the product does and how it feels.
- **Spec** is the technical plan — how it will actually be built.
- **Checklist** is instructions for the agent — the sequenced tasks Codex works through to build it.

Codex will read the scope notes and help turn them into user-facing requirements.

Output: `docs/hackathon-build/prd.md`. Next: the spec — say you're ready, or type `$build-spec`.
<!-- Copy maintainers: edit this page copy in content/learning/prd.md. -->