Subagent-Driven Development FAQs

Question 1

How does the two-stage review process work?

Accepted Answer

Every task completed by a subagent must pass two distinct reviews: first, a spec reviewer ensures all requirements are met; second, a code quality reviewer approves the implementation standards.

Question 2

When should I use this skill instead of standard execution?

Accepted Answer

Use this skill when you have a detailed implementation plan with mostly independent tasks and want to maintain high quality standards without manually reviewing every line during the process.

Question 3

Is it more expensive to run than manual coding?

Accepted Answer

While it involves more subagent invocations, it significantly reduces the cost of long-term maintenance and debugging by catching specification gaps and quality issues immediately.

Question 4

What is Subagent-Driven Development (SDD)?

Accepted Answer

SDD is a workflow that uses specialized sub-sessions to handle individual tasks from a development plan, ensuring high focus and preventing context pollution in the main session.

Question 5

Does this skill support Test-Driven Development?

Accepted Answer

Yes, subagents are instructed to follow TDD principles for each task, implementing, testing, and self-reviewing before submitting code for the formal two-stage review.

Subagent-Driven Development

Key Features

Use Cases

Subagent-Driven Development

Key Features

Use Cases