51 skills · sorted by relevance
Use when EZ_math_model runs in multi or hybrid mode and has two or more independent subtasks that can be assigned to subagents without shared files, shared state, or dataflow dependencies.
The English summary is being prepared. Showing the original description.
Use when facing 2+ independent tasks or investigations that can be worked on without shared state or sequential dependencies — fan out to specialized sub-agents with isolated context, then synthesize the results.
The English summary is being prepared. Showing the original description.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
The English summary is being prepared. Showing the original description.
Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.
The English summary is being prepared. Showing the original description.
Split independent work across parallel agents with explicit boundaries and a parent integration review. Use only when user allows subagents and tasks do not share mutable files.
The English summary is being prepared. Showing the original description.
当面对 2 个以上可以独立进行、无共享状态或顺序依赖的任务时使用
The English summary is being prepared. Showing the original description.
Use ONLY when the user explicitly asks to orchestrate parallel external agents (Codex or Claude Code) in tmux sessions via tp (tmux-pilot). Or when a user tells you that you're the boss or orchestrator. You can also use this if you are an operclaw agent. NEVER auto-invoke for a generic "do this in parallel" request. For in-process subagents, use superpowers:dispatching-parallel-agents instead.
The English summary is being prepared. Showing the original description.
Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.
The English summary is being prepared. Showing the original description.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
The English summary is being prepared. Showing the original description.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
The English summary is being prepared. Showing the original description.
Identify independent failures and spawn concurrent agents. Turns sequential N×time into 1×time.
The English summary is being prepared. Showing the original description.
Manages git worktrees for parallel agent isolation. Creates isolated worktrees for parallel agents on parallel/{name}-{timestamp} branches, merges results with conflict detection, prunes stale metadata, and reports health status. NOT for user-initiated feature branches — use git worktree directly for that.
The English summary is being prepared. Showing the original description.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
The English summary is being prepared. Showing the original description.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
The English summary is being prepared. Showing the original description.
Use quando enfrentar 2+ tarefas independentes que podem ser trabalhadas sem estado compartilhado ou dependências sequenciais
The English summary is being prepared. Showing the original description.
Padrões de orquestração multi-agente. Use quando múltiplas tarefas independentes podem rodar com diferentes especialidades de domínio ou quando uma análise abrangente requer múltiplas perspectivas.
The English summary is being prepared. Showing the original description.
Use quando enfrenta 2+ tarefas independentes que podem ser trabalhadas sem estado compartilhado ou dependências sequenciais
The English summary is being prepared. Showing the original description.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
The English summary is being prepared. Showing the original description.
Prevent tool call conflicts when making concurrent edits across a codebase. Establishes strict file ownership, interface contracts, and merge strategies. Use with parallel-agents when executing concurrent code changes.
The English summary is being prepared. Showing the original description.
Orchestrate concurrent analysis or implementation across independent domains. Use when a task can be decomposed into independent workstreams (e.g., via simultaneous tool calls or background processes) — spec writing, code review, security audit, feature implementation.
The English summary is being prepared. Showing the original description.
Use multiple Claude agents to investigate and fix independent problems concurrently
The English summary is being prepared. Showing the original description.
Use when facing 2+ independent tasks — "in parallel", "independent tasks", "multiple unrelated failures", "different test files or subsystems" — that can be worked on without shared state or sequential dependencies. Dispatch one agent per independent slice, each with only the context it needs, even when the user did not ask for subagents explicitly.
The English summary is being prepared. Showing the original description.
Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.
The English summary is being prepared. Showing the original description.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
The English summary is being prepared. Showing the original description.