to-prd

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.

Process

1. Choose where to publish. The default is Local markdown — a file under .scratch/ in this repo, no remote needed. Don't probe git remote; only publish to GitHub or GitLab if the user explicitly asks.

   • Ask the user where to publish, with Local markdown pre-selected:
     • Local markdown (default) — a file at .scratch/<feature-slug>/PRD.md in this repo
     • GitHub — a GitHub issue (gh CLI), only if requested
     • GitLab — a GitLab issue (glab CLI), only if requested
   • Carry the choice into step 4. For GitHub or GitLab, follow the exact conventions and triage-label mappings in docs/agents/issue-tracker.md if it covers that backend; otherwise use the conventions in <destination-conventions> below. Run /setup-skills to configure those conventions and a triage-label vocabulary.

2. 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.

3. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.

   Check with the user that these seams match their expectations.

4. Write the PRD using the template below, then publish it to the destination you chose in step 1. Apply the ready-for-agent triage label — no need for additional triage. (For Local markdown, "applying a label" means writing a Status: ready-for-agent line near the top of the file instead.)