prd-discovery

What problem does it solve? Product ideas often arrive as messy notes, meeting summaries, roadmap fragments, or vague feature requests. This Skill structures that raw input into a clear discovery brief covering the problem, users, evidence, assumptions, constraints, and open questions, so a PRD is written on solid ground instead of guesswork. ## Core Features & Use Cases - Input Classification: Identifies whether the input is an idea, feature request, scope document, meeting summary, user feedback, or draft PRD, and synthesizes mixed inputs. - Structured Discovery Brief: Produces a ten-section brief in Russian covering problem statement, target users, current workflow, desired outcomes, evidence, assumptions, constraints, open questions, and a PRD readiness verdict. - Fact vs. Assumption Separation: Treats only user-provided information as fact, explicitly marks unverified assumptions, and flags high-risk areas like trust, compliance, and money movement. - Use Case: Paste raw meeting notes about a new feature idea and receive a structured discovery brief that clarifies the real problem, lists 5-10 critical open questions, and states whether the initiative is ready for PRD drafting. ## Quick Start Use the prd-discovery skill to turn these product notes into a structured discovery brief before writing a PRD.