product-discovery

Product discovery transforms vague ideas into actionable specifications by applying structured questioning techniques—Five Whys, MECE, Socratic Probing—across Vision, Core Problem, Users, Technical, Validation, and Scoping phases. This produces SPEC.md, DESIGN.md, and PLAN.md documents with clear requirements, success criteria, and MVP scope.

MVP scoping uses discovery techniques to define target users, core problems, functional requirements, technical architecture, data models, and validation criteria. The Skill generates structured templates and implementation roadmaps that distinguish must-have features from future enhancements, reducing scope creep.

Use structured discovery during greenfield projects, ideation phases, and MVP definition to surface hidden assumptions and gaps. MECE ensures mutually exclusive, collectively exhaustive coverage; Socratic Probing uncovers unstated requirements through guided questioning—both prevent incomplete specifications.

Yes. The /greenfield command generates SPEC.md, DESIGN.md, and PLAN.md templates populated with problem statements, target users, MVP scope, architecture, data models, risks, and implementation roadmaps derived from your idea through structured discovery.

Specifications include problem statements, target user profiles, MVP feature scope, success criteria, technical architecture, data models, identified risks, and phased implementation roadmaps. Templates cover functional and technical requirements needed to move from ideation to development.

No external dependencies or tools are required. Product discovery works with your existing idea and generates templates and documents as outputs. The Skill provides the questioning framework and document structure; you supply the domain knowledge.