Workflow: Delegated Implementation

Phase-2 delegation strategy. When scope or complexity warrants it, the orchestrator groups related file changes, dispatches each cohesive group to a focused code-impl sub-agent, and consumes a concise verification summary instead of re-reading changed files. This keeps the orchestrator context lean and enables safe sequential (or opt-in parallel) execution.

Announce at start: "I'm using workflow-delegated-implementation to delegate [N] change groups to code-impl."

When to invoke

Delegate when any of the following is true:

Condition	Threshold	Rationale
File count	> 5 distinct files	Reading every diff fills orchestrator context
Module count	> 2 distinct modules/packages	Cross-module reasoning benefits from focused agents
Dependency depth	Changes span ≥ 2 dependency layers	Isolated agents reduce reasoning surface
Complexity	Non-trivial logic in ≥ 2 separate concerns	Each concern deserves focused attention
Explicit request	Orchestrator decides delegation is cleaner	Orchestrator judgment overrides thresholds

Not gated by task type — delegation applies equally to features, fixes, and refactors.