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/, if grill-me wrote one for this feature. Otherwise use the conversation.
  • Business docs. Read docs/business/user-story.md, sprint-breakdown.md, and the per-sprint files under acceptance-criteria-breakdown/. An older project may keep its stories and criteria in other files, for example docs/USER_STORY.md and docs/ACCEPTANCE_CRITERIA.md. Note the highest US and AC numbers, and how the project groups its work.
  • Glossary. Read docs/GLOSSARY.md if it exists, and use its terms.
  • Specs. Read the index of docs/technical-specs/ and of docs/api-specs/: _index.md, or an older name such as 0.technical-index.md.
  • Issue conventions. Read .github/ISSUE_TEMPLATE/ (including config.yml), and list the labels and milestones with gh label list and gh 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, and acceptance-criteria-breakdown/ with the first sprint file. Start at US-01. Features that already shipped get no stories.
  • No code yet. This is a new project. Stop and point the user at product-discovery.
Installs
31
GitHub Stars
9
First Seen
Jul 27, 2026