agent-army

# Agent Army A 2-layer parallel execution framework. The Commander is the top-tier model — Fable by default, or Opus if that's the session model — and does the thinking: recon, composition, briefing, verification. It orchestrates swarms of subordinate models whose tiers the user picks at deploy time (see Power Level). Each Layer 1 agent has its own full context window (not a slice). Each spawns Layer 2 sub-agents under it. The result is many independent brains running at once — not one brain divided. ``` Commander (you — Fable or Opus, the session model) | |-- Layer 1: Team (3 to 50+, each = own 1M context, L1 tier from power level) | |-- Agent A (1M) -- Sub-agent A1, A2, ... (L2 tier) | |-- Agent B (1M) -- Sub-agent B1, B2, ... (L2 tier) | |-- Agent C (1M) -- Sub-agent C1, C2, ... (L2 tier) | |-- ... (no cap) ``` **Swarm vs. army:** A swarm splits one context window across sub-agents — one brain, divided. An army gives each Layer 1 member its own window. That difference is the whole point of this skill. ## When to use - Large refactors spanning many files - Multi-file color / style / naming / API migrations - Broad codebase audits (security, a11y, performance, dead code) - Bulk content generation or transformation - Any task with **6+ independent units of work** that can run simultaneously ## When NOT to use - Fewer than 6 independent units of work — just do it directly - Heavy sequential dependencies where each step needs the last one's output - ...