Install any skill in seconds. Free to start, no credit card required.
Get Started Free →q00/interview
Socratic interview to crystallize vague requirements
Passed 3 of 9 test cases with the skill, and 3 of 9 without it.
and 2 more in the full report
4 fixed4 passed either way12 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
The requirements session has just auto-confirmed three consecutive factual questions from codebase files (project framework, database adapter, and lockfile version). The next question generated asks whether the project has an existing Docker Compose setup.
| Checked | Without skill | With skill |
|---|---|---|
| routes the fourth consecutive question directly to the user for human judgment | Missed | Passed |
The instructions your model reads when the skill loads.
Socratic interview to crystallize vague requirements into clear specifications.
ask_user — ask human-judgment questions through the active runtime's user-question surface.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.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.run_shell — run bounded local commands for version checks and repository inspection.refine_answer — confirm structured interpretations of free-text answers before forwarding them.maintain_ledger — keep ambiguity, gates, and unresolved decisions visible in the main session.run_closure_gate — audit readiness locally even when MCP reports seed-ready.restate_goal — restate the goal and require explicit approval before seed generation.seed-ready as permission to audit closure, not as completion.ooo interview [topic]
/ouroboros:interview [topic]
Trigger keywords: "interview me", "clarify requirements"
When the user invokes this skill:
test cases passed, vs 3 / 9 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.