auto

# /ouroboros:auto Run the full-quality auto pipeline from a single task description. ## Dispatch requirement This skill must be executed by invoking MCP tool `ouroboros_start_auto`. Do not manually inspect repositories, run shell commands, query GitHub, edit files, or otherwise emulate the auto pipeline as a substitute. Full auto runs routinely exceed interactive MCP tool-call timeouts, so the background starter is the supported default: it returns `job_id` and `auto_session_id` quickly. Retain both. When `response.meta.job_observer` is present, delegate its read-only wait/result contract to exactly one independent child session. The main session keeps only start and explicit on-demand status responsibility. If `ouroboros_start_auto` is unavailable, or if any required job polling/result MCP tool is unavailable, stop and report that the required MCP tool is unavailable. A manual fallback is not an `ooo auto` run. If a started auto job later returns `detached`, `blocked`, `failed`, or another auto-session status, report that auto-session status and the tool's blocker. `detached` is non-terminal tracked background work; surface the job/Ralph handles and keep observing them through the same owner. Do not label a `blocked` or `failed` outcome as MCP dispatch failure; dispatch failure means the MCP tool could not be invoked. If the active runtime routes `ooo auto` through a background starter such as `ouroboros_start_auto`, do not stop after returning the `job_id`. Keep owner...