test-driven-development

Enforce test-first workflows with failing tests before implementation.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/Kristopherlb/shinobi-wan --skill test-driven-development-kristopherlb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/Kristopherlb/shinobi-wan/tree/main/.cursor/skills/test-driven-development
Command: npx skills add https://github.com/Kristopherlb/shinobi-wan --skill test-driven-development-kristopherlb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers reduce regressions and implementation uncertainty by enforcing a disciplined workflow that starts with failing tests and validates changes through deterministic verification.

Core Features & Use Cases

  • Test-First Development: Guides feature work, bug fixes, refactors, and scripts by writing focused failing tests before implementation.
  • Deterministic Testing Practices: Promotes isolated tests, boundary validation, controlled environments, and avoidance of flaky dependencies.
  • Use Case: Apply this Skill when adding a CLI feature or fixing an API behavior to define the expected contract first, implement the smallest solution, and safely refactor afterward.

Quick Start

Use the test-driven-development skill to create a failing test for my feature request, implement the minimum change needed, and refactor while keeping tests passing.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
How do I use test-driven development for fixing bugs and refactoring code?

Test-driven development for bug fixes and refactoring starts by writing a deterministic failing test that defines the expected behavior, implementing the minimum code change to pass it, and safely refactoring while keeping tests green.

What is the red-green-refactor workflow in software development?

The red-green-refactor workflow is an incremental test-first development practice where you write a failing test, implement the minimum solution to make it pass, and then improve the code structure without breaking behavior.

How do I write deterministic tests for CLI tools and API boundary contracts?

Writing deterministic tests for CLI tools and APIs requires isolated test environments, clear behavior assertions, and controlled dependencies to prevent flaky results when validating boundary contracts during feature implementation.

Can I apply test-first development workflows to scripts and feature implementation?

Yes, test-first development workflows apply directly to scripts and feature implementation by enforcing focused failing tests before writing code, ensuring changes are validated through deterministic verification across various software development scenarios.

Why does my test-driven development workflow produce flaky tests?

Flaky tests in test-driven development usually occur when tests lack isolation or depend on uncontrolled environments, which is why this approach enforces deterministic isolated tests and boundary validation to eliminate unpredictable failures.