Clarify ambiguous product requirements through a guided Socratic interview.
npx skills add https://github.com/kok1eee/o-m-cc --skill deep-interview-kok1eee
Please help me install this Agent Skill. Skill: deep-interview Source: https://github.com/kok1eee/o-m-cc/tree/main/skills/deep-interview Command: npx skills add https://github.com/kok1eee/o-m-cc --skill deep-interview-kok1eee
Ambiguous or high-level feature ideas cause wasted effort, misaligned expectations, and slow progression to design and implementation. This skill guides stakeholders through a focused, step-by-step interview to transform fuzzy ideas into a concrete, structured requirements summary ready for planning.
Run the deep-interview skill with a short vague feature idea, for example: /o-m-cc:deep-interview "allow users to save drafts".
High-intent search queries and answers about installing and using this skill.
To clarify vague product requirements, use a Socratic interview loop that evaluates WHO, WHAT, WHY, SCOPE, and CONSTRAINT axes, asking up to seven targeted questions to transform fuzzy ideas into a structured summary.
The best way to run requirements discovery is applying a five-axis ambiguity evaluation that adapts subsequent questions to prior answers, minimizing user burden while producing a handoff-ready structured requirements summary.
To conduct a Socratic interview for feature requests, ask one targeted question at a time, evaluate ambiguity across five axes, and stop after clarity is reached or seven questions are answered to prevent stakeholder fatigue.
Yes, you can ground requirement questions in existing code or docs by using repository search tools like Glob, Grep, and Read to contextually adapt questioning when a repository is available.
After completing requirements discovery, you should use the generated five-axis structured summary for deeper analysis or invoke a discovery-council process for downstream planning and design handoffs.
You should not use a guided interview for stakeholder feature requests when the requirements are already concrete and unambiguous, as the Socratic questioning loop is specifically designed for early-stage and fuzzy ideas requiring discovery.
AcendasGuides feature discovery conversations from vague ideas to structured plans and specs.
r-irbeAudit Lean 4 projects to identify and close retroactive council coverage gaps.
tranvietanh0Search source code, skills, and documentation for code fragments and usage examples.
djd1mClarify vague user requests through guided Socratic questioning into structured Task Briefs.
