shared-tdd

Enforce red-green-refactor TDD cycles with test-based completion gates.

3|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/edfenton/claude-skills --skill shared-tdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shared-tdd
Source: https://github.com/edfenton/claude-skills/tree/main/shared/shared-tdd
Command: npx skills add https://github.com/edfenton/claude-skills --skill shared-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes and enforces test-driven development practices across all platforms to ensure tests exist before features are completed.

Core Features & Use Cases

  • Mandatory TDD workflow: Red-Green-Refactor steps enforced.
  • Evidence requirements: commits/PRs must include tests and notes.
  • Completion gate: stories cannot be marked complete without test files.

Quick Start

Write a failing test first, implement the minimal code to pass, then refactor while keeping all tests green.

Frequently Asked Questions about shared-tdd

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

FAQPage Schema
How do I enforce a test-driven development workflow across different platforms?

You can enforce a test-driven development workflow by applying automated policies that mandate red-green-refactor cycles and block story completion without passing test files. This ensures consistent TDD practices across all software development contexts.

Why does my development process allow stories to be marked complete without test evidence?

Your development process lacks a completion gate requiring test evidence. Implementing a mandatory test-first policy ensures stories cannot be marked complete without associated test files and explicit verification notes in commits or PRs.

How do I require failing tests before writing implementation code in my development process?

To require failing tests first, enforce a strict red-green-refactor cycle where developers must write a failing test, implement minimal code to pass, and then refactor while keeping all tests green. This prevents skipping the initial test phase.

Can I use test-first workflow enforcement for any software development context?

Yes, test-first workflow enforcement applies to software development tasks across all platforms. It guides developers uniformly to write tests before code, verify failing tests, and ensure green tests before completion, regardless of the specific project.

Does commit evidence for TDD require test files in pull requests?

Yes, commit evidence for TDD requires explicit test files and notes in commits or PRs. This functional requirement ensures that test-based completion gates are satisfied before any story is marked as complete.

What is the best way to standardize quality assurance practices across multiple development platforms?

The best way to standardize quality assurance is to automate enforcement of TDD practices across platforms, requiring red-green-refactor cycles and test-based completion gates to guarantee tests exist before features are completed.