Menu
How to write PRDs for this project. Use when creating a new product requirement document, planning a feature, or adding to docs/prd/.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | writing-prds |
| description | How to write PRDs for this project. Use when creating a new product requirement document, planning a feature, or adding to docs/prd/. |
PRDs live in docs/prd/ and follow a consistent format. Each new feature gets a PRD before implementation.
PRDs capture a decision at a point in time. As the project evolves, implementations may diverge from the original PRD — that's expected. Don't update old PRDs to match current code. Instead, write a new PRD when the direction changes.
PRDs are numbered sequentially: 001-vision.md, 002-mvp.md, 003-prompt.md, etc. Use the next available number.
Follow the structure of existing PRDs (read one from docs/prd/ for reference). At minimum:
# PRD-NNN: Title
**Depends on:** [NNN-name.md](./NNN-name.md)
## Summary
One paragraph explaining what this change does.
## Motivation
Why this change is needed. What problem it solves.
## Changes
### Subsection per change area
Details of what changes, with examples and diagrams where helpful.
## Files
| File | Action |
|------|--------|
| `path/to/file.go` | Created — description |
| `path/to/other.go` | Modified — description |
## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
- [ ] `make build`, `make lint`, `make test` all pass
Update docs/prd/README.md to add a row to the index table:
| [NNN](NNN-title.md) | Title |
make build, make lint, make test as a criterionFlow workspace management — commands, state format, rendering, and PRs. Load this skill at the start of every session.
How to create pull requests for this project. Use when opening a PR on GitHub.
How to add new CLI commands to flow. Use when creating a new subcommand, adding flags, or modifying the command tree.
How to create Claude Code skills for this project. Use when adding new skills, creating SKILL.md files, or setting up skill directories.
Testing conventions and patterns for this project. Use when writing tests, creating mocks, or understanding the test infrastructure.
How to update documentation for this project. Covers updating the root README, creating and updating VHS tape recordings, running gendocs, and the make commands that tie it together.