What problem does it solve?
Batch mechanics orchestration solves the challenge of implementing multiple unimplemented game mechanics efficiently by coordinating an agent-team workflow that groups related tasks, plans each group with review loops, and executes sequentially with post-implementation verification.
Core Features & Use Cases
- Phase 1 — Group & Classify: Read UNIMPLEMENTED-MECHANICS.md, group items by relevance, and identify dependencies.
- Phase 2 — Plan (Parallel Teammates): Spawn planning teammates, create detailed implementation plans, and run a plan-review loop with up to three rounds for gaps.
- Phase 3 — Execute (Sequential by Default): Implement approved plans one group at a time, re-read affected files before changes, and ensure compilation after each step.
- Phase 4 — Post-Implementation Verification: Lead reviews the teammate's work, performs run-commands for verification, updates planning docs, and commits changes.
- Phase 5 — Cleanup: Verify overall health with repository-wide tests and clean up planning state.
Quick Start
Invoke the batch-mechanics skill to orchestrate planning, execution, and verification for the unimplemented mechanics listed in UNIMPLEMENTED-MECHANICS.md.
