📦
brainstorming
79Shape Ideas Into Implementation Designs
Early feature ideas often lack clear scope, trade-offs, and validation. This skill guides structured dialogue that turns uncertain ideas into reviewed designs.
Productivity View
Skills test-driven-development
📦
test-driven-development
Content revision r1 Safe ⚙️ External commands
Write Better Code with Test-First Development
Feature work and bug fixes can ship with weak tests when testing comes after implementation. This skill guides Claude, Codex, and Claude Code through strict test-first cycles, failure verification, minimal implementation, and refactoring.
Supports: Claude Codex Code(CC)
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "test-driven-development" from https://skillstore.io/skills/cycleaddict-test-driven-development.md and its manifest at https://skillstore.io/api/skills/cycleaddict-test-driven-development/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "test-driven-development". Add retry support to an operation helper.
Expected outcome:
- Starts by naming one observable retry behavior.
- Asks you to run the focused test and confirm the expected failure.
- Limits implementation to the passing behavior before refactoring.
Using "test-driven-development". Bug: empty email is accepted.
Expected outcome:
- Creates a regression test that rejects an empty email.
- Requires proof that the test fails for the missing validation.
- Guides the smallest validation change and then verifies green tests.
Using "test-driven-development". Review tests that use many mocks.
Expected outcome:
- Identifies assertions that only prove a mock exists.
- Suggests testing real behavior or mocking at a lower boundary.
- Checks whether each mock matches the real dependency contract.
Security Audit
Safev8 • 7/6/2026 Open versioned report
I found no executable command behavior in the reviewed files. The external-command findings are Markdown fences, inline examples, or generic test command examples, and the blocker findings are ordinary testing prose. No evidence found for prompt injection, data exfiltration, or unsafe semantic behavior.
2
Files scanned
672
Lines analyzed
0
Review items
0
False positives ignored
Risk Factors
⚙️ External commands (27)
SKILL.md:33-35 SKILL.md:35-49 SKILL.md:49-69 SKILL.md:69-76 SKILL.md:76-90 SKILL.md:90-95 SKILL.md:95-104 SKILL.md:104-117 SKILL.md:117-119 SKILL.md:119-135 SKILL.md:135-146 SKILL.md:146-151 SKILL.md:151-162 SKILL.md:162-172 SKILL.md:172-174 SKILL.md:174-202 SKILL.md:202-203 SKILL.md:203-295 SKILL.md:295-300 SKILL.md:300-303 SKILL.md:303-306 SKILL.md:306-309 SKILL.md:309-316 SKILL.md:316-319 SKILL.md:319-322 SKILL.md:322-366 SKILL.md:366-369
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/cycleaddict-test-driven-development/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/cycleaddict-test-driven-development?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/cycleaddict-test-driven-development?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cycleaddict-test-driven-development/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/cycleaddict-test-driven-development.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Cycleaddict. (2026). test-driven-development security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cycleaddict-test-driven-development/audits/8BibTeX citation
@techreport{cycleaddict-cycleaddict-test-driven-development-2026,
author = {Cycleaddict},
title = {test-driven-development security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/cycleaddict-test-driven-development/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "test-driven-development security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "Cycleaddict"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/cycleaddict-test-driven-development/audits/8"
identifiers:
- type: other
value: "skillstore:cycleaddict-test-driven-development:audit:8"
description: "Skillstore immutable audit report identifier"
Compare variants
9 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
Highest Skillstore Score
Author / source Skillstore Score Evidence Confidence Skillstore usage Updated
DMJGilbert Recommended
dmjgilbert-test-driven-development
Skillstore Score 79
Evidence Confidence High
Skillstore usage 10
Updated
2026-08-21
obra-test-driven-development
Skillstore Score 78
Evidence Confidence High
Skillstore usage 11
Updated
2026-08-21
Cycleaddict Current
cycleaddict-test-driven-development
Skillstore Score 78
Evidence Confidence High
Skillstore usage 8
Updated
2026-08-21
cygnusfear-test-driven-development
Skillstore Score 78
Evidence Confidence High
Skillstore usage 7
Updated
2026-08-21
dyai2025-test-driven-development
Skillstore Score 75
Evidence Confidence Medium
Skillstore usage 8
Updated
2026-08-21
codingcossack-test-driven-development
Skillstore Score 74
Evidence Confidence High
Skillstore usage 13
Updated
2026-08-21
zhanlincui-test-driven-development
Skillstore Score 69
Evidence Confidence High
Skillstore usage 99
Updated
2026-08-21
sickn33-test-driven-development
Skillstore Score 38
Evidence Confidence Medium
Skillstore usage 9
Updated
2026-08-21
davila7-test-driven-development
Skillstore Score 38
Evidence Confidence Medium
Skillstore usage 7
Updated
2026-08-21
Skillstore Score
Why this score Evidence Confidence: High 55
Architecture
85
Maintainability
87
Content
72
Community
83
Spec Compliance
What You Can Build
Implement a Feature Test First
Guide a developer from a single failing behavior test to minimal implementation and safe refactoring.
Fix a Regression with Proof
Turn a reported bug into a failing regression test before applying the smallest reliable fix.
Improve Mock-Heavy Tests
Review tests that assert on mocks and redirect them toward real behavior and simpler dependencies.
Try These Prompts
Start a TDD Change
Help me implement this change with TDD. First identify the smallest failing test, then wait for the failure result before implementation.
Create a Regression Test
Convert this bug into a regression test. Describe the expected failure, ask me to run it, then guide the minimal fix.
Refactor After Green
My focused tests now pass. Help me refactor without changing behavior, and keep the verification steps explicit.
Audit Test Strategy
Review this test plan for TDD discipline. Flag tests written after code, mock assertions, missing failure proof, and weak verification steps.
Best Practices
- Watch each new test fail for the expected reason before implementation.
- Add the smallest production change that makes the current test pass.
- Refactor only after focused and related tests are green.
Avoid
- Writing implementation first and adding tests after.
- Asserting that mocks exist instead of verifying real behavior.
- Expanding scope during the green phase without a failing test.
Frequently Asked Questions
Does this skill run tests automatically?
No. It guides the agent to ask for and use project-specific test commands.
Can I use it for bug fixes?
Yes. It asks for a failing regression test before the fix.
Does it support refactoring?
Yes. It supports refactoring only after tests are green and behavior is protected.
What frameworks does it cover?
It is framework-neutral. The examples use TypeScript, but the workflow applies across languages.
How does it treat mocks?
It discourages testing mock behavior and recommends real behavior tests when practical.
When should I not use it?
Ask for human approval before skipping TDD for prototypes, generated code, or configuration-only changes.
Developer Details
Author
CycleaddictLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Repository
https://github.com/Cycleaddict/generic-superpowers/tree/main/skills/test-driven-developmentRef
d11af420e07cd866fe39cfa937efef3223896c06
Maintenance freshness
7/18/2026
Usage
5 downloads · 315 views
File structure
More from Cycleaddict
View all📦
dispatching-parallel-agents
79Dispatch Parallel Coding Agents
Sequential debugging slows teams when failures are independent. This skill shows how to split focused tasks across parallel AI agents and integrate results safely.
Coding & Development View
📦
requesting-code-review
78Request Structured Code Reviews
Implementation teams need reliable review before merge. This skill guides Claude, Codex, and Claude Code through structured readiness checks.
Coding & Development View
📦
writing-plans
78Create Detailed Coding Plans
Complex implementation work can fail when tasks, files, tests, and handoffs are unclear. This skill helps Claude, Codex, and Claude Code create detailed plans with small steps, exact paths, tests, and execution options.
Coding & Development View
📦
executing-plans
78Execute Implementation Plans with Checkpoints
Long implementation plans are easy to rush or execute without review. This skill guides Claude, Codex, and Claude Code through batched work with verification checkpoints.
Coding & Development View
📦
receiving-code-review
78Evaluate Code Review Feedback
Code review feedback can be unclear, incomplete, or technically wrong for the current codebase. This skill gives Claude, Codex, and Claude Code a verification workflow before changing code.
Coding & Development View
Related Skills
View all📦
tdd
80Guide TDD with Red-Green-Refactor
by mattpocock
Test-first work often becomes brittle when teams test internals or write too many tests upfront. This skill guides Codex, Claude, and Claude Code through behavior-focused red-green-refactor cycles.
Coding & Development View
📦
analyzing-patterns
86Analyze Patterns Across Your Codebase
by C0ntr0lledCha0s
Large codebases hide repeated structures and inconsistent decisions. This skill maps design patterns, architecture, conventions, duplication, and anti-patterns with evidence and recommendations.
Coding & Development View
📦
testing
85Build Reliable Test Automation
by 89jobrien
Weak tests slow releases and hide regressions. This skill guides test strategy, TDD, automation, coverage review, and Playwright web checks.
Coding & Development View
📦
testing-patterns
81Plan Reliable Tests Across Your Codebase
by 0xDarkMatter
This skill helps teams choose test strategies, mocks, data fixtures, coverage gates, and CI patterns without mixing test scopes. It gives Claude, Codex, and Claude Code structured guidance for unit, integration, end-to-end, TDD, and pipeline testing.
Coding & Development View
📦
golang-testing
81Build Better Go Tests
by 89jobrien
Go teams need consistent tests across units, integrations, mocks, benchmarks, and coverage. This skill provides practical Go testing patterns that Claude, Codex, and Claude Code can apply during development.
Coding & Development View
📦
tdd-pytest
81Build Python Tests with pytest TDD
by 89jobrien
Python teams often need consistent tests, coverage, and reports without losing TDD discipline. This skill provides pytest-focused workflows, examples, and reporting guidance for Claude, Codex, and Claude Code.
Coding & Development View