to-prd

Topics in the source

• Process
• Problem Statement
• Solution
• User Stories
• Implementation Decisions
• Testing Decisions
• Out of Scope
• Further Notes

This skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview the user — just synthesize what you already know. The issue tracker and triage label vocabulary should have been provided to you — run /setup-matt-pocock-skills if not. 1. 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. 2. Sketch out the major modules you will need to build or modify to complete the implementation. Actively look for opportunities to extract deep modules that can be tested in isolation. A deep module (as opposed to a shallow module) is one which encapsulates a lot of functionality in a simple, testable interface which rarely changes. Check with the user that these modules match their expectations. Check with the user which modules they want tests written for. 3. Write the PRD using the template below, then publish it to the project issue tracker as a reference issue (not ready-for-agent — a PRD is a spec, not a single unit of work). Its own template demands a LONG, extensive user-story list, which wi

This is an excerpt. Refer to the complete source and its current requirements.