skills.rest
mtthsnc
mtthsncCOMMUNITY
Explore all skills by this author →
GitHub

use-tdd

Enforce test-driven development through red-green-refactor cycles with automated checks.

1|Updated Jan 9, 2026
Search Tags:#workflow#testing#tdd#software-engineering#test-driven-development
One-click install
npx skills add https://github.com/mtthsnc/autonome --skill use-tdd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: use-tdd
Source: https://github.com/mtthsnc/autonome/tree/main/skills/use-tdd
Command: npx skills add https://github.com/mtthsnc/autonome --skill use-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces test-first development to prevent production code from being written without a failing test, guiding teams toward intentional design and reliable software.

Core Features & Use Cases

  • Red-Green-Refactor cycle: write a failing test, observe failure, implement the minimal production code to pass, then refactor with confidence.
  • Mandatory failure verification: ensure tests fail for missing functionality and that fixes are validated by running the test suite.
  • Guided workflow with guardrails: structured steps, reviews, and checks that reduce risk when implementing new features or fixing bugs.

Quick Start

Write a failing test that expresses the desired behavior, run the tests to confirm failure, then implement the minimal production code to pass and finally refactor with tests still passing.

Frequently Asked Questions about use-tdd

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

FAQPage Schema
What is test-driven development and how does the red-green-refactor cycle work?▼

Test-driven development is a workflow requiring a failing test before production code, observing the failure, implementing minimal code to pass, and refactoring while keeping tests green to drive intentional software design.

How do I start writing a failing test for a new feature or bug fix?▼

To start test-driven development, write a test expressing the desired behavior, run the test suite to confirm it fails for missing functionality, then implement minimal production code to pass before refactoring.

Does test-driven development work for both new features and bug fixes?▼

Test-driven development applies to both new features and bug fixes, guiding teams through red-green-refactor cycles with structured steps and guardrails to reduce risk across software projects.

What's the best way to enforce mandatory failure verification in test-driven development?▼

Enforce test-driven development by running tests to observe failure before writing production code, ensuring tests fail for missing functionality and fixes are validated by automated checks during the refactor phase.

Why should I write a failing test before implementing production code?▼

Writing a failing test before production code prevents unvalidated functionality from being added, ensuring code changes are intentional and reliable software is built through disciplined experimentation and automated checks.

Related Skills

Explore More Software Engineering Skills→
project-axproject-ax
5

ax-testing

Automate AX platform regression tests with Node.js and Bun test runners.

Official
Advanced
RheasilviaRheasilvia

test-driven-development

Enforce the Red-Green-Refactor cycle with automated tests via terminal.

Community
Advanced
mattleonard16mattleonard16

test-driven-development

Enforce a red-green-refactor cycle with failing tests first.

Community
Intermediate
Cogni-AI-OUCogni-AI-OU
3

tdd

Guide test-driven development with contract-first red-green-refactor sequencing.

Official
Advanced