Check an Ouroboros execution session’s status and progress, and optionally compare its current output with the original Seed specification. The drift report explains goal deviations and suggests whether to continue, evaluate, or reconsider the direction.
Check session status and measure goal drift
Review the instructions the agent will receive before you install.
Check an execution session's status and, on request, measure drift from the Seed goal.
/ouroboros:ouroboros-status [session_id]
Ouroboros tools may be deferred, and a schema loaded on one turn can unload by the next. Immediately before each ouroboros_* call, load it with the active runtime's tool-discovery capability: "+ouroboros session status" for ouroboros_session_status and ouroboros_measure_drift. A call whose schema is not loaded fails with "Invalid tool parameters". If the tool is already callable, discovery is a no-op and an empty result is expected. Use the fallback only when the tool is genuinely absent.
Session: use the given session_id, else the most recent one in the conversation, else ask the user.
Call ouroboros_session_status MCP tool:
Tool: ouroboros_session_status
Arguments:
session_id: <session ID>
If the user asks about drift (or says "am I drifting?"), also call ouroboros_measure_drift:
Tool: ouroboros_measure_drift
Arguments:
session_id: <session ID>
current_output: <current execution output or file contents>
seed_content: <original seed YAML>
constraint_violations: [] (any known violations)
current_concepts: [] (concepts in current output)
Show the status and progress, and the drift report as the tool renders it (weights, threshold, breakdown, suggestions). When combined drift exceeds 0.3 (status EXCEEDED), warn and suggest ooo interview to re-clarify or ooo evolve to course-correct; otherwise suggest continuing with ooo run or ooo evaluate.
Tell the user session tracking needs the Ouroboros MCP server (ooo setup), and that without it they can compare the implementation against the Seed by hand.
End the final response with exactly one line ◆ <current state> → next: <recommended action>. Derive the state from live session state via ouroboros_session_status when available, otherwise from this skill's actual outcome. Never use a linear Step N of M footer; when the next step is a real choice, list 2-3 options.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Turn a multi-file development task or technology migration into a specification with acceptance criteria, then launch background implementation and verification. The workflow clarifies missing requirements, reviews the specification, and tracks progress and blockers through linked jobs.
Register and search existing Git repositories and worktrees, then choose which projects Ouroboros interviews use as context. You can also generate a configuration containing verified build, test, and other check commands for the evaluation workflow.
Stop stuck Ouroboros executions or background jobs by ID, or cancel all running and paused executions in the current project. It reports whether cancellation is complete or has been requested, with guidance for checking the final status.
Verify finished work against acceptance criteria using executable checks and a review of whether each requirement is met. Multiple models can review uncertain cases, and rejected work can enter an automated repair loop when the required Seed is available.
Start and monitor an Ouroboros development loop that revises project concepts and acceptance criteria, the conditions for judging completion. Run and evaluate successive generations, focus revisions on failed criteria, inspect progress, or rewind to an earlier generation.
Turn a vague development idea into clear goals, constraints, and acceptance criteria through a guided interview. It checks unresolved decisions and confirms the agreed goal before moving toward a Seed, the requirements document used by Ouroboros.