What problem does it solve? Teams often build the wrong thing because requirements live in scattered conversations, scope creeps silently, and success is never defined in advance. This Skill structures PRD writing so every document records decisions with evidence, kills scope creep with explicit non-goals, and pre-commits to measurable outcomes. ## Core Features & Use Cases - Evidence-based problem framing: Enforces a problem statement template (user pain + business stake) free of solution vocabulary, backed by interviews, tickets, or funnel data. - Scope containment: Requires a non-goals section with reasons, MoSCoW-ranked requirements, and a would-we-still-ship test for must-haves. - Accountable success criteria: Pre-commits metrics, targets, guardrails, and an instrumentation plan before build starts. - Use Case: Sales requests "invoice customization." The Skill guides you to interview evidence showing customers actually need logo and tax fields, scope the PRD to that, list template editing as a non-goal, and catch a jurisdiction compliance question early — halving the engineering estimate. ## Quick Start Write a PRD for the payout reconciliation feature using the attached support tickets and interview notes as evidence.
