subagent-driven-development

You automate plan execution by dispatching a fresh subagent per independent task within a single session. This workflow applies context isolation and predefined prompts to ensure rapid iteration and structured code review.

The best way to maintain context isolation is dispatching a fresh subagent for each task. This ensures deterministic workflow execution and prevents context bleed during rapid iteration across multiple tasks.

Two-stage code review works by applying predefined prompts sequentially after each task dispatch. The first stage checks spec compliance, and the second stage evaluates code quality to ensure the implementation plan meets requirements.

Yes, you can use subagent dispatch for TDD workflows in a single session. The skill orchestrates rapid iteration by applying a plan-to-review flow with predefined prompts for spec compliance and code quality.

You should use subagent-driven workflow orchestration when you need to execute an implementation plan with independent tasks. It provides rapid iteration, clear progress tracking, and structured two-stage reviews within a single session.

No, plan execution with subagent dispatch requires no external dependencies. The skill operates independently by using predefined prompts and per-task dispatch to maintain spec compliance and code quality within the current session.