ouroboros-run

# /ouroboros:ouroboros-run Execute a Seed specification through the Ouroboros workflow engine. ## Usage ``` /ouroboros:ouroboros-run [seed_file_or_content] ``` **Trigger keywords:** "ouroboros run", "execute seed" ## How It Works 1. **Input**: Provide seed YAML content directly or a path to a `.yaml` file 2. **Validation**: Seed is parsed and validated (goal, constraints, acceptance criteria, ontology) 3. **Execution**: The orchestrator runs the workflow with PAL routing 4. **Progress**: Real-time progress updates via session tracking 5. **Result**: Execution summary with pass/fail status 6. **Convergence**: completed runs enqueue formal evaluation by default. An explicit rejection continues through a bounded Ralph loop until approved or the configured evolution budget/stop condition is reached. ## Instructions When the user invokes this skill: ### Load MCP Tools (Required first) The Ouroboros MCP tools are often registered as **deferred tools** that must be explicitly loaded before use. **You MUST perform this step before proceeding.** 1. Use the active runtime's tool-discovery capability to find and load the execution MCP tools: ``` tool discovery query: "+ouroboros execute" ``` 2. The tools will typically be named with prefix `mcp__plugin_ouroboros_ouroboros__` (e.g., `ouroboros_execute_seed`, `ouroboros_session_status`). After runtime tool discovery returns, the tools become callable. 3. If the tools are callable — already exposed, or loaded by d...