From prd-workflow
Full PRD workflow for creating, planning, and implementing Product Requirements Documents
How this skill is triggered — by the user, by Claude, or both
Slash command
/prd-workflow:prdThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The PRD skill handles the creation, planning, and implementation of Product Requirements Documents. It guides you through the appropriate workflow based on your intent.
reference/cli-tools.mdreference/log-spec.mdreference/prd-spec.mdreference/task-spec.mdscripts/get-task.shscripts/get-unanswered-research.shscripts/list-defined-tasks.shscripts/list-prd-draft-tasks.shscripts/list-prds.shscripts/research-status.shscripts/task-status.shscripts/update-task-status.shworkflows/CreatePRD.mdworkflows/PlanPRD.mdworkflows/WorkPRD.mdThe PRD skill handles the creation, planning, and implementation of Product Requirements Documents. It guides you through the appropriate workflow based on your intent.
The CLI scripts are located in scripts/ relative to this skill's directory. Before running any script, resolve the full absolute path based on where this skill file was loaded from. All script references in workflows use paths relative to this skill directory (e.g., scripts/list-prds.sh).
When this skill is invoked, follow these steps:
reference/prd-spec.mdscripts/list-prds.shWhen to use: Creating a new PRD from scratch
Trigger words: "create", "new", "draft", "start", "begin"
File: workflows/CreatePRD.md
Purpose: Gather requirements and create a new PRD document structure
When to use: An existing PRD needs analysis, research, and task definition
Trigger words: "plan", "analyze", "research", "refine", "break down", "define tasks"
File: workflows/PlanPRD.md
Purpose: Analyze the PRD, conduct research, and create detailed task specifications
When to use: A PRD has defined tasks ready for implementation
Trigger words: "implement", "build", "execute", "work", "code", "develop"
File: workflows/WorkPRD.md
Purpose: Execute defined tasks and complete the implementation
Is the user creating new content?
├── Yes → CreatePRD
└── No → Does the PRD exist?
├── No → Ask for clarification or suggest CreatePRD
└── Yes → Are tasks defined? (check with scripts/task-status.sh)
├── No tasks or all draft → PlanPRD
└── Tasks defined (defined > 0) → WorkPRD
Use these scripts to check PRD status:
scripts/list-prds.sh - List all PRDs with statusscripts/task-status.sh <prd> - Get task counts by statusscripts/research-status.sh <prd> - Get research completion statusreference/prd-spec.md - PRD file format specificationreference/task-spec.md - Task specification templatereference/cli-tools.md - Full CLI tool documentationIf the user's intent is unclear:
Never assume - always clarify when the routing decision is ambiguous.
npx claudepluginhub itzsaga/cc-prd --plugin prd-workflowClassifies task scope (quick fix, standard, PRD) and generates PRDs for features, multi-file bugs, refactors. Confirms requirements, follows repo CLAUDE.md for PRD paths at docs/tasks.
Guides interactive creation of Product Requirements Documents (PRDs) through structured questions across 15 sections like executive summary and problem statement. Saves as Markdown file.
Creates, validates, or edits product requirements documents via tri-modal workflows (Create -c, Validate -v, Edit -e) using sequential step files and BMAD standards for Phase 2 Planning.