What problem does it solve?
Keeps project execution state consistent and auditable by ensuring every plan completion is recorded, progress is recalculated, and git history reflects successful plan work. It prevents lost progress, inflated completion counts, and ambiguous wave/phase status during parallel agent runs.
Core Features & Use Cases
- Atomic plan commits: Create one git commit per successful plan using a strict Conventional Commits format to make changes traceable.
- State and roadmap updates: Read, update, and write .planning/STATE.md and .planning/ROADMAP.md to reflect plan, wave, and phase outcomes without modifying plan output files.
- Robust failure handling: Record failed and partial plans without incrementing completed counts, report blocked waves, and provide recovery guidance for reruns.
- Optional memory recording: Write outcome summaries to .planning/memory when available and include adapter commit signatures when present.
- Use case: Run during /legion:build to coordinate parallel agent results, update progress bars across phases, and produce an auditable git history.
Quick Start
Run /legion:build and have the execution-tracker update .planning/STATE.md and .planning/ROADMAP.md while producing an atomic git commit for each successful plan.
