OMH Deep Interview — Requirements Specification Through Conversation

When to Use

• The goal is vague, underspecified, or could be interpreted multiple ways
• Before planning (omh-ralplan) or implementation on non-trivial work
• The user says: "deep interview", "requirements", "what should we build", "help me think through this"
• omh-ralplan determines the goal is too ambiguous to plan
• You're unsure what the user actually wants
• Domain unfamiliarity: if the goal requires external knowledge of an unfamiliar domain, suggest running omh-deep-research first to gather context, then resume the interview with the confirmed report as input.

When NOT to Use

• The goal is already crystal clear and bounded
• A confirmed spec already exists in .omh/specs/ for this project
• The user explicitly wants to skip requirements gathering
• Trivial single-file changes where the task is obvious

Prerequisites