driving-tdd

Convert acceptance criteria into failing tests and implement minimal code.

2|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/chriswch/praxis --skill driving-tdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: driving-tdd
Source: https://github.com/chriswch/praxis/tree/main/skills/driving-tdd
Command: npx skills add https://github.com/chriswch/praxis --skill driving-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Drives the TDD loop to convert acceptance criteria into failing tests, write minimal code to pass, and refactor to reveal design.

Core Features & Use Cases

  • Red-Green-Refactor cycles to implement story-level acceptance criteria with minimal code.
  • Feedback loop to surface spec gaps back to clarifying-intent for iterative refinement.
  • Applies after clarifying-intent or sketching-design to drive controlled implementation toward emergent design.

Quick Start

Start a TDD session by translating the story’s acceptance criteria into tests and implementing the minimum code to pass.

Frequently Asked Questions about driving-tdd

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

FAQPage Schema
How do I start test-driven development from acceptance criteria?

Start test-driven development by translating story-level acceptance criteria into failing tests, then implement the minimal code required to pass them before refactoring.

What is the Red-Green-Refactor cycle in TDD?

The Red-Green-Refactor cycle in TDD involves writing a failing test, implementing the minimum code to make it pass, and then refactoring to reveal emergent design.

How do I handle edge cases when driving a TDD workflow?

Handle edge cases in a TDD workflow by iterating through Red-Green-Refactor cycles to cover story-level changes and maintain a checklist of acceptance criteria.

When should I refactor code during test-driven development?

Refactor code during test-driven development after implementing the minimal code to pass a failing test, ensuring the refactoring process reveals emergent design without breaking functionality.

Can I feed back spec gaps discovered during TDD to refine requirements?

Yes, you can surface spec gaps discovered during TDD back to the intent clarification phase, creating a feedback loop for iterative requirement refinement.

Do I need to clarify intent before starting a TDD session?

Yes, clarifying intent or sketching a design before starting a TDD session is recommended to drive controlled implementation toward emergent design effectively.