to-prd
To PRD
This skill takes the current conversation context and codebase understanding and produces a PRD. Synthesize what you already know — do not run a grilling interview. If module boundaries or test scope are genuinely ambiguous after exploration, ask one focused confirmation (modules to build/modify, which modules get tests); otherwise proceed.
For publishing to the issue tracker or applying triage labels, follow docs/agents/issue-tracker.md when it exists, or run /setup-matt-pocock-skills to scaffold tracker and label docs. If the user only wants an in-chat or in-repo PRD draft without publishing, skip tracker steps and say so.
Process
-
Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the PRD, and respect any ADRs in the area you're touching.
-
Sketch out the major modules you will need to build or modify to complete the implementation. Actively look for opportunities to extract deep modules (see
/codebase-design— simple, testable interface hiding substantial functionality).
If module boundaries or test scope are unclear after exploration, ask one confirmation covering both (modules to build/modify and which get tests). Otherwise proceed from context.
- Write the PRD using the template below, then publish it to the project issue tracker. Apply the
ready-for-agenttriage label - no need for additional triage.