Tdd
Test-driven development workflow for implementing features or fixing bugs through red-green-refactor. Use when the user asks to build, change, or fix behavior and the codebase has a practical automated test surface.
Install
$ agentstack add skill-ntaffzii-skill-agents-tdd ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-ntaffzii-skill-agents-tdd) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
TDD
Use this skill to make behavior changes with a tight feedback loop.
Workflow
- Clarify behavior
- Identify the user-visible behavior, input, output, and edge cases.
- Find the smallest vertical slice that proves the behavior.
- If the request is ambiguous, make a conservative assumption and state it.
- Find the test seam
- Prefer the seam closest to real behavior: integration, API, component, e2e, then unit.
- Avoid tests that only assert implementation details.
- If no useful seam exists, note that as design pressure and choose the best available signal.
- Red
- Write one failing test for the next slice.
- Run only the narrowest relevant test command first.
- Confirm the failure is for the expected reason.
- Green
- Implement the smallest change that passes the test.
- Keep changes scoped to the behavior under test.
- Do not refactor unrelated code during green.
- Refactor
- Improve clarity only after the test passes.
- Preserve behavior and rerun the relevant tests.
- Remove duplication only when it is real and local.
- Expand
- Add edge cases only after the core path works.
- Repeat red-green-refactor for each slice.
- Finish by running the broader relevant suite.
Test Quality Rules
- A good test fails before the fix and passes after it.
- Test names should describe behavior, not implementation.
- Do not mock the thing being tested.
- Prefer fixtures over hand-built objects when local patterns already use fixtures.
- Keep assertions specific enough to catch the bug or behavior contract.
Verification
- The new or changed test fails before the implementation when practical.
- The focused test command passes after the implementation.
- A broader relevant suite passes when the change touches shared behavior.
- Untested risk is named when broader validation is not practical.
Completion Report
End with:
- Behavior implemented
- Tests added or changed
- Commands run
- Any untested risk
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ntaffzii
- Source: ntaffzii/Skill-Agents
- License: MIT
- Homepage: https://github.com/ntaffzii/ai-desk-tools
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.