Skip to content
Skills Library
Programming · Testing

test-driven-development

/test-driven-development

Use only when the user explicitly requests TDD, test-first development, or a red-green-refactor workflow for executable behavior.

Licence
MIT
Last repository change
05.09.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
1
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

Use only when the user explicitly requests TDD, test-first development, or a red-green-refactor workflow for executable behavior.

Original author description

Use only when the user explicitly requests TDD, test-first development, or a red-green-refactor workflow for executable behavior.

How it works

SKILL.md has no level-two headings · 18 lines, 166 words

SKILL.md preview
---
name: test-driven-development
description: Use only when the user explicitly requests TDD, test-first development, or a red-green-refactor workflow for executable behavior.
---

<!-- Derived from Superpowers by Jesse Vincent (MIT). See THIRD_PARTY_NOTICES.md. -->

# Test-Driven Development

Apply strict red-green-refactor to one behavior at a time.

1. **Red:** Write the smallest test that expresses the required behavior. Run it and confirm it fails because that behavior is missing, not because the test is broken.
2. **Green:** Write only enough production code to pass. Run the focused test, then the smallest relevant regression suite.
3. **Refactor:** Improve structure without changing behavior. Keep the tests green.
4. Repeat for the next behavior.

Do not write or retain the implementation for a requested behavior before observing its test fail. If exploration is needed, keep it disposable and restart the production change from the failing test. Prefer real code over mocks; mock only an unavoidable boundary.

Generated artifacts, documentation, metadata, and non-executable configuration are outside this workflow. Verify them with the smallest relevant check instead.

Completion evidence must include the observed failing test, the passing test after implementation, and the final relevant suite.
Files in this package (2)
  • SKILL.md 1 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · hashimthearab/agent-workflows86MIT
GanyuanRan/Aegis100MIT
lucasouzadev/agent-kit-skill100MIT
zeative/satgas100AGPL-3.0
nikospavlopoulos/devops-mutant-powers100MIT
JohnStrunk/CommonCast100LGPL
Sanit-mann/The-Insectoids100MIT
mastro993/fstack100MIT
jelvodev/yaap100MIT

Database snapshot: 13.11.2026 · package version 18c1e65e0159 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100tdd
    Test-Driven Development enforcement skill. Activates full TDD mode. Activate when: TDD, test-driven, test first, red-green-refactor, write tests first.
  • 100tdd-workflow
    Test-Driven Development workflow enforcement with RED-GREEN-REFACTOR cycle. Use only when the user explicitly asks for test-first work or improved test coverage.
  • 95tdd-workflow
    Test-Driven Development workflow enforcement skill. Use when explicitly asked for TDD methodology, test-first development, red-green-refactor cycle, or TDD implementation. Triggers on keywords like "start TDD", "test-driven development", "write tests first", or in Chinese "開始…
  • 100test-driven-development-codex
    Enforce strict test-driven development via Codex-backed implementation. Use only when the user explicitly asks for the Codex-backed TDD workflow.
  • 100tdd
    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
  • 100tdd
    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.