| name | prd |
| description | Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context. |
PRD
Overview
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.
Core Workflow
Step 1 — Understand the codebase
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.
Step 2 — Sketch out
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.
Step 3 — Write the PRD.md
Run prd-end <branchName> via the Bash tool, and parse the JSON output.
Write the PRD to <prdPath>, following the template.
Step 4 — Write COMMIT_HINT.md
Write COMMIT_HINT.md to <commitHintPath>.
Load commit-hint.md for format and rules.
Derive Goal from the PRD's Problem Statement.
Suggested type is plan(<slug>) where slug is the plan directory name.
Step 5 — Stop
Ask the user if they're ready to move to /issues
Common Rationalizations
| Rationalization | Reality |
|---|
| "I know this codebase, no need to explore" | Domain terms may have changed. Explore first. |
| "The modules are obvious, no need to check with the user" | Module scope and test scope are separate decisions. Confirm both. |
| "I will write the PRD in the current repo" | Always use prd-end — it handles worktree creation and dep install |
| "I'll call git-worktree-create myself" | Always use prd-end — it handles worktree creation and dep install |
Checklist
