/ouroboros:interview

Socratic interview that turns a vague request into the goals, constraints, and acceptance criteria a Seed needs.

Required Skill Capabilities

• ask_user: ask human-judgment questions through the active runtime's ask_user capability.
• inspect_code: answer repo-local factual questions from exact local files before asking the user.
• call_mcp: use Ouroboros MCP tools for persistent interview state and seed generation.
• orchestrate_subagents: run advisory lanes and the Seed-ready Acceptance Guard lanes.
• run_lateral_review: invoke lateral thinking subagents before milestone turns and direct-answer synthesis.
• web_research: fetch current external facts only when the interview genuinely depends on them.
• refine_answer: confirm structured interpretations of free-text answers before forwarding them (Refine gate).
• maintain_ledger: keep ambiguity, gates, and unresolved decisions visible in the main session.
• run_closure_gate: run the Seed-ready Acceptance Guard even when MCP reports seed-ready.
• restate_goal: restate the goal and require explicit approval before seed generation (Restate gate).

Non-Skippable Gates

• Refine gate on free-text answers that carry scope, constraints, or decisions (step 4).
• A visible ambiguity ledger in the main session (step 6).
• MCP seed-ready (meta.seed_ready=true) is permission to run the Seed-ready Acceptance Guard (step 8), not completion.
• Restate gate and explicit user approval before suggesting or running seed generation (step 9).

The server names the last two seed_ready_acceptance_guard and restate_goal_approved in required_client_gates.

Usage

ooo interview [topic]
/ouroboros:interview [topic]