Plan Execution & TDD Runner FAQs

Question 1

Does this skill require Test-Driven Development?

Accepted Answer

Yes, TDD is mandatory by default. This ensures every task is verified by tests before completion, unless the task is explicitly exempt, such as documentation or configuration updates.

Question 2

How do I start the execution process?

Accepted Answer

The skill is typically triggered after using 'harness:writing-plans'. You announce the use of the skill and choose between Subagent or Batch mode based on your session requirements.

Question 3

What is the difference between Subagent and Batch mode?

Accepted Answer

Subagent mode operates within the same session using isolated processes for faster iteration, while Batch mode is designed for separate sessions and complex changes requiring human feedback between tasks.

Question 4

Can I use this skill for refactoring?

Accepted Answer

Absolutely. It is highly effective for refactoring as it manages task context isolation and ensures that existing or new tests pass at every stage of the execution plan.

Question 5

How does it handle code quality?

Accepted Answer

The skill utilizes a multi-stage review process involving specialized subagents for both specification compliance and code quality audits, ensuring the output meets project standards.

Plan Execution & TDD Runner

Key Features

Use Cases

Plan Execution & TDD Runner

Key Features

Use Cases