Skills tdd-workflows-tdd-cycle
📦

tdd-workflows-tdd-cycle

Content revision r1 Safe ⚙️ External commands

Run a Strict TDD Cycle

Teams often skip fail-first testing and lose design feedback. This skill guides Claude, Codex, and Claude Code through a strict red-green-refactor workflow.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "tdd-workflows-tdd-cycle" from https://skillstore.io/skills/sickn33-tdd-workflows-tdd-cycle.md and its manifest at https://skillstore.io/api/skills/sickn33-tdd-workflows-tdd-cycle/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.

Markdown detail GET /skills/sickn33-tdd-workflows-tdd-cycle.md Signed manifest GET /api/skills/sickn33-tdd-workflows-tdd-cycle/manifest Signed lockfile GET /api/skills/sickn33-tdd-workflows-tdd-cycle/lockfile

Test it

Using "tdd-workflows-tdd-cycle". Create a payment validation feature using TDD.

Expected outcome:

The assistant lists acceptance criteria, writes failing unit tests, verifies the failures, implements only required logic, then refactors with tests passing.

Using "tdd-workflows-tdd-cycle". Use incremental TDD for a search filter.

Expected outcome:

The assistant handles one behavior at a time, keeps each implementation minimal, and records coverage progress after each cycle.

Using "tdd-workflows-tdd-cycle". Review whether this feature followed TDD.

Expected outcome:

The assistant reports phase violations, missing tests, coverage gaps, and refactoring needs, then recommends concrete recovery steps.

Security Audit

Safe
v4 • 7/7/2026 Open versioned report

All nine static findings appear to be false positives caused by inline backtick formatting, checklist words, and testing workflow language in SKILL.md. I found no evidence of command execution, network reconnaissance, system reconnaissance, credential access, prompt injection, or data exfiltration intent.

1
Files scanned
222
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (3)
SKILL.md:21 SKILL.md:132 SKILL.md:142
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.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-tdd-workflows-tdd-cycle/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-tdd-workflows-tdd-cycle/security.svg)](https://skillstore.io/skills/sickn33-tdd-workflows-tdd-cycle?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-tdd-workflows-tdd-cycle?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-tdd-workflows-tdd-cycle/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-tdd-workflows-tdd-cycle.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

sickn33. (2026). tdd-workflows-tdd-cycle security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-tdd-workflows-tdd-cycle/audits/4

BibTeX citation

@techreport{sickn33-sickn33-tdd-workflows-tdd-cycle-2026, author = {sickn33}, title = {tdd-workflows-tdd-cycle security audit report (audit version 4)}, institution = {Skillstore}, year = {2026}, number = {4}, url = {https://skillstore.io/skills/sickn33-tdd-workflows-tdd-cycle/audits/4}, 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: "tdd-workflows-tdd-cycle security audit report (audit version 4)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-07" url: "https://skillstore.io/skills/sickn33-tdd-workflows-tdd-cycle/audits/4" identifiers: - type: other value: "skillstore:sickn33-tdd-workflows-tdd-cycle:audit:4" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
68
Community
83
Spec Compliance

What You Can Build

Ship Features Test First

Use the red-green-refactor loop to build new behavior from clear acceptance criteria and failing tests.

Standardize Test Automation

Create repeatable unit, integration, performance, and edge-case testing steps for a development team.

Review TDD Compliance

Check whether a feature followed fail-first testing, coverage checkpoints, and refactoring expectations.

Try These Prompts

Start a TDD Feature 
Apply this TDD cycle to <feature>. Start by defining acceptance criteria, edge cases, and failing unit tests. Do not implement production code yet.
Use Incremental Mode 
Use incremental mode for <feature>. Write one failing test, implement only enough code, then refactor before the next test.
Build a Full Test Suite 
Use suite mode for <module>. Design the full failing test suite, implement the smallest passing solution, then add integration tests.
Audit TDD Discipline 
Review <feature> against this TDD workflow. Identify any broken phase, missing checkpoint, coverage gap, or refactoring issue.

Best Practices

  • Confirm each test fails for the expected reason before writing implementation.
  • Keep green-phase code limited to the behavior required by failing tests.
  • Run the relevant test suite after every refactoring step.

Avoid

  • Writing implementation code before a failing test exists.
  • Changing tests only to make broken production code pass.
  • Skipping refactoring after tests become green.

Frequently Asked Questions

Does this skill run tests automatically?
No. It instructs the AI assistant to run project test commands when available.
Can I use it with Claude, Codex, and Claude Code?
Yes. The workflow is written for AI coding assistants and supports those tools.
Does it require a specific programming language?
No. It describes a TDD process that can apply across languages and test frameworks.
What does incremental mode mean?
Incremental mode focuses on one failing test, one minimal implementation, and one refactor at a time.
What does suite mode mean?
Suite mode writes a broader failing test set before implementing the full feature behavior.
Can the coverage thresholds be changed?
Yes. The listed thresholds are defaults and should match repository standards when needed.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/tdd-workflows-tdd-cycle

Ref

9f814fc6a43fd99946f2da5e0df231c65a38bc76

Maintenance freshness

7/23/2026

Usage

8 downloads · 94 views

File structure

📄 SKILL.md

More from sickn33

View all

Related Skills

View all