mh-cto-sdlc-tdd-session

Enforce the RED-GREEN-LOOP cycle for iterative story implementation.

2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Imad-Oute/MicroHard --skill mh-cto-sdlc-tdd-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mh-cto-sdlc-tdd-session
Source: https://github.com/Imad-Oute/MicroHard/tree/main/src/departments/cto/sdlc/phase-6-implementation/mh-cto-sdlc-tdd-session
Command: npx skills add https://github.com/Imad-Oute/MicroHard --skill mh-cto-sdlc-tdd-session

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures a structured, disciplined approach to Test-Driven Development (TDD) for implementing software stories, reducing bugs and improving code quality.

Core Features & Use Cases

  • TDD Feedback Loop: Manages the RED → GREEN → LOOP cycle for each story behavior.
  • Discipline Enforcement: Embeds TDD discipline reference and checklist per cycle.
  • Acceptance Criteria Validation: Verifies story acceptance criteria against the implemented behavior.
  • Debugging Discipline: Requires tagging debug logs for session cleanup and verifiability.
  • Progression to Review: Advances story status to review upon clean exit.
  • Use Case: For a story in progress, initiate a TDD session to validate each behavior against acceptance criteria and ensure adherence to TDD discipline.

Quick Start

Begin a TDD session for the current story using the command: 'tdd session'

Frequently Asked Questions about mh-cto-sdlc-tdd-session

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

FAQPage Schema
How do I enforce test-driven development discipline for iterative story implementation?

To enforce TDD discipline for iterative story implementation, you facilitate a structured RED → GREEN → LOOP cycle that validates each story behavior against predefined acceptance criteria. This ensures disciplined software development and reduces bugs.

What is the RED → GREEN → LOOP cycle in test-driven development?

The RED → GREEN → LOOP cycle in test-driven development is a structured feedback loop for iterative story implementation. It requires writing failing tests first, making them pass, and then refactoring or looping to validate the next behavior against acceptance criteria.

How do I validate acceptance criteria during a TDD session?

To validate acceptance criteria during a TDD session, you apply the RED → GREEN → LOOP cycle to each story behavior. The session verifies the implemented behavior against the predefined acceptance criteria before advancing the story status to review.

Do I need a specific environment to run a TDD session for story implementation?

Yes, you need a TDD-compliant environment with predefined acceptance criteria and established test frameworks. The session operates within this setup to enforce software development discipline and validate story behaviors accurately.

How does test-driven development handle debugging and session cleanup?

Test-driven development handles debugging by requiring strict tagging of debug logs during the TDD session. This ensures verifiability and simplifies session cleanup, allowing the story to advance to review only upon a clean exit.

Best way to manage TDD feedback loops for agile software development?

The best way to manage TDD feedback loops for agile software development is to enforce the RED → GREEN → LOOP cycle per story behavior. This embeds TDD discipline references and validates acceptance criteria before progressing to code review.