guild-tdd

Enforces test-first development by guiding the Red-Green-Refactor cycle for Guild engineering teams.

6|Updated Apr 24, 2026

Search Tags:#workflow #testing #tdd #quality-assurance #software-engineering #test-driven-development

Ready to run

npx skills add https://github.com/lookatitude/guild --skill guild-tdd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: guild-tdd
Source: https://github.com/lookatitude/guild/tree/main/skills/fallback/tdd
Command: npx skills add https://github.com/lookatitude/guild --skill guild-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams enforce test-first development by guiding when and how to apply Test-Driven Development (TDD) before implementing features or fixes.

Core Features & Use Cases

Guides the Red-Green-Refactor cycle to ensure code correctness from the start.
Enforces production code requires a failing test first, preventing untested changes.
Provides practical examples and decision criteria for applying TDD across features, bugfixes, and refactors.

Quick Start

Start by writing a failing test, then implement the minimal code to pass.

Frequently Asked Questions about guild-tdd

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

FAQPage Schema

What is the test-driven development workflow for software engineering?▼

Test-driven development follows the Red-Green-Refactor cycle: write a failing test first, implement minimal production code to pass it, then iteratively refactor with guardrails.

How do I apply TDD to bug fixes and refactoring?▼

For bug fixes and refactoring, apply TDD by writing a failing test that reproduces the bug or validates the design, then implement minimal code changes to make it pass.

When should I enforce the failing-test-first rule in feature implementation?▼

Enforce the failing-test-first rule before writing any production code for new features; this prevents untested changes and ensures code correctness from the start.

What's the best way to start a TDD cycle for engineering teams?▼

Start a TDD cycle by writing a failing test, then implement the minimal code required to pass that test, and finally refactor the code iteratively using provided checklists.

Does TDD require specific testing frameworks to implement the Red-Green-Refactor cycle?▼

No specific testing frameworks are required; the TDD discipline applies the Red-Green-Refactor cycle generically across feature implementation, bug fixes, and refactoring workflows.

Why does minimal production code matter in test-driven development?▼

Minimal production code matters because it ensures you only write code necessary to pass the failing test, maintaining strict quality-assurance and preventing over-engineering.