skills.rest
SethyPagna
SethyPagnaCOMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Enforce test-first development with RED-GREEN-REFACTOR cycles.

Updated May 14, 2026
Search Tags:#testing#tdd#refactoring#red-green-refactor#quality-assurance#unit-tests
One-click install
npx skills add https://github.com/SethyPagna/Secretary-Jarvis --skill test-driven-development-sethypagna
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/SethyPagna/Secretary-Jarvis/tree/main/src/capabilities/skills/software-development/test-driven-development
Command: npx skills add https://github.com/SethyPagna/Secretary-Jarvis --skill test-driven-development-sethypagna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents ad hoc coding by making test-first development the default, so features, fixes, and refactors are verified before production code lands.

Core Features & Use Cases

  • Enforces the RED-GREEN-REFACTOR cycle for new work and bug fixes.
  • Guides you to write one clear failing test, confirm it fails for the right reason, implement the smallest passing change, and then refactor safely.
  • Useful when you need reliable behavior changes, regression protection, or a disciplined workflow for shared codebases and automation tasks.

Quick Start

Ask me to help you implement a change using strict TDD, starting with the failing test and then the minimal code needed to make it pass.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
How do I start writing unit tests before implementing new features?▼

The RED-GREEN-REFACTOR cycle ensures test-first development by requiring you to write one failing test, implement the minimal code to make it pass, and then refactor safely while maintaining repeatable verification.

Can I use test-first development for bug fixes and refactoring?▼

Yes, test-first development applies to bug fixes and refactors by guiding you to write a failing test that verifies the specific behavior change, ensuring regression protection before any production code is written.

Why do I need to confirm a test fails for the right reason before writing code?▼

Confirming a test fails for the right reason ensures your unit tests are actually validating the intended behavior change, preventing false positives and ensuring repeatable verification of your production code.

What's the best way to enforce strict TDD discipline in a shared codebase?▼

Enforce strict TDD discipline by preventing production code from being written without a failing test, applying one-behavior tests, and running full-suite checks to ensure safe delivery and reliable regression protection.

Does test-driven development prevent ad hoc coding for automation tasks?▼

Yes, test-driven development prevents ad hoc coding by making test-first verification the default workflow, ensuring features and fixes for automation tasks are fully verified by failing tests before implementation.

Related Skills

Explore More Software Engineering Skills→
ChiejiChieji

test-driven-development

Guide Red-Green-Refactor cycles with failing tests before implementation.

Community
Intermediate
guccangguccang
3

test-driven-development

Create failing tests before implementing minimal production code.

Community
Intermediate
lgzarturolgzarturo

cc-tdd-cycle

Automate red/green/refactor TDD cycles with explicit phase sequencing.

Community
Intermediate
TheBushidoCollectiveTheBushidoCollective
187

bdd-principles

Conduct Three Amigos sessions and produce executable scenarios for BDD workflows.

Official
Intermediate