tdd-patterns

Track RED-GREEN-REFACTOR tasks for TDD cycles in CI workflows.

6|2|Updated Dec 19, 2025
One-click install
npx skills add https://github.com/synaptiai/synapti-marketplace --skill tdd-patterns-synaptiai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-patterns
Source: https://github.com/synaptiai/synapti-marketplace/tree/main/plugins/flow/skills/tdd-patterns
Command: npx skills add https://github.com/synaptiai/synapti-marketplace --skill tdd-patterns-synaptiai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a disciplined, repeatable workflow for writing reliable tests and implementing features or fixes so tests validate behavior rather than implementation and test runner misconfiguration does not mask failures.

Core Features & Use Cases

  • Red-Green-Refactor workflow: Create and track RED, GREEN, and REFACTOR tasks to ensure tests fail first, pass next, and then code is cleaned up.
  • Test runner discipline and CI alignment: Enforce running tests in non-watch modes and verify no orphan test processes remain.
  • Quality standards and coverage targets: Encourage one behavior per test, descriptive names, minimal mocking, and meaningful coverage thresholds for critical paths.
  • Use Case: When implementing a new API endpoint or fixing a bug, write a failing test first, implement the minimal change to pass it, then refactor while validating the entire suite.

Quick Start

Create a failing test for the new feature, implement the simplest code to make it pass, then refactor while running the full test suite between each step.

Frequently Asked Questions about tdd-patterns

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

FAQPage Schema
How do I enforce test-driven development discipline in my CI workflow?

To enforce test-driven development discipline in CI, configure a testing.tddMode policy to manage Red-Green-Refactor cycles, record task states via a task-tracking API, and maintain test runner discipline by preventing misconfigured watch modes.

What is the Red-Green-Refactor workflow for writing reliable tests?

The Red-Green-Refactor workflow tracks RED, GREEN, and REFACTOR tasks to ensure tests fail first, pass with minimal implementation, and then clean up code while validating the entire suite.

How do I stop test runner misconfiguration from masking failures?

Stop test runner misconfiguration by enforcing non-watch modes and verifying no orphan test processes remain, ensuring tests validate behavior rather than implementation and failures are never masked.

Does TDD discipline require a task-tracking API to manage test cycles?

Yes, TDD discipline requires a task-tracking API with TaskCreate, TaskUpdate, and TaskList operations to record RED, GREEN, and REFACTOR tasks during feature implementations and bug fixes.

What's the best way to maintain quality standards when doing test-driven development?

Maintain TDD quality standards by encouraging one behavior per test, descriptive names, minimal mocking, and meaningful coverage thresholds for critical paths throughout the Red-Green-Refactor cycle.