tdd-workflow
Drive a feature with a disciplined test-driven development loop — red, green, refactor. Use when implementing a feature or fixing a bug and you want tests to lead, or when asked to 'do this with TDD' / write the test first. Produces a step-by-step red-green-refactor plan: the failing test to write first, the minimal code to pass it, and the refactor — one small cycle at a time.
npx skills add mohitagw15856/pm-claude-skills --skill tdd-workflow --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# TDD Workflow Skill The failure mode of AI-assisted coding is writing a pile of code, then maybe some tests that rubber-stamp it. TDD inverts that: the test defines the behavior *first*, the code does the minimum to pass, then you refactor safely. This skill runs that loop with discipline — **one small red-green-refactor cycle at a time**, never jumping ahead to untested code. ## Required Inputs Ask for these only if they aren't already provided: - **The behavior to build** — the feature/bugfix, stated as observable behavior (input → expected output). - **The stack** — language, test framework/runner, where tests live. - **The seam** — the function/module/endpoint under test, and any collaborators to fake/mock. - **Edge cases** — the conditions that matter (errors, empty, boundaries). ## Output Format ### TDD plan: [behavior] **Behavior list** — the observable cases to drive out, ordered simplest → richest (happy path first, then edges/errors). Each becomes one cycle. Then, for **each cycle** (do them one at a time, smallest first): **🔴 Red** — the single failing test to write now (the actual test code), and *why it fails* (the behavior doesn't exist yet). One assertion of one be
- Required Inputs
- Output Format
- TDD plan: [behavior]
- Quality Checks
- Anti-Patterns
- Based On
What does the tdd-workflow skill do?
Drive a feature with a disciplined test-driven development loop — red, green, refactor. Use when implementing a feature or fixing a bug and you want tests to lead, or when asked to 'do this with TDD' / write the test first. Produces a step-by-step red-green-refactor plan: the failing test to write first, the minimal code to pass it, and the refactor — one small cycle at a time.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill tdd-workflow --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.