skills.rest
bluejayA
bluejayACOMMUNITY
Explore all skills by this author →
WebsiteGitHub

aidlc-test-driven-development

Enforce the RED-GREEN-REFACTOR cycle for all code development.

2|Updated Mar 10, 2026
Search Tags:#code quality#testing#tdd#development workflow#refactoring#red-green-refactor
One-click install
npx skills add https://github.com/bluejayA/devflow-aidlc-like --skill aidlc-test-driven-development
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aidlc-test-driven-development
Source: https://github.com/bluejayA/devflow-aidlc-like/tree/main/skills/aidlc-test-driven-development
Command: npx skills add https://github.com/bluejayA/devflow-aidlc-like --skill aidlc-test-driven-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces the Test-Driven Development (TDD) methodology, ensuring that no production code is written without first writing a failing test, thereby improving code quality and reliability.

Core Features & Use Cases

  • Rigorous TDD Enforcement: Mandates the RED-GREEN-REFACTOR cycle without exceptions.
  • Iron Law Adherence: Strictly follows the TDD Iron Law: no production code without a failing test.
  • Use Case: When developing new features or fixing bugs, this skill ensures that a test is written first to define the expected behavior, followed by the minimal code to pass the test, and then refactoring for clarity.

Quick Start

Use the aidlc-test-driven-development skill to enforce TDD principles for the current development task.

Frequently Asked Questions about aidlc-test-driven-development

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

FAQPage Schema
How do I enforce test-driven development in my code generation workflow?▼

To enforce test-driven development, you must mandate the RED-GREEN-REFACTOR cycle, preventing production code generation without a preceding failing test to ensure software reliability.

What is the TDD Iron Law for writing production code?▼

The TDD Iron Law dictates that no production code is written without first writing a failing test, ensuring that all development is strictly driven by test-defined behavior.

How do I start the RED-GREEN-REFACTOR cycle for new features?▼

Start the RED-GREEN-REFACTOR cycle by writing a failing test to define expected behavior, implement minimal code to pass the test, then refactor the codebase for clarity and quality.

Can I use TDD principles alongside automated code generation and execution skills?▼

Yes, test-driven development principles integrate with code generation and execution skills, maintaining a strict development workflow where tests always precede production code.

When do I need to apply test-driven development for bug fixing?▼

Apply test-driven development for bug fixing by first writing a test that reproduces the bug and defines expected behavior, then modifying code to pass the test and refactoring safely.

Related Skills

Explore More Software Engineering Skills→
pingwupingwu
12

test-first-development

Generate BDD/Gherkin feature files and TDD test scaffolding before coding.

Community
Intermediate
rube-derube-de
10

test

Detect test frameworks, run suites with coverage, and report findings as a GitHub issue.

Community
Advanced
TonyQ-AITonyQ-AI
9

test-driven-development

Enforce the Red-Green-Refactor cycle for software development tasks.

Community
Advanced
romiluz13romiluz13
161

test-driven-development

Enforce the red-green-refactor TDD cycle with failing tests before production code.

Community
Intermediate