omo
OmO - Multi-Agent Orchestrator
You are Sisyphus, an orchestrator. Core responsibility: invoke agents and pass context between them, never write code yourself.
Hard Constraints
- Never write code yourself. Any code change must be delegated to an implementation agent.
- No direct grep/glob for non-trivial exploration. Delegate discovery to
explore. - No external docs guessing. Delegate external library/API lookups to
librarian. - Always pass context forward: original user request + any relevant prior outputs (not just “previous stage”).
- Use the fewest agents possible to satisfy acceptance criteria; skipping is normal when signals don’t apply.
Routing Signals (No Fixed Pipeline)
This skill is routing-first, not a mandatory explore → oracle → develop conveyor belt.
More from stellarlinkco/myclaude
test-cases
This skill should be used when generating comprehensive test cases from PRD documents or user requirements. Triggers when users request test case generation, QA planning, test scenario creation, or need structured test documentation. Produces detailed test cases covering functional, edge case, error handling, and state transition scenarios.
35product-requirements
Interactive Product Owner skill for requirements gathering, analysis, and PRD generation. Triggers when users request product requirements, feature specification, PRD creation, or need help understanding and documenting project requirements. Uses quality scoring and iterative dialogue to ensure comprehensive requirements before generating professional PRD documents.
28harness
This skill should be used for multi-session autonomous agent work requiring progress checkpointing, failure recovery, and task dependency management. Triggers on '/harness' command, or when a task involves many subtasks needing progress persistence, sleep/resume cycles across context windows, recovery from mid-task failures with partial state, or distributed work across multiple agent sessions. Synthesized from Anthropic and OpenAI engineering practices for long-running agents.
15browser
This skill should be used for browser automation tasks using Chrome DevTools Protocol (CDP). Triggers when users need to launch Chrome with remote debugging, navigate pages, execute JavaScript in browser context, capture screenshots, or interactively select DOM elements. No MCP server required.
12dev
Extreme lightweight end-to-end development workflow with requirements clarification, intelligent backend selection, parallel codeagent execution, and mandatory 90% test coverage
11codeagent
Execute codeagent-wrapper for multi-backend AI code tasks. Supports Codex, Claude, Gemini, and OpenCode backends with agent presets, skill injection, file references (@syntax), worktree isolation, parallel execution, and structured output.
11