implement

You can automate code generation by dispatching implementation tasks to dedicated subagents. This orchestration delegates coding work into isolated contexts, ensuring the main agent never writes implementation code directly while maintaining task governance.

TDD workflow orchestration enforces the RED/GREEN/REFACTOR cycle within isolated subagent contexts. Each task is dispatched to a dedicated subagent that executes the TDD workflow, ensuring reproducible and verifiable coding results without main agent interference.

The best way to delegate build tasks in arc-driven task management is dispatching them to per-task subagents. This prevents the orchestrator from directly implementing code and applies task governance to tasks labeled as implement, build, or execute the plan.

Yes, subagent orchestration depends on arc task descriptions, task state, and environment details. Specifying these dependencies ensures the subagents have the necessary isolated context to execute implementation tasks and produce verifiable results.

Yes, task orchestration dispatches implementation work to per-task subagents with isolated contexts. This isolation ensures each coding task operates independently, preventing context bleed and maintaining strict task governance throughout the execution lifecycle.

You should not use subagent delegation if your workflow does not follow arc-driven task management or TDD cycles. This orchestration is specifically designed for tasks labeled implement, build, or execute the plan within structured tracking systems.