mcpField
T
tdd-workflows-tdd-green

tdd-workflows-tdd-green

github.com/sickn33Testing & quality48.7k235 installsUpdated today
Repository

About tdd-workflows-tdd-green

A skill for the Green phase of TDD, intended for developers implementing the smallest correct change for an agreed failing test. It emphasizes rerunning tests after each change, keeping scope narrow, and noting debt for later refactoring.

Key features

  1. 01Identify the smallest fix for a failing test
  2. 02Implement changes and rerun tests incrementally
  3. 03Preserve existing interfaces and security boundaries
  4. 04Record items for the refactoring phase

Use cases

  1. 01Move from Red to Green in a TDD cycle
  2. 02Satisfy the next test with minimal behavior
  3. 03Avoid bypassing tests to make them pass
  4. 04Track temporary implementation shortcuts

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill tdd-workflows-tdd-green

After installing, type/tdd-workflows-tdd-greenin Claude Code to confirm it loaded.

Bundled filesresources/implementation-playbook.md

Details

From the project README

TDD Green Phase

Implement the smallest correct behavior for an agreed failing test while preserving existing requirements, security boundaries and interfaces. Read the bundled playbook as illustrative material, not an executable tool.

Use this skill when

  • Moving from red to green in a TDD cycle
  • Implementing minimal behavior to satisfy tests
  • You want to keep implementation intentionally simple

Do not use this skill when

  • You are refactoring for design or performance
  • Tests are already passing and you need new requirements
  • You need a full architectural redesign

Instructions

  1. Review failing tests and identify the smallest fix.
  2. Implement the minimal change to pass the next test.
  3. Run tests after each change to confirm progress.
  4. Record shortcuts or debt for the refactor phase.

Safety

  • Avoid bypassing tests to make them pass.
  • Keep changes scoped to the failing behavior only.

Resources

  • resources/implementation-playbook.md for detailed patterns and examples.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Comments

Markdown supported