Introduction
This skill turns an ambiguous feature request into product requirements that can be discussed, implemented, and accepted. It clarifies the problem, users, business outcome, scope, flows, rules, exception cases, nonfunctional needs, dependencies, and success measures, while listing unresolved questions instead of guessing them away.
Use Cases
Use it for new-feature PRDs, workflow changes, internal tools, platform capabilities, and cross-team reviews. It can create a specification from scratch or audit an existing document for contradictions, gaps, and untestable language.
Template
Provide the background, user problem, goal, main flow, known rules, scope limits, technical or compliance constraints, related systems, and timing. The output includes a structured PRD, scenarios, edge cases, dependencies, risks, and verifiable acceptance criteria.
