team-shinchan:test-driven-development

Enforce test-first development with failing tests before production code.

8|2|Updated Feb 3, 2026

Search Tags:#workflow #testing #tdd #red-green-refactor #unit-testing #quality-assurance #test-driven-development

One-click install

npx skills add https://github.com/seokan-jeong/team-shinchan --skill team-shinchan-test-driven-development

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: team-shinchan:test-driven-development
Source: https://github.com/seokan-jeong/team-shinchan/tree/main/skills/test-driven-development
Command: npx skills add https://github.com/seokan-jeong/team-shinchan --skill team-shinchan-test-driven-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a strict test-first workflow so production code cannot be added without a failing test, reducing regressions, unchecked design drift, and debugging time during Stage 3 execution.

Core Features & Use Cases

TDD enforcement: Require a failing test before any production change is written.
RED-GREEN-REFACTOR workflow: Guide the developer through writing a failing test, implementing the minimal code to pass, and refactoring while keeping tests green.
Anti-pattern guidance and exceptions: Lists common anti-patterns to avoid and allows skipping TDD only with explicit human approval for throwaway prototypes or documentation-only changes.
Use Case: When fixing a bug or adding a feature, block commits that don't start with a failing test and ensure the test suite is run after refactors.

Quick Start

Require the agent to create a failing test for the new behavior, make the minimal production change to pass that test, and run the test suite after refactoring.

Frequently Asked Questions about team-shinchan:test-driven-development

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

FAQPage Schema

How do I enforce test-first development during feature implementation?▼

To enforce test-first development, require a failing test before any production code is written. This prevents unchecked design drift and ensures minimal code changes to pass tests during feature implementation.

What is the RED-GREEN-REFACTOR workflow in unit testing?▼

The RED-GREEN-REFACTOR workflow in unit testing requires writing a failing test first, implementing minimal production code to pass that test, and then refactoring while keeping the test suite green.

Can I skip test-driven development for throwaway prototypes?▼

You can skip test-driven development for throwaway prototypes or documentation-only changes, but only with explicit human approval. Otherwise, TDD enforcement blocks commits not starting with a failing test.

Why should I run the test suite after refactoring production code?▼

Running the test suite after refactoring production code ensures the changes maintain passing tests. This TDD step verifies that structural improvements do not introduce regressions or break existing behavior.