TDD
pietheinstrengholt/rssmonster
Test-driven development. An agent skill from pietheinstrengholt/rssmonster.
A skill your agent uses when implementing a change with test-driven development (TDD): work test-first through focused red-green cycles.
Install Test Driven Development
$ npx skills add intent-driven-dev/intent-driven-template --skill test-driven-development -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install intent-driven-dev/intent-driven-template test-driven-development --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/test-driven-development .claude/skills/test-driven-development && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "test-driven-development" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/test-driven-development into .claude/skills/test-driven-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-driven-development", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/test-driven-developmentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add intent-driven-dev/intent-driven-template --skill test-driven-development -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install intent-driven-dev/intent-driven-template test-driven-development --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/test-driven-development .agents/skills/test-driven-development && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "test-driven-development" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/test-driven-development into .agents/skills/test-driven-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-driven-development", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add intent-driven-dev/intent-driven-template --skill test-driven-development -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install intent-driven-dev/intent-driven-template test-driven-development --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/test-driven-development .cursor/skills/test-driven-development && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "test-driven-development" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/test-driven-development into .cursor/skills/test-driven-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-driven-development", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/intent-driven-dev/intent-driven-template.git --path .agents/skills/test-driven-development--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add intent-driven-dev/intent-driven-template --skill test-driven-development -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install intent-driven-dev/intent-driven-template test-driven-development --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/test-driven-development .gemini/skills/test-driven-development && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "test-driven-development" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/test-driven-development into .gemini/skills/test-driven-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-driven-development", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install intent-driven-dev/intent-driven-template test-driven-developmentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add intent-driven-dev/intent-driven-template --skill test-driven-development -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/test-driven-development .github/skills/test-driven-development && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "test-driven-development" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/test-driven-development into .github/skills/test-driven-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-driven-development", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add intent-driven-dev/intent-driven-template --skill test-driven-development -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install intent-driven-dev/intent-driven-template test-driven-development --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/test-driven-development .opencode/skills/test-driven-development && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "test-driven-development" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/test-driven-development into .opencode/skills/test-driven-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-driven-development", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
test-driven-development- GitHub stars
- 160
- Token cost
- ~405 tokens
- SKILL.md length
- 197 words
- Files
- 3 (incl. references)
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when implementing a change with test-driven development (TDD): work test-first through focused red-green cycles.
- Implementing a change with test-driven development (TDD): work test-first through focused red-green cycles
- SKILL.md covers Red, Green, Refactor and Patterns and anti-patterns, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Test-driven development
What it does
Test Driven Development is an agent skill from intent-driven-dev/intent-driven-template. Use when implementing a change with test-driven development (TDD): work test-first through focused red-green cycles.
Its SKILL.md is about 410 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/best-practices.md` and `references/collaborators.md`).
It sits in Testing & QA, covering Test-driven development. The repository describes itself as: OpenSpec and OpenCode template for intent-driven development with specs, ADRs, C4 diagrams, Gherkin, TDD, Multi-Model Adversarial Spec Authoring, Glossary for Domain Terms, and… The licence is MIT.
When your agent uses it
- Implementing a change with test-driven development (TDD): work test-first through focused red-green cycles
- Tasks that involve Test-driven development
Example prompts
- “/test-driven-development”
What it can do on your machine
Read from SKILL.md and the folder at commit 73f54d5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Test Driven Development loads about 405 tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 35 tokens; SKILL.md has 197 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from intent-driven-dev/intent-driven-template at commit 73f54d5, republished under its MIT licence (© intent-driven-dev). 197 words, ~405 tokens.
Download SKILL.mdSave it as
.claude/skills/test-driven-development/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- test-driven-development
- description
- Use when implementing a change with test-driven development (TDD): work test-first through focused red-green cycles.
Test-Driven Development
Use the repository's existing test tooling and conventions.
One test, one behaviour, one reason to fail. A test name describes that one behaviour; never use joiners such as "and", "or", or "etc." to combine independent outcomes. Multiple assertions are acceptable only when together they establish that same behaviour.
Red
- Select one observable behaviour from the requirement.
- Write one test before changing implementation code.
- Run the test and confirm it fails because the behaviour is missing, not because the test is broken.
Green
- Write only enough implementation code to pass the failing test.
- Run the test, then run the relevant suite.
- Do not add behaviour without first seeing its test fail.
Refactor
- Refactor only while the relevant suite is green, after completing a red-green slice.
- Refactor either the tests or the implementation in one pass, not both.
- Reuse shared setup, teardown, helpers, and parameterized structure when they clarify intent without combining behaviours.
- Rerun the relevant suite after each refactor pass.
Patterns and anti-patterns
Read patterns and anti-patterns when choosing a test shape, writing examples, or deciding whether cases belong together.
Collaborators
Read collaborators before substituting a dependency. Mock system boundaries, not code owned by the application.
© intent-driven-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in .agents/skills/test-driven-development of intent-driven-dev/intent-driven-template.
- SKILL.md
- references/best-practices.md
- references/collaborators.md
Open the folder on GitHubat commit 73f54d5
Compare with similar skills
Test Driven Development next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Test Driven Development this skillintent-driven-dev/intent-driven-template | 160 | — | ~405 | Automated safety check: Pass | MIT | |
| TDDpietheinstrengholt/rssmonster | 564 | 30 repos | ~906 | Automated safety check: Pass | MIT | |
| TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph | 112 | 11 repos | ~2.4k | Automated safety check: Pass | None | |
| TDDsanity-io/sanity | 6.4k | 20 repos | ~1k | Automated safety check: Pass | MIT | |
| Test Driven Developmentfarm-fe/farm | 5.6k | 51 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Tapd Story PipelineTencentBlueKing/bk-bcs | 840 | — | ~2.6k | Automated safety check: Pass | Custom licence |
Similar skills
TDD Workflow
hellangleZ/burn-in-cceverywhere-ralph
A skill your agent uses when writing new features, fixing bugs, or refactoring code.
- Official
TDD
sanity-io/sanity
Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.
Test Driven Development
farm-fe/farm
A skill your agent uses when implementing any feature or bugfix, before writing implementation code
Tapd Story Pipeline
TencentBlueKing/bk-bcs
单需求实现流水线——把一个 TAPD 需求从零推进到代码提交。自动串联技术澄清、 开发计划、任务拆分、TDD 实现、架构/安全校验、代码提交六个阶段。
Absolute Init
maddhruv/absolute
One-time setup for absolute: interview how you want it to behave (output style, autonomy, TDD strictness, spec dir, families) + detect the stack once, then write .absolute.config.json (project…
More from intent-driven-dev/intent-driven-template
All 10 skills in this repoAcceptance Test Authoring
intent-driven-dev/intent-driven-template
A skill your agent uses when creating or modifying acceptance tests, configuring cucumber-js or behave runners, writing or refactoring step definitions, linting executable Gherkin specs, choosing an…
Adversarial Authoring
intent-driven-dev/intent-driven-template
A skill your agent uses when rules or instructions mention "adversarial-authoring", "adversarial authoring", "must use adversarial-authoring skill", "model council", "cross-model review", or…
Architectural Decision Records
intent-driven-dev/intent-driven-template
A skill your agent uses when documenting, drafting, reviewing, or updating architectural decisions, ADRs, decision logs, tradeoffs, rationale, consequences, alternatives, or architecture decision…
Gherkin Authoring
intent-driven-dev/intent-driven-template
A skill your agent uses when drafting, reviewing, or improving Gherkin, Cucumber scenarios, BDD acceptance criteria, feature examples, Scenario Outlines, Backgrounds, Rules, Doc Strings, Data…
Glossary
intent-driven-dev/intent-driven-template
A skill your agent uses when authoring or reviewing specs, requirements, design docs, ADRs, tasks, glossary entries, domain terms, technical terms, or wording consistency across artifacts
Openspec Bulk Apply Change
intent-driven-dev/intent-driven-template
A skill your agent uses when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.
Related
Categories
Questions about Test Driven Development
What does Test Driven Development do?
A skill your agent uses when implementing a change with test-driven development (TDD): work test-first through focused red-green cycles. Test Driven Development is an agent skill from intent-driven-dev/intent-driven-template. Use when implementing a change with test-driven development (TDD): work test-first through focused red-green cycles.
When should I use Test Driven Development?
Test Driven Development fits situations like: implementing a change with test-driven development (TDD): work test-first through focused red-green cycles; tasks that involve Test-driven development.
How do I install Test Driven Development in Claude Code?
Run `npx skills add intent-driven-dev/intent-driven-template --skill test-driven-development -a claude-code`. Or copy the skill folder (.agents/skills/test-driven-development in intent-driven-dev/intent-driven-template) into .claude/skills/test-driven-development in your project. Claude Code loads it when a task matches its description.
How do I install Test Driven Development in Codex?
Run `npx skills add intent-driven-dev/intent-driven-template --skill test-driven-development -a codex`. Or copy the skill folder (.agents/skills/test-driven-development in intent-driven-dev/intent-driven-template) into .agents/skills/test-driven-development in your project. Codex loads it when a task matches its description.
Can I use Test Driven Development in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add intent-driven-dev/intent-driven-template --skill test-driven-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-driven-development, .gemini/skills/test-driven-development, .github/skills/test-driven-development and .opencode/skills/test-driven-development in your project.
What does Test Driven Development need to run?
SKILL.md names no scripts, command-line tools or credentials: Test Driven Development is instructions for the agent only.
Does Test Driven Development access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Test Driven Development safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Test Driven Development use?
Test Driven Development is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Test Driven Development use?
About 405 tokens (SKILL.md is roughly 1.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 827 tokens, read only when the agent opens those files.
What are the alternatives to Test Driven Development?
Skills that share tags, products or a category with Test Driven Development: TDD (pietheinstrengholt/rssmonster, 564 stars), TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars), TDD (sanity-io/sanity, 6.4k stars) and Test Driven Development (farm-fe/farm, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Test Driven Development?
intent-driven-dev (a GitHub organization) maintains it in intent-driven-dev/intent-driven-template, which has 160 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 4, 2026.
Source: intent-driven-dev/intent-driven-template on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.