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 by repo docs or project instructions. If missing, inspect AGENTS.md, CONTEXT.md, docs/ADR files, and available issue tracker metadata; ask one focused setup question only if the tracker or labels remain ambiguous.

Process

Explore the repo to understand the current state of the codebase, if you haven't already. Inspect git status --short --branch, repo instructions, README.md, CONTEXT.md/CONTEXT-MAP.md, docs/adr/, relevant manifests/tests, codebase-map-understand.md, and codebase-map-understand.md when present. For broad implementation scope, consult the codebase map for module/caller/data-flow leads and verify named files. 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 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.

Write the PRD using the template below, then publish it to the project issue tracker. Apply the ready-for-agent triage label - no need for additional triage.

to-prd

Process

Problem Statement