jupes/agent-forge-harness / .agents/skills/tdd
tdd
VerifiedImplement behavior in red-green-refactor slices. Use for test-driven feature or bug work, or when a Forge plan calls for TDD.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.0 KB |
| deep-modules.md | markdown | 1.2 KB |
| interface-design.md | markdown | 653 B |
| mocking.md | markdown | 1.4 KB |
| refactoring.md | markdown | 387 B |
| tests.md | markdown | 1.6 KB |
SKILL.md
View on GitHub---
name: tdd
description: Implement behavior in red-green-refactor slices. Use for test-driven feature or bug work, or when a Forge plan calls for TDD.
---
# tdd
Use test-driven development to deliver features/fixes in small behavior-focused increments.
## Core principles
- Test observable behavior via public interfaces.
- Avoid coupling tests to internal implementation details.
- Work in vertical slices: one failing test -> minimal passing code -> repeat.
- Refactor only while green.
## Workflow
### 1) Plan behavior and boundaries
Before coding:
- Confirm target behavior with the user (or issue AC)
- Identify public interface changes
- Select highest-value behaviors to test first
- Spot deep-module opportunities (simple interface, deep internals)
### 2) Tracer bullet first
Create one thin end-to-end test that proves a real path.
```
RED: write one failing behavior test
GREEN: write minimal code to pass
```
### 3) Incremental red-green loop
For each next behavior:
```
RED: next failing behavior test
GREEN: minimal implementation
```
Rules:
- One test at a time
- No speculative implementation
- Keep assertions on externally visible outcomes
### 4) Refactor pass
When all current tests are green:
- Remove duplication
- Deepen modules where complexity is leaking
- Tighten names/interfaces
- Re-run test suite after each refactor step
Never refactor while red.
## Test quality checklist
- Test describes behavior (not internals)
- Test uses public interfaces only
- Test survives internal refactor
- Added code is minimal for current failing test
- No dead code or TODO placeholders
## Harness verification gates
After meaningful changes, run:
```bash
bun run typecheck
bun run lint
bun test
```
If a sub-repo defines different commands, follow that sub-repo's `AGENTS.md`.
## Beads integration
Use beads to track TDD slices:
Choose priority with [beads-priority-assignment](../beads-priority-assignment/SKILL.md) before creating work. Reuse an existing issue when it already owns the outcome.
```bash
bd create --type task --title "TDD slice: <behavior>" --description "<expected behavior and test scope>" --priority <priority> --repo .
bd comments add <id> "worklog: red->green completed for <behavior>"
```
## Deep-dive references
Bundled with this skill (self-contained — no external repos required):
- [tests.md](tests.md) — read when choosing assertions or reviewing test quality
- [interface-design.md](interface-design.md) — read when the public contract is difficult to test
- [deep-modules.md](deep-modules.md) — read when deciding where behavior belongs
- [mocking.md](mocking.md) — read when isolating external dependencies
- [refactoring.md](refactoring.md) — read when selecting a refactor after tests pass
## Attribution
The bundled deep-dive docs ([tests.md](tests.md), [interface-design.md](interface-design.md),
[deep-modules.md](deep-modules.md), [mocking.md](mocking.md), [refactoring.md](refactoring.md)) are
vendored **verbatim** from the `tdd` skill in [mattpocock/skills](https://github.com/mattpocock/skills).
This `SKILL.md` is an Agent Forge adaptation of the same concepts (Beads tracking + harness quality
gates). Original work © 2026 Matt Pocock, MIT License:
> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and
> associated documentation files (the "Software"), to deal in the Software without restriction,
> including without limitation the rights to use, copy, modify, merge, publish, distribute,
> sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is
> furnished to do so, subject to the following conditions: The above copyright notice and this
> permission notice shall be included in all copies or substantial portions of the Software.
> THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND.
## Completion
Each implemented behavior has a test observed failing for the intended reason before the fix, then passing. Record relevant regression-check results.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |