About prd
A skill that turns a feature request into a structured Product Requirements Document. It is for requests to produce a PRD rather than broader planning or strategy work.
Key features
- 01Generates a structured PRD
- 02Uses a feature request as input
- 03Returns task-specific action notes
Use cases
- 01Documenting requirements for a proposed feature
- 02Turning a feature request into a PRD
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/prdin Claude Code to confirm it loaded.
Bundled filesreferences/full-guidance.mdscripts/.gitkeep
Details
From the project READMEprd
Purpose
Generate a structured Product Requirements Document from a feature request.
Routing
- Use when: Use when the user asks to generate a structured Product Requirements Document from a feature request.
- Do not use when: Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Outputs: Outcome from prd: task-specific result plus concrete action notes.
- Success criteria: Returns concrete actions and decisions matching the requested task, with no fabricated tool-side behavior.
Trigger Examples
Positive
- Use the prd skill for this request.
- Help me with prd.
- Use when the user asks to generate a structured Product Requirements Document from a feature request.
- prd: provide an actionable result.
Negative
- Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Do not use prd for unrelated requests.
- This request is outside prd scope.
- This is conceptual discussion only; no tool workflow is needed.
Runtime Prompt
- Current runtime prompt length: 845 characters.
- Runtime prompt is defined directly in
../prd.json.
Comments
Markdown supported