wa:dev-feature-tdd

Coordinate red/green TDD cycles for epic child issues with verification gates.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-dev-feature-tdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wa:dev-feature-tdd
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/dev-feature-tdd
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-dev-feature-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of reliably developing complex features by enforcing a strict red/green TDD workflow with explicit verification gates, reducing regressions and missed requirements.

Core Features & Use Cases

  • End-to-end TDD orchestration: Plans and sequences work for epic child issues, automatically routing which prefixes must follow red/green cycles versus direct development.
  • Automated failing-test creation (red): Generates a failing test suite from acceptance criteria, with stage-based status updates and explicit “test-only” constraints.
  • Green development that satisfies tests: Directs minimal production code changes to make the previously failing tests pass, without modifying the tests.

Quick Start

Ask the skill to run TDD development for epic WA-123 by requesting: "Develop epic WA-123 using strict red/green TDD with verification gates."

Frequently Asked Questions about wa:dev-feature-tdd

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

FAQPage Schema
How do I enforce strict red green TDD cycles for complex feature development?

Red green TDD coordinates feature development by creating deterministic failing tests from acceptance criteria, then directing minimal production code changes to make those tests pass without modifying the tests.

What is test-first development orchestration for epic child issues?

Test-first development orchestration sequences epic child issue work by routing items through mandatory red green cycles, applying dependency-aware batching and repo or branch preparation before generating failing tests.

How do I automate failing test creation from acceptance criteria?

Automate failing test creation by applying deterministic test-only red instructions derived from acceptance criteria, ensuring the generated test suite fails initially and includes stage-based status updates for tracking.

Can I use test-driven development orchestration for backend, frontend, and bot work items?

Yes, test-driven development orchestration applies to backend, frontend, bot, and security work items that require test-first behavior, routing each through disciplined red green cycles with gate verification.

What are the limitations of automated TDD gate verification?

Automated TDD gate verification requires stage-based planning with explicit user approval and relies on deterministic test, lint, and format commands, meaning it cannot bypass verification gates or handle work items lacking acceptance criteria.