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
completeness-spec-and-handoff.mdrules/
- name:
- completeness-spec-and-handoff
- description:
- Phases 5–7 — completeness gate, writing the spec from SPEC_TEMPLATE.md, and handoff
Completeness check, spec output, and handoff
Phase 5: Completeness check
Do not write the spec until all of the following are satisfied:
| Area | Must have |
|---|---|
| Problem | Clear problem statement, success metrics, stakeholders |
| UX | User journey, core actions, error/edge handling |
| Technical | Data model, integrations, scale, security, deployment |
| Decisions | Tradeoffs explicitly chosen; no silent TBDs; user confirms understanding |
If something is missing: name the gap, run targeted Phase 2 questions, then re-run this table.
Phase 6: Spec generation
- Summarize understanding; get confirmation.
- Generate
docs/specs/YYYY-MM-DD-<name>.mdfrom SPEC_TEMPLATE.md.
Phase 7: Implementation handoff
AskUserQuestion for next steps:
- Start implementation → User can say they want the spec implemented.
- Plan implementation → Plan agent or
/create_planif available. - Review spec / done → Confirm path and that the spec reflects what was agreed.