subagent-driven-development

To execute implementation plans with parallel subagents, you organize tasks into dependency-safe waves where file changes do not conflict. The skill dispatches independent subagents simultaneously, then validates each wave against repository-derived build, test, and lint commands before proceeding.

Dependency-safe wave-based execution is a coordination method that dispatches parallel subagents only when their assigned file scopes are conflict-free. It ensures downstream tasks receive exact generated artifacts rather than summaries, preventing unsafe or incomplete execution across dependent implementation steps.

You validate subagent output by running spec-compliance review and project-derived validation after each wave completes. The skill requires exact task contracts and repository-derived validation commands, escalating any failures through precise correction cycles before moving to dependent work.

Yes, exact task contracts and conflict-free file scopes are required for parallel subagent execution. The plan preflight checks that all tasks have clear files, dependencies, acceptance criteria, and validation commands before implementation starts to prevent unsafe execution.

The best way to pass artifacts between dependent subagent tasks is sending exact generated artifacts directly rather than summaries. This ensures downstream work uses real contracts and schemas, maintaining integrity across dependency waves during software delivery.

Subagent-driven development requires a final acceptance audit to confirm all planned work, validations, and reviews are complete. After wave execution and correction cycles finish, a global code review ensures the complete implementation meets the approved plan's acceptance criteria.