specdo-tdd

Automate test-first implementation for behavior-changing tasks within the SpecDo lifecycle.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MoonCoder-HAPPY/SpecDo --skill specdo-tdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specdo-tdd
Source: https://github.com/MoonCoder-HAPPY/SpecDo/tree/main/specdo-tdd
Command: npx skills add https://github.com/MoonCoder-HAPPY/SpecDo --skill specdo-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates test-first implementation for behavior-changing tasks within the SpecDo lifecycle, ensuring a validated apply context and safe progression through wrappers.

Core Features & Use Cases

  • Enforces a complete apply context (task_scope, handoff_payload, gate_history) before execution.
  • Guides a red-green wrapper flow between specdo-apply, specdo-debugging, and code-review for behavior-changing work.
  • Provides explicit gate contracts and next-step guidance when failures occur, with documented lifecycle rules.

Quick Start

Provide a resolved active apply payload and run the SpecDo TDD wrapper to begin test-first implementation

Frequently Asked Questions about specdo-tdd

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

FAQPage Schema
How do I enforce test-driven development for behavior-changing tasks?

Test-driven development for behavior-changing tasks is enforced by automating a test-first wrapper flow that validates the apply context and gates progression through verification steps. This ensures safe code changes within the lifecycle.

What is a red-green wrapper flow in test-first implementation?

A red-green wrapper flow in test-first implementation guides progression between specdo-apply, specdo-debugging, and code-review. It provides explicit gate contracts and next-step guidance when failures occur during behavior-changing work.

How do I validate an apply context before executing code changes?

To validate an apply context before executing code changes, you must provide a complete apply payload containing task_scope, handoff_payload, and gate_history. This satisfies the wrapper contract for safe progression.

When do I need to use verification gates for test-first implementation?

Verification gates for test-first implementation are needed when applying code changes that alter behavior and require validation. These gates ensure a safe progression through the appropriate next steps of the wrapper lifecycle.

Does test-driven development work with existing debugging and code review workflows?

Test-driven development integrates with debugging and code review workflows by guiding a red-green wrapper flow between specdo-apply, specdo-debugging, and code-review components. This coordinates behavior-changing tasks across the lifecycle.