subagent-driven-development

To orchestrate parallel tasks without context bleed, this Skill dispatches a fresh subagent per task. This approach ensures clear focus and deterministic task boundaries by isolating execution context for each individual implementation step.

A two-stage review workflow enforces quality by first checking spec compliance, then evaluating code quality. This structured approach catches issues early through automated review gates during complex implementation plan execution.

Executing a complex implementation plan requires providing the plan to the system, which then handles automated handoffs. It dispatches per-task subagents with propagated context and built-in review gates for scalable, consistent output.

Yes, subagent-driven development applies to complex planning workflows where tasks are parallelizable. It structures execution with per-task context propagation and deterministic boundaries to ensure consistent output across large scale implementations.

You should not use a multi-subagent workflow for tasks that cannot be parallelized or lack clear boundaries. This approach requires deterministic task boundaries and spec compliance checks to function effectively without context bleed.