prd-writing
PRD Writing
Write PRDs that communicate intent, scope, and constraints without over-specifying implementation.
How to use
/prd-writingApply PRD constraints to this conversation./prd-writing <feature>Draft or review a PRD for the described feature.
Constraints
Problem First
- MUST start with the problem, never the solution
- Problem statement MUST be understandable by someone who just joined the team in under 60 seconds
- MUST include user evidence (data, quotes, support tickets) not just PM intuition
- NEVER jump to features without establishing why this matters
Structure
- One-pager format for smaller features: problem, proposed solution, success metrics, scope boundaries, open questions
More from dragoon0x/product-skills
freemium-vs-paid-gate
Decide whether a product should offer a free tier, free trial, or go straight to paid. Structured decision framework based on economics, distribution model, and competitive landscape. Use when launching a new product or reconsidering your pricing model.
1error-recovery
When things break, guide people forward instead of leaving them stranded. Error message copy, retry patterns, graceful degradation, and recovery flows. Use when building error handling or failed state UIs.
1cta-patterns
Design calls-to-action that people actually click. Covers button copy, placement logic, urgency without manipulation, and progressive commitment. Use when reviewing pages for conversion potential or when CTA copy feels generic.
1onboarding-flow
Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.
1user-psychology
Apply motivation, friction, and trust patterns to product decisions. Maps cognitive biases and behavioral triggers to specific UI and copy choices. Use when reviewing flows for drop-off points or when something feels right but doesn't convert.
1microcopy
The small words that shape big experiences. Button labels, tooltips, confirmations, placeholders, and the 3-word strings that determine whether a product feels polished or half-finished. Use during any copy audit pass.
1