To PRD

Synthesize the current conversation and codebase understanding into a PRD. I do NOT interview the user — just synthesize what I already know.

Assumes your repo has a CONTEXT.md (domain glossary) and docs/adr/ (decisions recorded). If not, run /setup-mateonunez-skills first. The issue tracker and triage label vocabulary come from setup.

Process

1. Explore

Understand the current state of the codebase if not already familiar. Use domain glossary vocabulary throughout the PRD and respect ADRs in the touched area.

2. Sketch modules

Identify the major modules you'll need to build or modify. Look for opportunities to extract deep modules (high functionality behind simple, testable interfaces, rarely changing).

Check with the user:

• Do these modules match your expectations?
• Which modules should have tests written for them?