SkillsAdd

tjboudreaux/cc-engineering-skills · Archived

eng-tdd

Enforces disciplined RED-GREEN-REFACTOR cycle—write failing test first, watch it fail, write minimal code to pass, then refactor.

First seen May 26, 2026

Installation

$ npx skills add tjboudreaux/cc-engineering-skills --skill eng-tdd
View on skills.sh ↗ GitHub repository ↗

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

eng-verification Same source · more installs
tjboudreaux/cc-engineering-skills

Mandatory checklist before claiming work is complete—run the evidence-producing command, inspec…

13 installs
eng-spec-driven Same source
tjboudreaux/cc-engineering-skills

Spec-driven development workflow for planning before coding with Factory

12 installs
eng-iterative-delivery Same source
tjboudreaux/cc-engineering-skills

Decompose work into safe, observable increments with feature flags, rollbacks, and communicatio…

11 installs
eng-holistic-systems Same source
tjboudreaux/cc-engineering-skills

Model the end-to-end system, constraints, and failure modes before touching code; use whenever …

11 installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
azure-diagnostics Shared topics
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs
azure-validate Shared topics
microsoft/azure-skills

Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure…

567.7K installs
supabase-postgres-best-practices Shared topics
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs

Also in this package

Other skills from tjboudreaux/cc-engineering-skills · top by installs.

npx skills add tjboudreaux/cc-engineering-skills
eng-verification 13 eng-spec-driven 12 eng-iterative-delivery 11 eng-holistic-systems 11 eng-security-safety 11 eng-rigorous-validation 11 eng-user-impact 11 eng-testing-anti-patterns 11 eng-quality-handoff 11 eng-performance 11

Browse all from tjboudreaux/cc-engineering-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,720 B
  • docs SUMMARY.md 146 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 12 installs

SKILL.md

Test-Driven Development (TDD)

Overview

Write the test first. Watch it fail. Implement just enough to pass. Refactor while staying green. If you didn’t see the test fail, you don’t know whether it tests the right behavior.

Iron Law

NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST

Wrote code before the test? Delete it. Start from tests.

When to Use

  • Every feature, bug fix, refactor, or behavior change.
  • Exceptions only with explicit human approval (throwaway prototypes, generated code, etc.).

Red-Green-Refactor Cycle

  1. RED – Write one minimal test describing desired behavior.

- Clear, specific name. - Tests real behavior (avoid unnecessary mocks).

  1. Verify RED – Run the test; confirm it fails for the expected reason.
  2. GREEN – Write the simplest code to make the test pass. No extra features.
  3. Verify GREEN – Run the test suite; ensure the new test and existing tests pass.
  4. REFACTOR – Clean up code/tests while keeping everything green.
  5. Repeat for next behavior.

Good vs Bad Tests

Good Bad
Tests one thing Vague “does work”
Clear name test1
Real behavior Asserts on mocks

Why Order Matters

  • Tests written after code pass immediately → prove nothing.
  • Manual testing isn’t reproducible evidence.
  • Keeping prewritten code “for reference” breaks TDD—delete and rebuild from tests.

Rationalization Countermeasures

Excuse Response
“Too simple” Simple code breaks—test anyway.
“I’ll test later” Tests-after confirm existing behavior, not requirements.
“Manual testing is enough” No record or rerun; automation is required.
“Deleting work is wasteful” Sunk cost; untested code is debt.
“Being pragmatic” TDD prevents debugging hell; pragmatism = reliability.

Verification Checklist

  • Every new behavior guarded by a test.
  • Saw each test fail before implementation.
  • Each failure was due to missing behavior (not typos).
  • Wrote minimal code to make each test pass.
  • Full suite green after changes.
  • Refactors done only while green.
  • Tests cover edge/error cases.

Failed any item? You skipped TDD—start over.

Integrating Bug Fixes

  • Reproduce bug with a failing test first.
  • Apply fix to satisfy the test.
  • Keep the test to prevent regressions.

Final Rule

Production code exists only alongside a test that failed before the code was written. Otherwise, redo it with TDD.