subagent-development

Automate plan-driven development by dispatching dedicated subagents per task to execute complex plans with isolated context. This approach reduces context leakage and ensures quality through sequential spec-compliance and code-quality reviews.

A two-stage review workflow for subagent development enforces a sequential spec-compliance review followed by a code-quality review. This ensures independent task execution meets specifications and maintains high code standards before completion.

Prevent context leakage by dispatching fresh, dedicated subagents per task. This per-task isolation keeps independent development tasks separate, reducing cross-task contamination and maintaining clean execution environments.

Subagent workflows are applicable to plan-driven development where tasks are largely independent. If your complex plan involves heavily dependent tasks, the per-task isolation and two-stage review design may not suit your context.

The best way to break a development plan into discrete tasks is using a plan-to-execution workflow that automates clear ownership and traceability. Each task then spawns a fresh subagent for isolated execution and review.

Spec compliance failures occur when the two-stage review process identifies gaps between task execution and plan specifications. The sequential review enforces spec compliance before proceeding to the final code-quality check.