Fireteam uses different execution strategies based on task complexity. Each mode balances thoroughness against efficiency.
SINGLE_TURN → Execute (one-shot)
MODERATE → Execute → Review → loop until ≥95%
FULL → Plan → Execute → 3 Reviews → loop until 2/3 say ≥95%
For: Trivial and simple tasks like typo fixes, adding comments, simple bug fixes
Behavior:
- Single CLI call
- Full tool access
- No review phase
- Fastest execution
fireteam run -m single_turnFor: Tasks requiring verification but not extensive planning
Behavior:
- Execute phase with full tools
- Single review after execution
- Loops until reviewer says ≥95% complete
- Feedback from reviews flows to next iteration
fireteam run -m moderateFor: Complex tasks requiring planning and thorough validation
Behavior:
- Planning Phase: Analyze goal, explore codebase, create implementation plan (once at start)
- Execution Phase: Implement according to plan
- Review Phase: 3 parallel reviewers assess completion
- Loop: Continue until 2 of 3 reviewers say ≥95% complete
fireteam start -m fullRunning 3 reviewers in parallel and requiring 2/3 agreement:
- Reduces false positives from a single biased review
- Provides diverse perspectives on completion
- Catches issues one reviewer might miss
- More robust than single-reviewer assessment
Fireteam uses a dual-gate system to determine when a task is complete:
- Reviewer Gate: Reviewers must say ≥95% complete
- Executor Gate: Executor can signal
WORK_COMPLETE: falseto continue even if reviewers are satisfied
This respects Claude's judgment - if the executor believes more work is needed, iteration continues.
Let Fireteam choose based on complexity estimation:
fireteam start # Mode auto-detected from task complexityForce a specific mode:
# Be thorough with a simple task
fireteam start -m full
# Be quick with a moderate task
fireteam start -m single_turnBy default, MODERATE and FULL modes loop indefinitely until completion. Set a limit:
fireteam start --max-iterations 10| Phase | Tools Available |
|---|---|
| Planning | Glob, Grep, Read (read-only) |
| Execution | Read, Write, Edit, Bash, Glob, Grep |
| Review | Glob, Grep, Read (read-only) |
Planners and reviewers have read-only access to prevent unintended modifications during analysis phases.