메뉴
Parallelize independent subtasks — bulk refactors, multi-host changes, "do all of these". Maximize throughput with concurrent subagents.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
After `nix flake update`, sync `input_rev` and `input_hash` metadata in all flake-input skill files to match new `flake.lock`.
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
| name | fleet |
| description | Parallelize independent subtasks — bulk refactors, multi-host changes, "do all of these". Maximize throughput with concurrent subagents. |
| metadata | {"when_to_use":"fleet mode, throw a fleet, spawn agents, parallelize, many files at once, bulk refactor"} |
When a task breaks into independent, parallelizable subtasks, spin up task subagents concurrently in one message.
| Situation | Action |
|---|---|
| 5+ independent file edits | Fleet |
| Sequential edits (B depends on A) | Direct |
| 10 files, trivial one-liners | Direct (overhead > work) |
| Bulk search across 20+ files | Fleet |
| Multi-host changes (each independent) | Fleet |
| User says "do all of these", "fleet mode", "parallel", "at once" | Fleet |
Rule: If overhead outweighs per-item work, go direct. Batch trivial subtasks to one subagent.
Sketch the tree — one line per subagent prevents overlap:
Tree:
├── Agent A: search callers of getCwd
├── Agent B: search callers of setCwd
└── Agent C: check both against new API
Each subagent prompt must be self-contained:
Subagents can launch their own fleet (max depth 3):
Orchestrator
├── Subagent A (aggregates A1, A2, A3)
│ ├── A1 (leaf)
│ ├── A2 (leaf)
│ └── A3 (leaf)
└── Subagent B (aggregates B1, B2)
├── B1 (leaf)
└── B2 (leaf)
Parent aggregates children before returning. Each level strips irrelevant detail.