Skills tdd-workflow
📦

tdd-workflow

Content revision r2 Safe ⚙️ External commands

Apply Test-Driven Development

Unstructured coding often produces unverified behavior and costly rework. This skill guides development through focused failing tests, minimal implementations, and disciplined refactoring.

Supports: Claude Codex Code(CC)
🥉 79 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-workflow" from https://skillstore.io/skills/sickn33-tdd-workflow.md and its manifest at https://skillstore.io/api/skills/sickn33-tdd-workflow/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-workflow.md Signed manifest GET /api/skills/sickn33-tdd-workflow/manifest Signed lockfile GET /api/skills/sickn33-tdd-workflow/lockfile

Test it

Using "tdd-workflow". Add rejection of empty email addresses using TDD.

Expected outcome:

  • Red: Add a focused test expecting empty email input to be rejected.
  • Green: Add the minimum validation needed to satisfy that test.
  • Refactor: Clarify validation names while preserving all passing tests.

Using "tdd-workflow". Fix a calculator defect where division by zero returns an invalid value.

Expected outcome:

First reproduce the defect with an error-focused test. Then add the smallest guard and simplify only after the full suite passes.

Using "tdd-workflow". Prioritize tests for a new order total calculation.

Expected outcome:

  • Priority 1: Verify a standard order total.
  • Priority 2: Verify invalid prices and quantities.
  • Priority 3: Verify empty orders and rounding boundaries.
  • Priority 4: Measure performance for large orders.

Security Audit

Safe
v6 • 9/6/2026 Open versioned report

All three static findings are false positives caused by ordinary TDD prose and a fenced process diagram. No executable commands, reconnaissance behavior, or prompt injection were found.

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

Risk Factors

⚙️ External commands (1)
SKILL.md:17-25
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-workflow/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

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

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-tdd-workflow.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-workflow security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-tdd-workflow/audits/6

BibTeX citation

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

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Higher Skillstore usage
sickn33 Recommended Current

sickn33-tdd-workflow

Skillstore Score 79
Evidence Confidence High
Skillstore usage 13
Updated

2026-09-09

DoubleslashSE

doubleslashse-tdd-workflow

Skillstore Score 79
Evidence Confidence High
Skillstore usage 10
Updated

2026-09-09

Skillstore Score

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

What You Can Build

Develop a New Feature

Turn a feature requirement into focused tests, minimal implementation steps, and controlled refactoring.

Prevent Bug Regressions

Reproduce a defect with a failing test before implementing and refining the correction.

Coordinate AI Coding Roles

Assign test writing, implementation, and refactoring responsibilities across separate AI agents.

Try These Prompts

Start a TDD Cycle 
Guide me through Red-Green-Refactor for this requirement: [requirement]. Begin with one observable behavior and a failing test.
Fix a Bug Test First 
Use TDD to fix this defect: [defect]. First define a regression test, then propose the smallest correction.
Design Edge Case Coverage 
Analyze [feature] and prioritize happy-path, error, and edge-case tests. Organize each test using Arrange, Act, and Assert.
Run a Multi-Agent TDD Workflow 
Plan a multi-agent TDD workflow for [complex feature]. Separate Red, Green, and Refactor responsibilities with review gates and acceptance criteria.

Best Practices

  • Confirm every new test fails for the expected reason before implementation.
  • Keep each test focused on one observable behavior.
  • Refactor in small steps while the complete test suite remains passing.

Avoid

  • Writing production code before observing a meaningful failing test.
  • Testing private implementation details instead of external behavior.
  • Adding optimization or unrelated abstractions during the Green phase.

Frequently Asked Questions

What development cycle does this skill use?
It uses Red-Green-Refactor: write a failing test, implement minimal passing code, then improve the design.
Can this skill write framework-specific tests?
It provides general test design guidance. The prompt must include repository and framework context for specific syntax.
Does the skill execute tests?
No. It guides the workflow, while the selected coding tool and project environment handle test execution.
When is TDD most useful?
It is most useful for new behavior, bug fixes, and complex logic with clear expected outcomes.
When should TDD be limited?
Use exploratory spikes for uncertain ideas, then apply TDD after requirements and interfaces become clearer.
Can multiple AI agents use this workflow?
Yes. Separate agents can own failing tests, minimal implementation, and refactoring, with shared acceptance criteria.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Repository

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

Ref

ae6ba0f1a47f0b4427a656b2202f2ff34bfea6be

Maintenance freshness

9/6/2026

Usage

12 downloads · 134 views

File structure

📄 SKILL.md

More from sickn33

View all

Related Skills

View all