gxpm-tdd

Name: gxpm-tdd
Availability: InStock
Author: laozhong86

Enforce test-first development with red-green-refactor cycles and integration tests.

1|Updated Apr 24, 2026

Search Tags:#tdd #red-green-refactor #integration-tests #behavior-spec #vertical-slices #gxpm

Ready to run

npx skills add https://github.com/laozhong86/gxpm --skill gxpm-tdd

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reduces production risk by enforcing test-first development and red-green-refactor cycles, ensuring features are implemented only after failing tests and validated end-to-end.

Core Features & Use Cases

Enforces vertical-slice tracer bullets that validate behavior through public interfaces via integration tests.
Maintains governance around testing workflow, including behavior-spec alignment and explicit entry points for each task.
Provides practical guidelines on mocking, interface design, and troubleshooting to keep tests robust and decoupled from implementation.

Quick Start

Begin a tracer bullet by writing a failing test for the next behavior, then implement the minimal code to pass it.

Frequently Asked Questions about gxpm-tdd

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

FAQPage Schema

How do I enforce test-first development for new features and bug fixes?▼

Test-first development is enforced by requiring failing integration tests to exist before any production code is written. This ensures features are implemented only after tests validate the intended behavior through public interfaces.

What is the red-green-refactor cycle and how does it drive production changes?▼

The red-green-refactor cycle drives production changes by first writing a failing test, implementing the minimal code to pass it, and then refactoring. This deterministic flow reduces production risk by ensuring behavior-spec alignment.

How do I validate behavior using vertical-slice tracer bullets?▼

Vertical-slice tracer bullets validate behavior by writing failing integration tests that target public interfaces. This approach ensures tests remain decoupled from implementation details while verifying end-to-end functionality.

Can I use integration tests to align behavior specs with production code?▼

Yes, integration tests align behavior specs with production code by acting as explicit entry points for each task. This governance keeps testing workflows auditable and ensures minimal code satisfies the required behavior.

What are the limitations of mocking when keeping tests decoupled from implementation?▼

Mocking limitations are mitigated by providing practical guidelines on interface design. This keeps tests robust and decoupled from implementation details, preventing brittle tests that break during refactoring.

Why does test-first discipline reduce production risk during feature implementation?▼

Test-first discipline reduces production risk by ensuring features are validated end-to-end only after failing tests are written and passed. This auditable flow guarantees that production changes strictly adhere to behavior specifications.