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. ## Next Steps - Run `/plan-roadmap` to sequence delivery. - Run `/prioritize` if scope exceeds current capacity.
Run a structured discovery flow from problem framing through opportunity mapping and validation planning.
Guide PM to Director to VP/CPO transition planning with role-fit diagnostics and onboarding guidance.
Turn strategy and validated opportunities into a sequenced roadmap with clear tradeoffs.
Select what to work on next using the right prioritization method for your context.
Build product strategy from positioning through opportunity and roadmap decisions.
Evaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.
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.