implementation-orchestrator

You can automate end-to-end feature implementation by orchestrating per-TODO work in isolated git worktrees, applying test-driven development gates, and merging intermediate changes into a final reviewed pull request. This workflow requires strict guardrails like deferred user interaction until the final PR.

Multi-TODO orchestration executes each refactoring step in its own isolated git worktree, producing one integration PR per TODO. Intermediate branches merge into an integration branch, culminating in a final user-facing PR rather than a single monolithic change.

Yes, isolated git worktrees parallelize test-driven development by dispatching deterministic subagents per TODO. Each worktree applies think, implement, simplify, and review gates before committing, ensuring structured code review gating across parallel branches.

Autonomous architecture execution defers manual code review gating until the final pull request. During the implementation phase, it enforces hard rules like no questions until the final PR and no destructive git operations, keeping you out of intermediate steps.

Incremental integration branch PRs prevent monolithic changes by splitting architecture execution into reviewed, test-driven TODOs. This approach safely merges intermediate worktrees into an integration branch before opening the final PR to the trunk base.

Autonomous implementation orchestrators limit interaction by deferring user questions until the final PR and restricting remote pushes beyond PR creation. They also prohibit destructive git operations, requiring strict adherence to deterministic subagent dispatch rules.