Execute a Seed specification through the Ouroboros workflow engine.
Scanned 2/12/2026
Install via CLI
openskills install Q00/ouroboros# /ouroboros:run
Execute a Seed specification through the Ouroboros workflow engine.
## Usage
```
/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
## Instructions
When the user invokes this skill:
1. Check if the user provided seed content or a file path:
- If a file path: Read the file with the Read tool
- If inline YAML: Use directly
- If neither: Check conversation history for a recently generated seed
2. Call the `ouroboros_execute_seed` MCP tool:
```
Tool: ouroboros_execute_seed
Arguments:
seed_content: <the seed YAML>
model_tier: "medium" (or as specified by user)
max_iterations: 10 (or as specified by user)
```
3. If resuming an existing session, include `session_id`:
```
Tool: ouroboros_execute_seed
Arguments:
seed_content: <the seed YAML>
session_id: <existing session ID>
```
4. Present the execution results to the user:
- Show success/failure status
- Show session ID (for later status checks)
- Show execution summary
- Suggest `/ouroboros:evaluate` for post-execution verification
## Fallback (No MCP Server)
If the MCP server is not available, inform the user:
```
Ouroboros MCP server is not configured.
To enable full execution mode, run: /ouroboros:setup
Without MCP, you can still:
- Use /ouroboros:interview for requirement clarification
- Use /ouroboros:seed to generate specifications
- Manually implement the seed specification
```
## Example
```
User: /ouroboros:run seed.yaml
[Reads seed.yaml, validates, executes via MCP]
Result:
Seed Execution SUCCESS
========================
Session ID: sess-abc-123
Goal: Build a CLI task manager
Duration: 45.2s
Messages Processed: 12
Next: /ouroboros:evaluate sess-abc-123
```
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.