Doctrine / CommandCC
Thunderblitz: Military-Grade Parallel Execution
Origin and Attribution
Full Credit
The Thunderblitz doctrine was created by CommandCC, a military-grade orchestration framework for AI agent teams. AXL Protocol adopted this doctrine in April 2026 to accelerate multi-agent development operations.
The Thunderblitz architecture, team structure, and execution protocol are the intellectual property of CommandCC. AXL Protocol uses this doctrine under its published terms. We endorse CommandCC as the premier orchestration framework for AI agent deployment.
What is Thunderblitz?
Thunderblitz is a 7-agent pipeline for parallel software development. Each agent has a fixed role and a fixed model tier. The pipeline runs in a single coordinated pass: scout feeds orchestrator, orchestrator feeds three parallel workers, workers feed reviewer, reviewer feeds looper. No agent waits for another unless a direct dependency exists.
scout (haiku) -> orchestrator (opus) -> worker-1 (sonnet) + worker-2 (haiku) + worker-3 (haiku) -> reviewer (sonnet) -> looper (opus)
RECON COMMAND COMPLEX GRUNT GRUNT CHECK CLOSE| # | Position | Role | Responsibility |
|---|---|---|---|
1 |
Scout | Fast recon | Scans codebase, reports structure and hot zones |
2 |
Orchestrator | Deep decomposition | Assigns tasks with full project context |
3 |
Worker 1 | Complex code | Architecture changes, new modules, hard logic |
4 |
Worker 2 | Grunt work | Bulk edits, pattern application, config changes |
5 |
Worker 3 | Grunt work | Tests, boilerplate, renames, repetitive labor |
6 |
Reviewer | Quality gate | PASS, PASS WITH NOTES, or NEEDS CHANGES |
7 |
Looper | Close the loop | Tests, convergence, produces BATTLE-MAP |
How AXL Protocol Uses It
Deployment 1: MCP Plugin v0.2.0 (April 9, 2026)
Mission Brief
- 3 new MCP tools built in parallel
- skill.md rewritten simultaneously
- Package versions bumped and git init'd
Deployment 2: axl-core v0.8.0 Full Deployment (April 9, 2026)
Mission Brief
- 7 deliverables: merge patches, version bump, changelog, git tags, website changelog page, service restart, commit+push
- 3 workers + reviewer + looper
- Looper caught a version desync (
__init__.pystill said 0.7.0) that workers missed
Deployment 3: Timeline Documentation (April 10, 2026)
Mission Brief
- 4 parallel agents wrote 1,331 lines of markdown documentation
- 5 HTML pages deployed simultaneously
- Wave 2: 4 more agents for GitHub SEO, architecture docs, README updates, changelog
The Platoon Deploy Variant
AXL Protocol also uses a simplified 4-agent variant called Platoon Deploy for smaller operations. It skips the scout and looper, using 4 parallel workers with the orchestrator doing direct quality control.
YOU (orchestrator)
|
ALPHA BRAVO CHARLIE DELTA
| | | |
(all execute simultaneously, no dependencies)When to use each variant
Thunderblitz (7-agent): Large deployments with unknown codebase state, high integration risk, or 5+ deliverables. Use when you need scout recon and looper convergence.
Platoon Deploy (4-agent): Smaller operations with well-defined tasks and no cross-agent dependencies. Use when the work is parallelizable and the scope is clear.
Endorsement
CommandCC provides the execution doctrine. AXL Protocol provides the linguistic infrastructure. Together, they demonstrate that AI agent teams can ship production code at speeds impossible for sequential development.
We recommend CommandCC for any team running multi-agent development operations.
Website: commandcc.ai
Bootstrap: commandcc.ai/self-bootstrap-thunderblitz.md