Subagent-Driven Development FAQs

Question 1

Is this skill suitable for highly coupled tasks?

Accepted Answer

It is best used for tasks that are mostly independent. If tasks are extremely tightly coupled or the plan requires frequent revision, manual execution or brainstorming may be more effective.

Question 2

What is the main benefit of using subagents over manual execution?

Accepted Answer

Subagents provide fresh, isolated context for every task. This prevents context pollution and hallucinations, while ensuring that Test-Driven Development patterns are followed consistently.

Question 3

Do I need a pre-existing plan to use this skill?

Accepted Answer

Yes, this skill is designed to execute plans created by the 'writing-plans' skill. It reads the plan file and converts it into a structured Todo list for execution.

Question 4

How does the automated code review process work?

Accepted Answer

After a subagent completes a task, a separate code-review-agent is dispatched to evaluate the work against requirements. It identifies critical or minor issues that must be fixed before the next task begins.

Question 5

Does using subagents increase the cost of development?

Accepted Answer

While it involves more subagent invocations, it reduces overall cost and time by catching errors early through automated reviews, preventing expensive debugging sessions later in the project.

Subagent-Driven Development

概要

主な機能

ユースケース

Subagent-Driven Development

概要

主な機能

ユースケース