How this skill is triggered — by the user, by Claude, or both
Slash command
/ouroboros:interviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Socratic interview to crystallize vague requirements into clear specifications.
Socratic interview to crystallize vague requirements into clear specifications.
ooo interview [topic]
/ouroboros:interview [topic]
Trigger keywords: "interview me", "clarify requirements"
When the user invokes this skill, choose the execution path:
If the ouroboros_interview MCP tool is available, use it for persistent, structured interviews:
Start a new interview:
Tool: ouroboros_interview
Arguments:
initial_context: <user's topic or idea>
The tool returns a session ID and the first question.
Present the question using AskUserQuestion:
After receiving a question from the tool, present it via AskUserQuestion with contextually relevant suggested answers:
{
"questions": [{
"question": "<question from MCP tool>",
"header": "Q<N>",
"options": [
{"label": "<option 1>", "description": "<brief explanation>"},
{"label": "<option 2>", "description": "<brief explanation>"}
],
"multiSelect": false
}]
}
Generating options — analyze the question and suggest 2-3 likely answers:
Relay the answer back:
Tool: ouroboros_interview
Arguments:
session_id: <session ID from step 1>
answer: <user's selected option or custom text>
The tool records the answer, generates the next question, and returns it.
Repeat steps 2-3 until the user says "done" or requirements are clear.
After completion, suggest ooo seed to generate the Seed specification.
Advantages of MCP mode: State persists to disk (survives session restarts), ambiguity scoring, direct integration with ooo seed via session ID, structured input with AskUserQuestion.
If the MCP tool is NOT available, fall back to agent-based interview:
agents/socratic-interviewer.md and adopt that roleThe interviewer is ONLY a questioner:
User: ooo interview Build a REST API
Q1: What domain will this REST API serve?
User: It's for task management
Q2: What operations should tasks support?
User: Create, read, update, delete
Q3: Will tasks have relationships (e.g., subtasks, tags)?
User: Yes, tags for organizing
User: ooo seed [Generate seed from interview]
After interview completion, use ooo seed to generate the Seed specification.
npx claudepluginhub mmerryweather/ouroborosCreates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.