Skip to content
Agentmart
Submit a tool

tdd-execution

Execute behavior changes with a RED -> GREEN -> REFACTOR loop when a practical automated test path exists.

Skill by gclm

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/gclm-tdd-execution

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Execute behavior changes with a RED -> GREEN -> REFACTOR loop when a practical automated test path exists.

Use cases: testing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/tdd-execution

What's inside

Skill name
tdd-execution
Description
Execute behavior changes with a RED -> GREEN -> REFACTOR loop when a practical automated test path exists.
License
MIT
Instructions
43 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# TDD Execution

Use this skill when implementing or fixing behavior that can be proven with automated tests.

## Read First

- `protocols/tdd.md`
- `docs/overview/roadmap.md` and `harness/state.md` if they exist
- `harness/history.md` if it exists
- the closest existing tests around the target behavior

## Goals

- define the expected behavior before production edits
- create a failing proof first when practical
- implement the smallest passing change
- keep verification tightly mapped to the requested outcome

## Steps

1. Identify the exact behavior to prove.
2. Choose the narrowest practical automated test.
3. Create or update the test so it fails for the expected reason.
4. Implement the smallest change that makes it pass.
5. Run the narrowest relevant test scope first.
6. Expand verification only as needed.
7. Refactor once behavior is passing and evidence is stable.

## Exceptions

If a RED step is not practical, state why clearly and use the closest concrete evidence path available instead of pretending the work was TDD.

## Output

Report:

- target behavior
- red evidence
- green evidence
- refactor summary
- remaining gaps

From gclm/super-stack, MIT.

More from gclm/super-stack

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Mar 29, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from gclm

Cite this page

tdd-execution skill. Agent Mart. https://agentmart.dev/skills/gclm-tdd-execution (last updated 2026-10-24)