spectre-tdd

Automate TDD cycles with failing tests before production code.

146|15|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/Codename-Inc/spectre --skill spectre-tdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spectre-tdd
Source: https://github.com/Codename-Inc/spectre/tree/main/plugins/spectre/skills/spectre-tdd
Command: npx skills add https://github.com/Codename-Inc/spectre --skill spectre-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams enforce discipline in software development by driving decisions through a strict TDD cycle (RED → GREEN → REFACTOR). It ensures that no production code is written before a failing test exists, reducing defects and enabling safer refactors.

Core Features & Use Cases

  • IRON LAW: NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST.
  • Stepwise TDD workflow: RED phase to write failing tests, GREEN phase to implement minimal code, REFACTOR phase to clean up, and COMMIT to finalize changes.
  • Looping integration: repeats until all TOs are addressed and tests pass.

Quick Start

Begin a TDD cycle by selecting a feature and running the RED-GREEN-REFACTOR workflow to drive tests first and implement minimal code.

Frequently Asked Questions about spectre-tdd

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

FAQPage Schema
How do I enforce strict test-driven development cycles for new features?

You can enforce test-driven development cycles by applying an automated RED-GREEN-REFACTOR workflow that prevents production code creation until a failing test is written.

What is the RED-GREEN-REFACTOR workflow in TDD?

The RED-GREEN-REFACTOR workflow in TDD is a stepwise process where you write a failing test (RED), implement minimal code to pass it (GREEN), clean up the codebase (REFACTOR), and commit the changes.

How to start a TDD cycle for bug fixes?

To start a TDD cycle for bug fixes, select the target feature and run the RED-GREEN-REFACTOR workflow to drive tests first, implement minimal passing code, and loop until all tasks are addressed and tests pass.

Can I write production code before creating a failing test?

No, you cannot write production code before creating a failing test, as the TDD workflow enforces an iron law that strictly prevents production code generation without a prior failing test.

Does automated TDD workflow support continuous looping until tests pass?

Yes, the automated TDD workflow supports continuous looping integration, repeating the RED, GREEN, and REFACTOR phases until all tasks are addressed and all tests successfully pass.

When should I use an automated TDD workflow in software projects?

You should use an automated TDD workflow in software projects when TDD discipline is desired for feature development or bug fixes, ensuring code changes are consistently guided by failing tests.