Loading...
Loading...
Found 49 Skills
Use when dealing with 2 or more tasks that can be performed independently, with no shared state or sequential dependencies
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.
Use when a task has multiple independent subtasks that can be executed concurrently by separate agents. Triggers when decomposed work has 2+ subtasks with no data dependencies, when subtasks operate on different files or codebase sections, when serial execution time would be significantly longer than parallel, or when independent analyses or deliverables need concurrent generation.
Concurrent investigation of independent failures. Use when multiple unrelated issues need parallel resolution.
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.
Concurrent investigation pattern - dispatches multiple AI agents to investigate and fix independent problems simultaneously.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Read this BEFORE launching any subagent (Task tool, background agents, parallel agents, best-of-N, delegating work to another agent). Hard model rules for subagents plus consensus principles for using them well. Triggers: launch a subagent, spawn agents, run agents in parallel, delegate to a subagent.
Comprehensive Python/FastAPI backend code review with optional parallel agents
Launch 3 research agents in parallel — market, users, tech — fast answers
Systematic implementation using APEX methodology (Analyze-Plan-Execute-eXamine) with parallel agents, self-validation, and optional adversarial review. Use when implementing features, fixing bugs, or making code changes that benefit from structured workflow.