void-tdd

Enforces test-driven development cycles with strict, souple, and exploratory modes for TypeScript projects.

Updated May 29, 2026
One-click install
npx skills add https://github.com/voidcorp-core/void-harness --skill void-tdd-voidcorp-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: void-tdd
Source: https://github.com/voidcorp-core/void-harness/tree/main/packages/core/skills/void-tdd
Command: npx skills add https://github.com/voidcorp-core/void-harness --skill void-tdd-voidcorp-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code written without tests drifts into regressions, and AI coding agents routinely skip test-first discipline unless it is enforced. This Skill installs a rigorous TDD methodology—RED-GREEN-REFACTOR with mode selection, mutation gates, and commit evidence—so every feature, bugfix, and refactor follows a verifiable test-first process. ## Core Features & Use Cases - Three TDD modes: strict (Iron Law: no production code without a failing test), souple (RED-GREEN-REFACTOR without mutation gates), and exploratory (throwaway spikes with declared deletion dates), auto-detected from file paths or explicit markers. - Mutation testing gate: when a mutation runner like Stryker is detected in the project config, strict mode requires running it and killing surviving mutants before completion. - Companion hook enforcement: a PreToolUse hook blocks edits to production code unless a sibling test file or a declared E2E coverage file exists. - Use Case: While implementing a retry utility in a TypeScript service, the Skill forces you to write a failing backoff test first, watch it fail, write minimal code to pass, run the mutation suite, and produce a commit history showing the RED-GREEN-REFACTOR progression. ## Quick Start Ask the agent to implement a new feature or fix a bug using test-driven development in strict mode, and it will write the failing test before any production code.

Frequently Asked Questions about void-tdd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce test-driven development with an AI coding agent?

Use a TDD skill that mandates the RED-GREEN-REFACTOR cycle: the agent must write a failing test, watch it fail, then write minimal code to pass. A companion PreToolUse hook blocks edits to production files unless a sibling test file exists.

What is the difference between strict and exploratory TDD modes?

Strict mode applies the Iron Law—zero production code without a failing test—plus mutation testing and 100% coverage. Exploratory mode allows untested spike code, but the file must declare throwaway status and a deletion date, and must transition to strict before merging.

Does this TDD workflow require a mutation testing tool?

No. The mutation gate only applies when a runner like Stryker is detected in the project dependencies and written into the config. Without it, strict mode relies on a manual mutator scan when writing tests instead of blocking the cycle.

How is TDD compliance verified in a pull request?

Compliance is shown through commit history evidence: separate commits for the failing test, the implementation, mutation fixes, and refactoring. Non-linear histories must document the RED, GREEN, and REFACTOR phases explicitly in the PR description.

What happens if code was written before the test in strict mode?

The code must be deleted entirely—not kept as reference or adapted—and re-implemented fresh from the tests. This rule exists because keeping unverified code leads to test-after behavior, which proves nothing about the intended design.