Find running or paused Ouroboros sessions after an MCP server disconnect. The skill lists saved sessions and provides commands to inspect recorded events, open a monitor, or resume execution with the original Seed specification file.
List in-flight Ouroboros sessions and show the commands needed to re-attach after MCP disconnect
Review the instructions the agent will receive before you install.
Recover in-flight Ouroboros sessions after an unexpected MCP server disconnect. The name avoids shadowing Claude Code's built-in /resume.
ooo resume-session [--all]
/ouroboros:resume-session
Run with the active runtime's run_shell capability:
ouroboros resume --list
It reads the configured EventStore directly and read-only (no MCP server needed, nothing created or written) and lists running or paused sessions: the 20 most recent, or all with --all. --list prints the table and exits without the interactive prompt, which aborts when no terminal is attached. Exit code 2 means the EventStore exists but could not be read.
If sessions are listed, show the table and ask which session to work with (active runtime's ask_user capability). Each row carries the session_id, exec_id, and Seed id used below.
Give the matching re-attach path:
ouroboros status execution <exec_id> --events
ouroboros tui monitor
--resume takes the session_id):
ouroboros run workflow --orchestrator --resume <session_id> <seed.yaml>
Afterwards: ooo evaluate once the execution completes, or ooo cancel <session_id> if it is stuck.
If it reports "No in-flight sessions found", the execution completed, failed, or was cancelled, or the EventStore was never created; ouroboros tui monitor browses past sessions.
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.