tdd-execution

Coordinate RED-GREEN-REFACTOR cycles with CLI validation gates and phase commits.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/gonz0w/bgsd-oc --skill tdd-execution-gonz0w
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-execution
Source: https://github.com/gonz0w/bgsd-oc/tree/main/skills/tdd-execution
Command: npx skills add https://github.com/gonz0w/bgsd-oc --skill tdd-execution-gonz0w

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralized, standardized TDD workflow definition that coordinates planning and execution cycles to ensure consistent quality and traceability across phases.

Core Features & Use Cases

  • Canonical TDD contract for planner and executor guiding RED-GREEN-REFACTOR cycles.
  • CLI-driven validation gates and explicit commit protocol per phase to ensure auditable artifacts.
  • Context budgeting and structured artifacts like test and feature commits to maintain iteration discipline.

Quick Start

Start a RED-GREEN-REFACTOR cycle by invoking the canonical CLI flow to plan and execute a TDD task.

Frequently Asked Questions about tdd-execution

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

FAQPage Schema
How do I enforce a standardized TDD workflow across my development team?

You can enforce a standardized TDD workflow by applying a canonical contract that coordinates planner and executor cycles, ensuring consistent RED-GREEN-REFACTOR execution and traceable commits across the team.

What is the best way to structure commits during a RED-GREEN-REFACTOR cycle?

The best way to structure commits in a RED-GREEN-REFACTOR cycle is using an explicit commit protocol that generates structured test and feature artifacts, maintaining iteration discipline and creating auditable phase targets.

How do CLI validation gates improve TDD execution?

CLI validation gates improve TDD execution by enforcing explicit phase targets before transitions, ensuring that each RED, GREEN, and REFACTOR stage meets canonical quality requirements before generating an artifact commit.

When do I need a formalized TDD contract for task planning and execution?

You need a formalized TDD contract when tasks require strict coordination between planning and execution cycles, explicit phase targets, and CLI-based validation gates to maintain quality and traceability.

Does this TDD approach support context budgeting during development iterations?

Yes, this TDD approach supports context budgeting by utilizing structured artifacts like test and feature commits, which coordinate planning and execution cycles to maintain iteration discipline without overwhelming the context.