oh-my-ai/discovery-interview
Interactive discovery interview → structured product spec. Triggers: spec, PRD, requirements, scoping, brainstorming, new project. Uses AskUserQuestion; WebSearch/WebFetch when user wants research. Outputs user stories, acceptance criteria, constraints.
99
2.28x
Quality
100%
Does it follow best practices?
Impact
96%
2.28xAverage score across 3 eval scenarios
Securityby
Advisory
Suggest reviewing before use
orientation-and-deep-dive.mdrules/
- name:
- orientation-and-deep-dive
- description:
- Phases 1–2 — initial orientation and per-category discovery using CATEGORIES.md
Orientation and category deep dive
Phase 1: Initial orientation
Use 2–3 AskUserQuestion rounds to nail:
- What problem are you solving?
- Who will use this?
- New build vs improving something existing?
Infer project type (guides which categories matter most): Backend/API · Web · CLI · Mobile · Full-stack · Script/automation · Library/SDK.
Phase 2: Category deep dive
Use CATEGORIES.md. For each relevant category:
- Ask at least 2 questions (typically 2–4) via AskUserQuestion.
- If the user is unsure, offer research (see Phase 3 in research-and-conflict-resolution).
- Educate when needed so decisions are informed.
- Track decisions internally.