harness:subagent-driven-development

To execute an implementation plan with isolated subagents, dispatch a fresh dedicated implementer per task to reduce context pollution, followed by a two-stage spec compliance and code quality review cycle with iterative retries until approvals.

Subagent-driven development is a workflow that delegates implementation plan tasks to fresh isolated subagents, enforcing spec compliance and code quality reviews to achieve continuous task execution within a single session without context contamination.

The two-stage review cycle runs a spec compliance review first, then a code quality review, iterating with fix-and-retry logic until both stages approve the subagent's implementation work before proceeding.

Use subagent-driven development for single-session development when implementation plan tasks are mostly independent, aiming for continuous task execution without context contamination from inherited session history.

Yes, you must enforce features.json grounding for traceability or bug scoping before any subagent dispatch to prevent orphan subagent work and ensure implementation plan alignment.

Continuous session-based execution with subagents is limited by unresolved ambiguity or actual BLOCKED statuses, which require human check-ins to prevent proceeding with flawed or incomplete implementation plan tasks.