todo-implement

Automated code implementation from a TODO backlog is orchestrated by reading task files, sequencing items by priority, and dispatching dedicated subagents to write and review the code changes. It sequences work, gates commits, and records completion status back into the todo files.

Enforcing code review before a git commit is handled by dispatching an independent reviewer subagent that evaluates the implementation. The system only stages item-related changes and commits if the reviewer verdict is APPROVED, otherwise blocking the commit and triggering fix rounds.

Blocked TODO items during task orchestration are skipped to maintain workflow momentum. The system records the specific block reasons back into the todo markdown files and supports multiple fix rounds, escalating to a stronger model after repeated rejection.

Batching independent TODO tasks into a single git commit is supported to improve throughput without concurrent execution. The workflow reviews and commits related independent items together, staging only the item-related changes for a single commit.

No external dependencies are required to run this task orchestration workflow. The system operates independently by managing status-driven flow, dispatching implementer and reviewer subagents, and handling dependency gating internally.