subagent-driven-development

Context pollution occurs when a single agent accumulates state across unrelated tasks, degrading reasoning quality. Subagent-driven development spawns fresh subagents per task, isolating context and maintaining clarity. Each subagent works independently, then results are reviewed before moving to the next task, ensuring clean reasoning throughout execution.

Yes. This Skill supports wave-based parallel execution where independent tasks run simultaneously in separate subagents, with mandatory post-task code reviews. Configure sequential or parallel modes depending on your workflow, and each subagent's output undergoes review before integration, maintaining quality gates across all execution paths.

Break your plan into independent tasks without shared state or dependencies (3+ tasks ideal). Dispatch each to a fresh subagent, collect output, trigger a code review, then proceed to the next task or wave. This Skill automates the dispatch, review triggering, and reporting, with configurable sequential or parallel execution modes and final plan-level review.

Subagent-driven development embeds post-task reviews into the execution flow. After each subagent completes work, a review phase runs automatically before the next task begins. This staged approach prevents accumulation of unreviewed code and keeps iteration tight, especially effective when tasks are independent and can be executed sequentially or in parallel waves.

Use independent subagents when you have 3+ independent issues or tasks without shared state, context dependency, or coupling. Single-agent approaches accumulate context across disparate work, reducing reasoning quality. Fresh subagents per task excel in execution plans where isolation prevents pollution, task-level reporting is required, and mandatory reviews are critical for quality.

Yes. This Skill integrates commits and tests into per-task execution, supporting existing CI/CD and version control patterns. Each subagent's work is tested, committed, and reviewed before the next task, maintaining compatibility with standard development practices while enforcing isolation and quality gates.