Test Driven Development
Use when implementing any feature or bugfix, before writing implementation code. Observe the required behavior first. Do not use it to keep a green suite that encodes the wrong object, to write tests after the code, or to ship production code without a failing test.
Install
npx skills add jeremybrasher/grokbot-skills --skill test-driven-developmentgit clone --depth 1 https://github.com/jeremybrasher/grokbot-skills.git /tmp/grokbot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/grokbot-skills/skills/test-driven-development ~/.claude/skills/test-driven-developmentPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Test-Driven Development (TDD) ## Overview Write the test first. Watch it fail. Write minimal code to pass. **Core principle:** If you didn't watch the test fail, you don't know if it tests the right thing. **Violating the letter of the rules is violating the spirit of the rules.** ## When to Use **Always:** - New features - Bug fixes - Refactoring - Behavior changes **Exceptions (ask your human partner):** - Throwaway prototypes - Generated code - Configuration files Thinking "skip TDD just this once"? Stop. That's rationalization. **Do not use this to:** - Write tests after the production code already exists (that is verification, not TDD) - Keep a green suite that encodes the wrong object - Add coverage for its own sake - Explore a design you intend to throw away (spike first, then start over with TDD) - Produce a test plan, a coverage report, or a testing strategy document ## Intake — before RED You need three things. Nothing else starts. Do not write a test. Do not write production code. 1. **A named required behavior.** What should the system do, for whom, after this change? "Add tests," "make it work," or "cover this file" is not enough. 2. **A way to tell the object is wrong.** A concrete failure a user would see, or a production change that would be a bug if it shipped. If you cannot name what would be wrong if we shipped without this, you do not have a requirement.
Details
- Skill name
test-driven-development- Repository
- jeremybrasher/grokbot-skills
- Path
skills/test-driven-development/SKILL.md- Repo updated
- 15 September 2026
FAQ
What does the Test Driven Development skill do?
Use when implementing any feature or bugfix, before writing implementation code. Observe the required behavior first. Do not use it to keep a green suite that encodes the wrong object, to write tests after the code, or to ship production code without a failing test.
How do I install the Test Driven Development skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jeremybrasher/grokbot-skills --skill test-driven-development. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Test Driven Development popular?
It lives in jeremybrasher/grokbot-skills, which has 38 GitHub stars and 11 forks.
Related skills
Anti Patterns
38jeremybrasher/grokbot-skills
Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
Anydesign
38jeremybrasher/grokbot-skills
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t
Archetype Review Base
38jeremybrasher/grokbot-skills
Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.
Typescript Best Practices
38jeremybrasher/grokbot-skills
TypeScript best practices. Use when reading or editing any .ts or .tsx file. Observe required inputs first; HOLD when they are missing rather than guessing.
Systematic Debugging
38jeremybrasher/grokbot-skills
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Observe the failure first. Do not use it to implement an already-approved design, to add a feature with no failing behavior, or to guess a root cause from a one-line complaint.
Well Architected
38jeremybrasher/grokbot-skills
6-pillar architecture review framework. Adapted from AWS Well-Architected for use by great_cto's architect agent on every non-nano ARCH document. Forces explicit answers across operational excellence, security, reliability, performance, cost, and sustainability — not just feature design.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.