tdd-cycle

Coordinate per-task TDD cycles using SPEC.md and PLAN.md inputs.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/Kohlex/autopilot-plugin --skill tdd-cycle-kohlex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-cycle
Source: https://github.com/Kohlex/autopilot-plugin/tree/main/skills/tdd-cycle
Command: npx skills add https://github.com/Kohlex/autopilot-plugin --skill tdd-cycle-kohlex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the per-task TDD lifecycle by dispatching the discipline to Superpowers and layering AutoPilot governance (commit conventions, progression tracking, and escalation) on top, so teams can move a single PLAN.md task from inception to a green, documented state.

Core Features & Use Cases

  • Thin wrapper that delegates the TDD lifecycle to Superpowers:test-driven-development while enforcing AutoPilot's pipeline discipline for commits and progression.
  • Coordinates SPEC.md and PLAN.md inputs, dispatches to /gsd-execute-phase, and updates PLAN.md and PROGRESS.yaml with outcome tracking, including escalation handling for failures.
  • Use Case: drive a capability's one unchecked PLAN.md task through RED-GREEN-REFACTOR with atomic commits and documented progress across waves.

Quick Start

Start /tdd-cycle to run the per-task TDD workflow for your current PLAN.md task.

Frequently Asked Questions about tdd-cycle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate test-driven development cycles for individual tasks in my project plan?

Automating test-driven development cycles for individual tasks involves dispatching the Red-Green-Refactor-Doc discipline to execute per-task TDD. The workflow reads SPEC.md and PLAN.md inputs, runs the TDD lifecycle, and updates PROGRESS.yaml with outcome tracking.

What is the best way to enforce conventional commit formats during TDD workflows?

Enforcing conventional commit formats during TDD workflows is handled by layering pipeline governance on top of the TDD lifecycle. Architecture lock constraints are enforced by hooks to guarantee commits meet conventional standards throughout the automation.

How do I track PLAN.md task progression and handle escalation when TDD tests fail?

Tracking PLAN.md task progression and handling escalation for TDD test failures is managed by updating PLAN.md and PROGRESS.yaml with outcome tracking. The workflow escalates failures while moving tasks from inception to a green, documented state.

Do I need specific files and plugins enabled to run automated per-task TDD?

Running automated per-task TDD requires SPEC.md and PLAN.md files to be present in your project. An enabled superpowers plugin is also required to execute the workflow and respect architecture lock constraints enforced by hooks.

When should I use workflow orchestration for test-driven development instead of manual testing?

Workflow orchestration for test-driven development should be used when moving a single PLAN.md task from inception to a green, documented state across waves. It provides atomic commits and documented progress, which is difficult to maintain manually.