Tdd workflow

Skill VoDaiLocz/kilo-kit-mcp/skills/engineering/tdd-workflow

Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.From its SKILL.md

Install

npx -y skills add VoDaiLocz/kilo-kit-mcp --skill tdd-workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

24 stars24 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.7 KB, 692 tokens by cl100k_base, as published. Nobody here has run it

TDD Workflow

Write tests first, code second.

1. The TDD Cycle

🔴 RED → Write failing test
    ↓
🟢 GREEN → Write minimal code to pass
    ↓
🔵 REFACTOR → Improve code quality
    ↓
   Repeat...

2. The Three Laws of TDD

Write production code only to make a failing test pass
Write only enough test to demonstrate failure
Write only enough code to make the test pass

3. RED Phase Principles

What to Write

Focus	Example
Behavior	"should add two numbers"
Edge cases	"should handle empty input"
Error states	"should throw for invalid data"

RED Phase Rules

Test must fail first
Test name describes expected behavior
One assertion per test (ideally)

4. GREEN Phase Principles

Minimum Code

Principle	Meaning
YAGNI	You Aren't Gonna Need It
Simplest thing	Write the minimum to pass
No optimization	Just make it work

GREEN Phase Rules

Don't write unneeded code
Don't optimize yet
Pass the test, nothing more

5. REFACTOR Phase Principles

What to Improve

Area	Action
Duplication	Extract common code
Naming	Make intent clear
Structure	Improve organization
Complexity	Simplify logic

REFACTOR Rules

All tests must stay green
Small incremental changes
Commit after each refactor

6. AAA Pattern

Every test follows:

Step	Purpose
Arrange	Set up test data
Act	Execute code under test
Assert	Verify expected outcome

7. When to Use TDD

Scenario	TDD Value
New feature	High
Bug fix	High (write test first)
Complex logic	High
Exploratory	Low (spike, then TDD)
UI layout	Low

8. Test Prioritization

Priority	Test Type
1	Happy path
2	Error cases
3	Edge cases
4	Performance

9. Anti-Patterns

❌ Don't	✅ Do
Skip the RED phase	Watch test fail first
Write tests after	Write tests before
Over-engineer initial	Keep it simple
Multiple asserts	One behavior per test
Test implementation	Test behavior

10. AI-Augmented TDD

Multi-Agent Pattern

Agent	Role
Agent A	Write failing tests (RED)
Agent B	Implement to pass (GREEN)
Agent C	Optimize (REFACTOR)

Remember: The test is the specification. If you can't write a test, you don't understand the requirement.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 2 of the 12 instructions most automation workflows skills give in 692 tokens

Counted across 813 of the 1,214 authors here whose files we hold, read 2026-09-06

Use conventional commit message formatin 38 of 813, across 34 files
Write tests before implementing codehere, and in 26 of 813, across 12 files
Achieve at least 80 percent test coveragein 24 of 813, across 11 files
Mock external dependencies for unit testsin 22 of 813, across 10 files
Read product marketing context before asking questionsin 21 of 813, across 6 files
Implement rollback plans for every deploymentin 21 of 813, across 9 files
Follow the arrange-act-assert patternhere, and in 20 of 813, across 9 files
Delete branches after mergingin 20 of 813, across 18 files
Test all edge cases and error scenariosin 20 of 813, across 8 files
Use semantic selectors for UI testsin 19 of 813, across 7 files
Define sequence type and audience contextin 18 of 813, across 5 files
Monitor feature drift and prediction distribution driftin 18 of 813, across 5 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.