to-prd
Installation
SKILL.md
To PRD
The mid-project entry to the pipeline. product-discovery and us-ac-formatter
start a project. This skill adds to one that already runs, in the same format,
so docs/business/ stays the single source of truth.
1. Read the input and the project
- Input. Take the latest decision log in
docs/decisions/, ifgrill-mewrote one for this feature. Otherwise use the conversation. - Business docs. Read
docs/business/user-story.md,sprint-breakdown.md, and the per-sprint files underacceptance-criteria-breakdown/. An older project may keep its stories and criteria in other files, for exampledocs/USER_STORY.mdanddocs/ACCEPTANCE_CRITERIA.md. Note the highest US and AC numbers, and how the project groups its work. - Glossary. Read
docs/GLOSSARY.mdif it exists, and use its terms. - Specs. Read the index of
docs/technical-specs/and ofdocs/api-specs/:_index.md, or an older name such as0.technical-index.md. - Issue conventions. Read
.github/ISSUE_TEMPLATE/(includingconfig.yml), and list the labels and milestones withgh label listandgh api repos/{owner}/{repo}/milestones. Step 6 follows them.
If docs/business/ does not exist, pick the case that fits:
- Older business docs exist. They are the source of truth. Continue their US and AC numbering, and write in their layout and language. Ask once whether to migrate them into
docs/business/instead. Never start a second set next to them. - No business docs in any form, but code exists (adopt mode). Create the skeleton in
us-ac-formatter's file targets:user-story.md,sprint-breakdown.md, andacceptance-criteria-breakdown/with the first sprint file. Start atUS-01. Features that already shipped get no stories. - No code yet. This is a new project. Stop and point the user at
product-discovery.