prd-creation

An outcome-based PRD articulates what you want to achieve and how you'll measure success, rather than prescribing how to build it. Define your feature objective, expected user impact, and success metrics, then populate a standardized PRD template with clear outcomes and acceptance criteria to align stakeholders before development begins.

Outcome-focused requirements specify WHAT to achieve and success criteria; prescriptive requirements dictate HOW to build it. Outcome-based PRDs reduce scope ambiguity, enable design flexibility, and encourage cross-functional collaboration by centering on measurable goals rather than implementation details.

Reference your project's AGENTS.md guidance and review existing PRD templates in docs/prds/ to maintain consistency. Use standardized templates and follow established quality patterns so stakeholders recognize the format and requirements stay comparable across features.

Yes. Outcome-based PRDs explicitly define objectives and measurable success criteria, making them ideal for stakeholder review, refinement, and approval before implementation. Clear outcome statements help product, design, and engineering teams align on value and scope.

Success criteria translate outcomes into measurable metrics: user adoption targets, performance thresholds, business impact goals, or behavioral changes. Pair each criterion with a specific measurement method so teams can objectively verify whether the feature achieved its intended objective.