# Ouroboros Run

Use when an Ouroboros Seed (a spec file with a goal and acceptance criteria, such as...

- Repository: https://github.com/Q00/ouroboros (6302 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Q00/ouroboros --skill ouroboros-run -g -a claude-code -y`
Codex: `npx skills add Q00/ouroboros --skill ouroboros-run -g -a codex -y`
Cursor: `npx skills add Q00/ouroboros --skill ouroboros-run -g -a cursor -y`
Gemini CLI: `npx skills add Q00/ouroboros --skill ouroboros-run -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add Q00/ouroboros`

## Description

Use when an Ouroboros Seed (a spec file with a goal and acceptance criteria, such as *.seed.yaml) already exists and the user wants it executed: 'run the seed', 'execute this spec', 'ooo run'. Executes it and verifies every acceptance criterion. Not for raw requests without a Seed (use interview or auto).

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# /ouroboros:ouroboros-run

Execute a Seed specification through the Ouroboros workflow engine as a background job. A completed run enqueues formal evaluation by default, and a rejection continues through a bounded Ralph loop.

## Usage

```
/ouroboros:ouroboros-run [seed_file_or_content]
```

## Instructions

### Loading MCP tools (deferred-schema guard)

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 execute"` for `ouroboros_start_execute_seed`, `ouroboros_job_wait`, `ouroboros_job_result`, and `ouroboros_ac_tree_hud`; `"+ouroboros session signal"` for `ouroboros_session_signal_targets` and `ouroboros_session_signal`. 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 (No MCP Server)** section only when the tools are genuinely absent.

### Execution Steps

1. **Do not create or switch branches yourself.** For a background execution
   job, `use_worktree` defaults to true: the server runs the task in its own
   worktree and reports `worktree_path` / `worktree_branch` in the job result.
   Tell the user the task was isolated only when those fields are present. A
   `dispatch_mode="plugin"` response delegates to a child session and carries
   no worktree.

2. **Get the Seed.** Read a given file path with the active runtime's `inspect_code` capability, use inline YAML directly, or otherwise take the most recently generated Seed in the conversation.

The rest: https://github.com/Q00/ouroboros/blob/HEAD/skills/run/SKILL.md