prd

To structure vague product requirements into actionable user stories, you need a guided dialogue that clarifies problem statements, success criteria, constraints, scope, and priorities. This process translates ambiguous feature ideas into a structured brief defining the what and why for development planning.

The best way to clarify ambiguous feature requests is through a structured questioning process focused on product definition. By defining problems, success criteria, and constraints upfront, you ensure the information passed to the planner is fully structured and actionable.

You define scope and priorities for a new product feature by engaging in a requirement discovery dialogue. This structured input process guides you through articulating specific constraints and success criteria, ensuring the final scope reflects the core problem statement.

Yes, you can generate a structured planner command from initial requirement discovery. The clarified requirements, including scope and priorities, are translated into a structured format suitable for direct delegation to a Planner skill for execution.

Requirement discovery works specifically for initial product definition phases. It applies to the early stages of requirement gathering by helping product managers articulate the what, why, and how of a feature before any technical planning begins.