skill
054-design-tdd
Use when Java implementation work should be guided by Test-Driven Development, including maintaining a test list, choosing the next behavior, writing a failing test first, implementing only enough production code to pass, and refactoring while keeping tests green. This should trigger for requests such as Apply TDD; Use test-driven development; Drive this Java change with tests; Write the failing test first; Red-green-refactor this feature. Part of Plinth Toolkit
Description as published by the maintainer. Source
- active
active — Most recent push to the repository was 2026-08-02.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 423 | Stars on the repository that contains this skill, not on the skill itself. A collection of fifty skills shares one number, so it says nothing about this particular skill. | cumulative, all time | GitHub | |
| Last commit | 2026-08-02 | Most recent push to the containing repository. It may reflect work on a different skill in the same collection. | point in time | GitHub | |
| repository status | active | The repository holding this skill exists and is not archived. | as of fetch | GitHub |
Will this work with your setup?
Install location suggests this is meant for claude-code. The author tagged this repository "claude-code-skills" on GitHub. That is their statement of intent, not a test result.
We have not run this skill against a task with and without it enabled, so we cannot tell you whether it improves anything, what it costs in tokens, or whether it duplicates behaviour your harness already has. When we have run that test, the result will appear on this page with the task, the versions and the budget it used.
The skill definition lives at skills/054-design-tdd/SKILL.md in https://github.com/jabrena/plinth.
Where to get it
Also from jabrena
-
jabrena-plinth-001-commands-inventory
— last commit 2026-08-02
Use when you need to generate a checklist document with embedded commands inventory, following the embedded template ex…
-
jabrena-plinth-002-agents-inventory
— last commit 2026-08-02
Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exac…
-
jabrena-plinth-003-skills-inventory
— last commit 2026-08-02
Use when you need to generate a checklist document with Java system prompts from skills.xml, following the embedded sec…
-
jabrena-plinth-004-commands-installation
— last commit 2026-08-02
Use when you need to install the embedded project commands into command directories (.github/commands, .claude/commands…
-
jabrena-plinth-005-agents-installation
— last commit 2026-08-02
Use when you need to install the embedded robot agents into .github/agents, .claude/agents, .cursor/agents, or .codex/a…
-
jabrena-plinth-012-agile-epic
— last commit 2026-08-02
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakd…
-
jabrena-plinth-013-agile-feature
— last commit 2026-08-02
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an…
-
jabrena-plinth-014-agile-user-story
— last commit 2026-08-02
Guides the creation of agile user stories. Use when the user wants to create a user story. This should trigger for requ…
-
jabrena-plinth-021-problem-framing
— last commit 2026-08-02
Use when a problem or issue needs explicit framing before deeper analysis begins — establishing the Problem statement,…
-
jabrena-plinth-022-root-cause-analysis
— last commit 2026-08-02
Use when a framed problem needs root-cause investigation rather than a symptom-level fix, applying Five Whys, Fishbone…
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab