implement-orchestrator

Automating end-to-end feature delivery is handled by orchestrating planning inputs, per-story implementation, verification, and merging across isolated git worktrees. The workflow coordinates a 6-phase process from feature discovery to final merge with built-in guardrails.

Yes, you can orchestrate per-story implementation using ADO feature documents and USER_STORY files. The orchestrator reads these inputs, handles dependency graphs, and delegates coding tasks to specialized implement agents while tracking progress in a SQL-todo store.

Coordinating verification and simplification steps is managed by the orchestrator, which invokes both phases sequentially, logs pipeline events, and enforces execution discipline. It maintains traceability using SQL todos and records pipeline events throughout the process.

Specialized agents are utilized to handle dependency graphs and worktree creation during feature delivery. The orchestrator delegates per-story implementation to an implement agent, manages worktree isolation, and handles phase transitions with guardrails to enforce execution discipline.

Correction tracking and future work parking are supported through integrated parking-lot tracking mechanisms. The orchestrator logs pipeline events, records progress in a SQL-todo store, and maintains traceability for incomplete items during the 6-phase workflow.

Isolated git worktrees prevent conflicts and maintain clean separation during multi-story feature delivery. The orchestrator creates worktrees for each story, manages dependency graphs across them, and enforces phase transitions with guardrails before final merging.