tdd
TDD
Purpose
Use strict red-green-refactor in small, behavior-focused increments. Write a failing test before writing the code that makes it pass.
When To Use
- Implementing new behaviour.
- Modifying existing behaviour.
- Fixing a bug (reproduce the bug with a test before fixing).
- Anything that could potentially alter publicly observable behaviour.
Do not use for purely declarative changes (configuration, styling, documentation, or static content).
Interaction Contract
- Align with the user before the first test in a sequence.
- Check in at decision boundaries: interface changes, new behavior branch, test strategy shifts, or non-trivial refactors.
More from goblindegook/skills
grill-me
Use when user wants to stress-test an idea or plan, review a design, or says "grill me".
10rca
Use when asked for RCA, 5-Whys, postmortem, causal-tree analysis, or help identifying root causes for incidents, defects, outages, delays, or quality regressions.
10roundtable
Review a project or feature from the point of view of a set of personas. Use this when the user asks for multi-perspective critique — "review from the POV of X, Y, Z", "what would a [role] think of this?", "roundtable review", "get different perspectives on this". Each persona reads the actual source code before commenting, then all personas discuss together to agree on a prioritised top 5 list. If no personas are provided, ask the user and offer suggestions.
4test-desiderata
Critiques and scores a project's test suite against Kent Beck's 12 test desiderata, assigning a 1–5 score to each property and surfacing the top 3 highest-impact improvements. Use this skill whenever the user wants to evaluate test quality, audit their test suite, understand what makes tests good, or get actionable feedback on how to improve their tests. Trigger on phrases like "review my tests", "how good are my tests", "test quality", "test audit", "improve my test suite", "evaluate my tests", "rate my tests", "Kent Beck", "test desiderata", or any request to assess or grade tests.
1