TDD Implementation Orchestrator FAQs

Question 1

What is the main role of dev-implement?

Accepted Answer

It acts as the orchestration layer for the implementation phase of development, delegating coding tasks to subagents while ensuring every change is backed by a failing test.

Question 2

How does the failure recovery protocol work?

Accepted Answer

If three consecutive implementation attempts fail to pass tests, the skill triggers a recovery protocol that reverts changes, documents the failure patterns, and consults the user for a new strategy.

Question 3

Why use subagents for implementation instead of the main chat?

Accepted Answer

Using subagents keeps the main chat's context window clean for high-level management and allows fresh agents to focus entirely on the TDD cycle for a single, specific task.

Question 4

Can the main chat write code while using this skill?

Accepted Answer

No, the skill enforces an 'Iron Law of Delegation' where the main chat manages the process and only task agents write or edit code to maintain context efficiency.

Question 5

What are the prerequisites for starting dev-implement?

Accepted Answer

Before starting, you must have a completed SPEC.md and PLAN.md that has been explicitly approved by the user, including a fully defined testing strategy.

TDD Implementation Orchestrator

Características Principales

Casos de Uso

TDD Implementation Orchestrator

Características Principales

Casos de Uso