Subagent-Driven Development FAQs

Question 1

How does this differ from standard plan execution?

Accepted Answer

Unlike standard execution, SDD uses a fresh subagent for every task to prevent context drift and enforces a mandatory code review gate before moving to the next item in the plan.

Question 2

How does it handle errors found during code review?

Accepted Answer

If a code reviewer subagent identifies critical issues, the skill dispatches a follow-up subagent to fix the specific problems before marking the task as complete.

Question 3

What is Subagent-Driven Development?

Accepted Answer

It is an AI workflow where a primary agent manages the execution of a plan by dispatching specialized subagents to handle specific tasks, ensuring clean context and quality control.

Question 4

When should I avoid using Subagent-Driven Development?

Accepted Answer

Avoid using this skill if your tasks are extremely tightly coupled or if the underlying development plan requires further brainstorming and revision before execution.

Question 5

Does this skill require other plugins or skills?

Accepted Answer

Yes, it is designed to integrate with the 'writing-plans' skill for plan creation and the 'requesting-code-review' skill for the quality gate phase.

Subagent-Driven Development

Key Features

Use Cases

Subagent-Driven Development

Key Features

Use Cases