Subagent-Driven Development FAQs

Question 1

What happens if a reviewer finds an issue?

Accepted Answer

The workflow triggers a fix-and-review loop where the implementer subagent addresses the feedback and the reviewer re-evaluates the code until all quality gates are passed.

Question 2

Can the subagents ask questions during the process?

Accepted Answer

Yes. The workflow is designed for the implementer subagent to surface questions and clarify requirements before proceeding, ensuring the work matches your specific intent.

Question 3

How does this differ from the standard 'Executing Plans' skill?

Accepted Answer

While 'Executing Plans' typically involves parallel sessions, this skill operates within your current session to maintain context while using fresh subagents per task to prevent context pollution.

Question 4

Why does this skill use a two-stage review process?

Accepted Answer

The two-stage process ensures that code is first functionally correct (spec compliance) before optimizing for maintainability and standards (code quality), preventing 'close enough' implementations.

Question 5

Does this skill support Test-Driven Development?

Accepted Answer

Absolutely. Subagents are instructed to follow TDD principles for each task, including writing tests, implementing code, and performing self-reviews before the formal review stages.

Subagent-Driven Development

Key Features

Use Cases

Subagent-Driven Development

Key Features

Use Cases