Loading...
Loading...
Found 44 Skills
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when parallel agents share a codebase: adding new behavior, editing or resolving conflicts in shared files (dispatchers, registries, lockfiles), finding and splitting churn hotspots, or writing AGENTS.md, CLAUDE.md, or README.
Dispatches one subagent per independent domain to parallelize investigation/fixes. Use when you have 2+ unrelated failures (e.g., separate failing test files, subsystems, bugs) with no shared state or ordering dependencies.
This is intended for use when OpenSpec workflows require dependency-aware parallel subagents that are compatible with OPSX commands, legacy OpenSpec commands, and Codex CLI prompt aliases.
Parallel Agent Orchestration
Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.
You MUST use this when several units of work might run concurrently through agents - independent investigations, specialist reviews, repository analyses, or plan tasks that look unrelated - covering whether they are genuinely independent, which mutable state needs isolation, how wide the wave should be, and how results are reconciled before integration.
Fan out independent read and write lanes.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when facing 3+ independent failures that can be investigated without shared state or dependencies - dispatches multiple Claude agents to investigate and fix independent problems concurrently
Use when facing 2 or more independent tasks that can be completed without shared state or sequential dependencies
Dispatch independent subagents in parallel for unrelated problems spanning different subsystems. Use when 2+ failures have independent root causes, multiple subsystems are broken independently, or user requests concurrent investigation. Use for "parallel", "multiple failures", "independent bugs", "fix these concurrently". Do NOT use for related failures, shared-state problems, or exploratory debugging where root cause is unknown.