subagent-driven-development

To delegate tasks without context bleed, assign each task to a fresh subagent with isolated context. This enforces clean boundaries and enables parallelizable workflow design for rapid iteration on large features.

The two-stage review flow is a gated quality assurance process that checks spec compliance first, followed by code quality. It ensures generated code meets master plan requirements before passing delivery gates.

Manage task lifecycles by using standardized prompts to assign tasks to fresh subagents. This orchestration method enforces per-task isolation and sequential spec and quality checks until all tasks pass.

Yes, subagent orchestration suits large feature work with many independent tasks. It delegates each task to an isolated subagent, keeping them aligned with a master plan through gated handoffs and reviews.

Using isolated subagents prevents cross-contamination of context during code review and task execution. This approach enforces per-task isolation, enabling rapid QA and reliable delivery without context bleed.

Avoid parallelizable subagent workflows for tasks lacking clear independence or spec boundaries. The orchestration relies on per-task isolation and gated handoffs, which requires tasks to be distinctly separable to function properly.