Test-driven development for factory builders. An agent skill from DanMcInerney/architect-loop.

MITAuto-check passedTesting & QA

Install TDD

skills CLI
$ npx skills add DanMcInerney/architect-loop --skill tdd -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install DanMcInerney/architect-loop tdd --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/DanMcInerney/architect-loop.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tdd .claude/skills/tdd && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tdd
GitHub stars
626
Token cost
~730 tokens
SKILL.md length
393 words
Files
3
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Test-driven development for factory builders. An agent skill from DanMcInerney/architect-loop.

  • A ship job implements at the issues pre-agreed seams — the red - green loop
  • SKILL.md covers Seams are pre-agreed, not…, What a good test is, Anti-patterns and Rules of the loop, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • One test then one minimal implementation per cycle

What it does

TDD is an agent skill from DanMcInerney/architect-loop. Test-driven development for factory builders. Use when a ship job implements at the issue's pre-agreed seams — the red - green loop, one test then one minimal implementation per cycle, never a refactor while RED.

Its SKILL.md is about 730 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `mocking.md` and `tests.md`).

It sits in Testing & QA, covering Test-driven development and Refactoring. The repository describes itself as: Super optimized /goal loop. Massive token savings and higher quality. Smart model designs and reviews, cheaper model builds.. The licence is MIT.

When your agent uses it

  • A ship job implements at the issues pre-agreed seams — the red - green loop
  • One test then one minimal implementation per cycle
  • Never a refactor while RED

Example prompts

  • “/tdd”

What it can do on your machine

Read from SKILL.md and the folder at commit 28dca7d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

TDD loads about 730 tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 393 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~54
When it runs · the whole SKILL.md, loaded when a task matches
~730

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from DanMcInerney/architect-loop at commit 28dca7d, republished under its MIT licence (© DanMcInerney). 393 words, ~730 tokens.

Download SKILL.mdSave it as .claude/skills/tdd/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
tdd
description
Test-driven development for factory builders. Use when a ship job implements at the issue's pre-agreed seams — the red -> green loop, one test then one minimal implementation per cycle, never a refactor while RED.
<!-- Adapted from mattpocock/skills (MIT). -->

Test-Driven Development

TDD is the red -> green loop. This skill is the reference that makes that loop produce tests worth keeping. Consult it before and during the loop, not after. Name things with the codebase-design vocabulary (skills/codebase-design/SKILL.md), preloaded beside this skill.

Seams are pre-agreed, not interviewed

A seam is the public boundary you test at — the interface where you observe behavior without reaching inside. In this factory the seams are already agreed before you start: they're named in the issue body and the spec. A builder never interviews a user to find seams; if an issue names none, that's a spec gap to report, not a prompt to go ask someone.

Frozen checks under docs/checks/ are read-only grading — not your tests. They verify the slice from outside, after the fact. Write your own tests at the issue's named seams and run them yourself before you report. A green frozen check with no tests of your own is not done.

What a good test is

Tests verify behavior through the seam, not implementation details. A good test reads like a specification and survives refactors because it doesn't care about internal structure. See tests.md for examples and mocking.md for mocking guidance.

Show full SKILL.md (194 more words)Show less

Anti-patterns

  • Implementation-coupled — mocks internal collaborators, tests private methods, or verifies through a side channel. Tell: it breaks on refactor with no behavior change.
  • Tautological — the assertion recomputes the expected value the way the implementation does, so it passes by construction. Expected values come from an independent source: a known-good literal, a worked example, the spec.
  • Horizontal slicing — writing every test first, then all implementation. Work in vertical slices instead: one test -> one minimal implementation -> repeat, each test a tracer bullet answering what the last cycle taught you.

Rules of the loop

  • Red before green. Write the failing test first, then only enough code to pass it. Don't anticipate future tests or add speculative features.
  • One slice at a time. One seam, one test, one minimal implementation per cycle.
  • Never refactor while RED. Refactoring belongs to review, not the red -> green cycle.
  • Mock at system boundaries only — external systems, time, randomness. Never your own modules.

Report only what you proved

Evidence-ground every claim: report only what a tool result from this session actually shows — the command output and exit code from a test you ran, not a claim of passing without the run behind it.

© DanMcInerney, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files in skills/tdd of DanMcInerney/architect-loop.

  • SKILL.md
  • mocking.md
  • tests.md

Open the folder on GitHubat commit 28dca7d

Compare with similar skills

TDD next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

TDD compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
TDD this skillDanMcInerney/architect-loop626—~730Automated safety check: PassMIT
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph11211 repos~2.4kAutomated safety check: PassNone
TDD Methodoly Expertthedaviddias/skill-check190—~2.2kAutomated safety check: PassMIT
Implementgenkovich/sdd171—~2.5kAutomated safety check: PassMIT
TDD Workflowaffaan-m/ECC275k1 repos~2.6kAutomated safety check: PassMIT
Fixjvm-skills/jvm-skills140—~695Automated safety check: PassApache-2.0

Similar skills

  • TDD Workflow

    hellangleZ/burn-in-cceverywhere-ralph

    A skill your agent uses when writing new features, fixing bugs, or refactoring code.

    112 GitHub starsUsed in 11 repos~2.4k tokens
    Testing & QAAuto-check passed
  • TDD Methodoly Expert

    thedaviddias/skill-check

    A skill your agent uses when implementing features or fixing bugs with strict Test-Driven Development (TDD).

    190 GitHub stars~2.2k tokensUpdated 4 mo ago
    Testing & QAAuto-check passed
  • Implement

    genkovich/sdd

    A skill your agent uses to implement a feature from its tasks.json with test-driven development — writes a failing test first, makes it pass, refactors, gates, and commits per task.

    171 GitHub stars~2.5k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed
  • TDD Workflow

    affaan-m/ECC

    Yeni özellikler yazarken, hata düzeltirken veya kod refactor ederken bu skill'i kullanın.

    275k GitHub starsUsed in 1 repo~2.6k tokens
    Testing & QAAuto-check passed
  • Fix

    jvm-skills/jvm-skills

    Fix a bug or missing feature using TDD — write failing test first, then fix, refactor, verify, beautify.

    140 GitHub stars~695 tokensUpdated 1 mo ago
    Testing & QAAuto-check passed
  • Test Driven Development

    dzhalaevd/Donatello

    Use as a workflow overlay when implementing any feature, bugfix, refactor, or behavior change before writing production code

    135 GitHub stars~1.1k tokensUpdated 5 days ago
    Testing & QAAuto-check passed

More from DanMcInerney/architect-loop

All 11 skills in this repo
  • Architect Research

    DanMcInerney/architect-loop

    A skill your agent uses when the user asks for discovery-scale research that informs a decision: brainstorming a project or feature, choosing a technology, or requests like "research X", "what's the…

    626 GitHub stars~2.3k tokensUpdated 25 days ago
    Auto-check passed
  • Adversarial Review

    DanMcInerney/architect-loop

    A skill your agent uses when the architect factory orchestrator dispatches a fresh strategist subagent to harden a draft spec: falsify it with file:line evidence, fold the surviving findings into a…

    626 GitHub stars~1.1k tokensUpdated 25 days ago
    Auto-check passed
  • Architect

    DanMcInerney/architect-loop

    A skill your agent uses when the user asks to architect, run or continue the autonomous software factory, turn a goal into a hardened tracker issue plan, dispatch builder jobs, grade finished work…

    626 GitHub stars~2.5k tokensUpdated 25 days ago
    Auto-check passed
  • Architect Fast

    DanMcInerney/architect-loop

    A skill your agent uses when the user asks to architect-fast a change, run the light factory lane, or factory-build a small goal — a few files, roughly one sitting, at most ~3 parallel issues — into…

    626 GitHub stars~1.9k tokensUpdated 25 days ago
    Auto-check passed
  • Final Review

    DanMcInerney/architect-loop

    A skill your agent uses for the closing whole-run review in the architect factory — the only model review in the loop: dispatched by the orchestrator, at finish, to one fresh strategist subagent…

    626 GitHub stars~1.7k tokensUpdated 25 days ago
    Auto-check passed
  • Frozen Checks

    DanMcInerney/architect-loop

    A skill your agent uses when the strategist drafts per-issue graded checks after decomposition and before builder dispatch.

    626 GitHub stars~816 tokensUpdated 25 days ago
    Auto-check passed

Categories

Questions about TDD

What does TDD do?

Test-driven development for factory builders. An agent skill from DanMcInerney/architect-loop. TDD is an agent skill from DanMcInerney/architect-loop. Test-driven development for factory builders.

When should I use TDD?

TDD fits situations like: A ship job implements at the issues pre-agreed seams — the red - green loop; one test then one minimal implementation per cycle; never a refactor while RED.

How do I install TDD in Claude Code?

Run `npx skills add DanMcInerney/architect-loop --skill tdd -a claude-code`. Or copy the skill folder (skills/tdd in DanMcInerney/architect-loop) into .claude/skills/tdd in your project. Claude Code loads it when a task matches its description.

How do I install TDD in Codex?

Run `npx skills add DanMcInerney/architect-loop --skill tdd -a codex`. Or copy the skill folder (skills/tdd in DanMcInerney/architect-loop) into .agents/skills/tdd in your project. Codex loads it when a task matches its description.

Can I use TDD in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add DanMcInerney/architect-loop --skill tdd -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tdd, .gemini/skills/tdd, .github/skills/tdd and .opencode/skills/tdd in your project.

What does TDD need to run?

SKILL.md names no scripts, command-line tools or credentials: TDD is instructions for the agent only.

Does TDD access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is TDD safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does TDD use?

TDD is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does TDD use?

About 730 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to TDD?

Skills that share tags, products or a category with TDD: TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars), TDD Methodoly Expert (thedaviddias/skill-check, 190 stars), Implement (genkovich/sdd, 171 stars) and TDD Workflow (affaan-m/ECC, 275k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains TDD?

DanMcInerney (a GitHub user) maintains it in DanMcInerney/architect-loop, which has 626 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 13, 2026.

Source: DanMcInerney/architect-loop on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.