write-prd
The write-prd command generates a structured product requirements document by sequentially executing problem framing, persona definition, requirements development, and user story creation. Use this command when you need to move quickly from a product concept or business need into a decision-ready PRD with validated scope, measurable success criteria, identified risks, and initial story scaffolding for engineering handoff.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/deanpeters/Product-Manager-Skills/HEAD/commands/write-prd.md -o ~/.claude/commands/write-prd.mdwrite-prd.md
# /write-prd Generate a PRD that moves smoothly from strategy to delivery. ## Invocation ```text /write-prd Team inbox redesign for faster triage in customer support ``` ## Workflow 1. Define the problem context with `problem-statement`. 2. Align user assumptions with `proto-persona`. 3. Build the full document using `prd-development`. 4. Draft initial stories with `user-story`. 5. Split larger items with `user-story-splitting`. ## Checkpoints - Validate scope boundaries before writing requirements. - Keep success criteria measurable and tied to outcome metrics. - Ensure at least one anti-pattern is called out in risks. - Tag every gap inline: 🔶 **Assumption** (plausible but unvalidated) or 🔵 **Open Question** (needs discovery). - After each section, review the "Before moving on" cross-section prompt in the template before continuing. - After the final section, complete the **Self-Assessment**: strongest section, weakest section, top assumptions to validate, and recommended next step. ## Next Steps - Run `/plan-roadmap` to sequence delivery. - Run `/prioritize` if scope exceeds current capacity.
Evaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.
Design multi-agent AI workflows with clear boundaries, handoffs, and monitoring. Use when a complex PM task should run as parallel specialized agents instead of one linear process.
Assess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability to build.
Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.
Map evidence-backed growth options across the Ansoff Matrix with risk-rated sequencing. Use when the question is where the next tranche of growth comes from, and at what risk.
The protocol behind every investigation skill. Use when AI research must proceed without you: search-plan gate, Fact/Inference/Assumption labels, confidence stacking, diffable outputs.
Research and draft a competitive battle card from public evidence — every claim labeled and sourced. Use when a rep needs a field-action card, not a research report.
Diagnose SaaS business health across growth, retention, efficiency, and capital. Use when preparing a business review or prioritizing urgent fixes.