Loading...
Loading...
Found 72 Skills
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
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.
Orchestrate multiple code-writing agents in parallel when the work contains 3 or more genuinely independent build tasks. Use for execution lanes with disjoint write scope, clear task boundaries, and no dependency edges that would force sequencing.
Parallel Agent Type Contracts
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.
Orchestrate multiple specialized agents working in parallel to debug independent problems. Use when encountering 3+ unrelated bugs or test failures in isolated modules. Matches each problem to the right expert agent and launches them concurrently via the Agent tool with worktree isolation. Supports all available subagent types.
Concurrent investigation pattern - dispatches multiple AI agents to investigate and fix independent problems simultaneously.
Parallel Agent Orchestration
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.
Concurrent investigation of independent failures. Use when multiple unrelated issues need parallel resolution.
Use when facing 2 or more independent tasks that can be completed without shared state or sequential dependencies