product-discovery

To turn vague ideas into PRDs and RFCs, structured product discovery runs batched clarification rounds to define scope, semantics, and architecture. It produces a discovery log and applies an independent review step to ensure implementation-ready artifacts.

Product discovery for defining requirements is a draft-to-review workflow. It guides you through batched questions to clarify UX structure and data assumptions, then requires an independent review to improve correctness before generating the final artifact.

Yes, you can generate a short clarity summary instead of a full PRD. The artifact-first output allows you to specify whether you need a PRD, RFC, design note, or message-style chat clarity summary at the end of the discovery process.

To start a guided clarification session for UX specifications, invoke the skill using the /product-discovery command. Specify your desired output format, and the system will begin a controlled sequence of batched questions to refine your feature scope.

A limitation of automated discovery for architecture decisions is that iteration is capped at a limited number of review passes. Additionally, the system requires strict explicit triggering and relies entirely on your direct input during the clarification rounds.

Yes, the product discovery workflow includes a mandatory independent review step. After producing a draft from the clarification rounds, this step evaluates the content to improve correctness and completeness before finalizing the design notes or RFC.