How do I install the Cm Tdd skill?

Run npx skillmds@latest add tody-agent/cm-tdd in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cm Tdd safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cm Tdd?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cm Tdd free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cm Tdd?

tody-agent (@tody-agent) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cm Tdd by tody-agent — Agent Skill

Name: Cm Tdd
Author: tody-agent

File contents

Test-Driven Development (TDD)

TL;DR

Use when writing or fixing code
Cycle: Red → Green → Refactor
Rule: no production code without a failing test first
Next: cm-execution or cm-code-review

When to Use

new features
bug fixes
refactors
behavior changes

The Iron Law

NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST

Choose the Need

Need to execute the normal TDD loop?
└─ YES → Red-Green-Refactor

Need help designing or reviewing test quality?
└─ YES → Test Quality

Need to counter "skip TDD" rationalizations?
└─ YES → Rationalizations

Need a worked bug-fix example?
└─ YES → Bugfix Example

Are you blocked or unsure how to continue?
└─ YES → Stuck / Debugging

Need	Summary	Load
Normal execution	core TDD loop and verification	`references/red-green-refactor.md`
Test quality	what good tests look like	`references/test-quality.md`
Reinforcement	anti-rationalization guidance	`references/rationalizations.md`
Example	concrete bug-fix walkthrough	`references/bugfix-example.md`
Recovery	how to proceed when stuck	`references/stuck-debugging.md`

Load Rules

Load red-green-refactor.md for normal execution.
Load test-quality.md when designing or reviewing tests.
Load rationalizations.md only when the user or agent is trying to bypass TDD discipline.
Load bugfix-example.md only for coaching or example use.
Load stuck-debugging.md only when blocked.

Non-Negotiables

Watch the test fail before writing production code.
Keep implementation minimal until green.
Refactor only after green.
Re-run verification after each meaningful change.

The Bottom Line

Write the failing test first. Pass it minimally. Refactor only after green.

---name: cm-tdddescription: Use when implementing any feature or bugfix. Routes to the core Red-Green-Refactor loop, test quality guidance, rationalization handling, examples, or stuck-state recovery.---# Test-Driven Development (TDD)## TL;DR- **Use when** writing or fixing code- **Cycle**: Red → Green → Refactor- **Rule**: no production code without a failing test first- **Next**: `cm-execution` or `cm-code-review`## When to Use- new features- bug fixes- refactors- behavior changes## The Iron Law```textNO PRODUCTION CODE WITHOUT A FAILING TEST FIRST```## Choose the Need```Need to execute the normal TDD loop?└─ YES → Red-Green-RefactorNeed help designing or reviewing test quality?└─ YES → Test QualityNeed to counter "skip TDD" rationalizations?└─ YES → RationalizationsNeed a worked bug-fix example?└─ YES → Bugfix ExampleAre you blocked or unsure how to continue?└─ YES → Stuck / Debugging```| Need | Summary | Load ||---|---|---|| Normal execution | core TDD loop and verification | `references/red-green-refactor.md` || Test quality | what good tests look like | `references/test-quality.md` || Reinforcement | anti-rationalization guidance | `references/rationalizations.md` || Example | concrete bug-fix walkthrough | `references/bugfix-example.md` || Recovery | how to proceed when stuck | `references/stuck-debugging.md` |## Load Rules- Load `red-green-refactor.md` for normal execution.- Load `test-quality.md` when designing or reviewing tests.- Load `rationalizations.md` only when the user or agent is trying to bypass TDD discipline.- Load `bugfix-example.md` only for coaching or example use.- Load `stuck-debugging.md` only when blocked.## Non-Negotiables- Watch the test fail before writing production code.- Keep implementation minimal until green.- Refactor only after green.- Re-run verification after each meaningful change.## The Bottom Line**Write the failing test first. Pass it minimally. Refactor only after green.**

Frequently asked questions

Cm Tdd