test-driven-development
/test-driven-development
Use when implementing a high-risk behavior change, reproduced regression, or costly contract. Do NOT use by default for docs, styling, config, or low-risk wiring.
- Author
- tsergeytovarov ↗
- Repository
- ai-settings ↗
- Licence
- MIT
- Last repository change
- 14.10.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when implementing a high-risk behavior change, reproduced regression, or costly contract. Do NOT use by default for docs, styling, config, or low-risk wiring.
Original author description
Use when implementing a high-risk behavior change, reproduced regression, or costly contract. Do NOT use by default for docs, styling, config, or low-risk wiring.
How it works
- Decision
- Critical TDD Cycle
- Existing Code or Impractical Automation
- Completion
SKILL.md preview
--- name: test-driven-development version: 6.2.0 category: workflow description: Use when implementing a high-risk behavior change, reproduced regression, or costly contract. Do NOT use by default for docs, styling, config, or low-risk wiring. --- # Risk-Based Test-Driven Development TDD protects critical behavior. It is not a requirement to create a test for every changed function. Read `../using-superpowers/references/risk-policy.md` and classify the change. ## Decision | Risk | New test | |---|---| | Low | None by default; use a focused check or smoke path | | Medium | Only for a key outcome, non-obvious branch, or hard-to-notice regression | | High | One minimal regression or contract test first when practical | Do not test private helpers, trivial branches, static rendering details, or behavior already covered through a public seam. ## Critical TDD Cycle For a warranted test: 1. Write the smallest test that describes the critical observable behavior. 2. Run it and confirm it fails for the expected missing behavior. 3. Implement the smallest production change. 4. Run the focused test and the affected suite once. 5. Refactor only if needed, then rerun the closest affected target. Mocks are limited to external boundaries. Prefer real in-process behavior. ## Existing Code or Impractical Automation Do not delete completed code merely because the test was not written first. Add a focused regression test when it materially protects the outcome. If automation is disproportionately expensive or impossible, record and run a reproducible smoke check instead. ## Completion - Every check that was run must pass. - A passing focused test does not justify running unrelated suites. - State what was verified and what was intentionally not tested.
Files in this package (3)
- CHANGELOG.md 1 KB
- SKILL.md 2 KB
- writing-good-tests.md 8 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · tsergeytovarov/ai-settings | 90 | MIT |
| GanyuanRan/Aegis | 100 | MIT |
| lucasouzadev/agent-kit-skill | 100 | MIT |
| zeative/satgas | 100 | AGPL-3.0 |
| nikospavlopoulos/devops-mutant-powers | 100 | MIT |
| JohnStrunk/CommonCast | 100 | LGPL |
| Sanit-mann/The-Insectoids | 100 | MIT |
| mastro993/fstack | 100 | MIT |
| jelvodev/yaap | 100 | MIT |
Database snapshot: 13.11.2026 · package version 5b778e411956 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100test-driven
Test-Driven Development (TDD) across any supported language. Use when implementing features or fixes with TDD methodology, writing tests before code, or following XP-style development. - 90test-first-development
Apply test-first discipline for behavior changes and bugfixes: define expected behavior, add or run a failing test, then implement minimally. Use when fixing bugs, changing logic, or adding features that need regression protection. Triggers: "bugfix", "TDD", "regression test",… - 96sr-test-driven-development
Use when implementing any feature or bugfix, before writing implementation code - 90tdd
AI DevKit · Test-driven development — write a failing test before writing production code. Use when implementing new functionality, adding behavior, or fixing bugs during active development. - 100behavior-driven-development
Applies behavior-driven development principles including Gherkin scenarios and test-driven development. This skill should be used when the user asks to implement features, fix bugs, or when writing executable specifications and tests before writing production code.