agent-army

# Agent Army A 2-layer parallel execution framework. 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) | |-- Layer 1: Team (3 to 50+, each = own 1M context) | |-- Agent A (1M) -- Sub-agent A1, A2, ... | |-- Agent B (1M) -- Sub-agent B1, B2, ... | |-- Agent C (1M) -- Sub-agent C1, C2, ... | |-- ... (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 - Single-file changes - Tasks needing one coherent authorial voice across all output (parallel agents drift) If the task doesn't clearly fit, say so and propose doing it inline instead of spinning up an army. <mandatory-rules> ## MANDATORY RULES 1. EVERY Layer 1 agent MUST spawn 2+ sub-agents. No exceptions. If you're about to deploy an L1 agent with no sub-...