workflow-delegated-implementation

What problem does it solve?

It solves the problem of orchestrator token/context overload when implementing multi-module, multi-concern changes that would otherwise force the main agent to re-read diffs and reason about everything at once.

Core Features & Use Cases

• Conditional delegation gating: Delegates when file/module/dependency complexity exceeds thresholds, or when the orchestrator explicitly chooses delegation.
• Cohesive change grouping: Partitions edits into Infrastructure, Core logic, Tests, and Wiring groups using module-boundary + change-together cohesion.
• Structured dispatch + result contract: Sends each group to code-impl with a strict brief (Goal, file_set, verify_cmd) and consumes only a concise verification summary to avoid re-reading changed files.
• Safe execution model: Defaults to sequential dispatch on a shared worktree, with opt-in parallelism only when disjoint file paths, no cross-group dependencies, and non-overlapping verify coverage hold.

Quick Start

Use workflow-delegated-implementation to delegate a multi-module change by asking the orchestrator to partition the edits into cohesive groups and run verify commands via code-impl while consuming only verification summaries.