skills.rest
ShaggyD
ShaggyDCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sdlc-4-test-driven-development

Implement a Red-Green-Refactor workflow with tests before code changes.

2|Updated Apr 30, 2026
Search Tags:#testing#tdd#quality assurance#debugging#regression#sdlc
One-click install
npx skills add https://github.com/ShaggyD/agent-toolkit --skill sdlc-4-test-driven-development
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdlc-4-test-driven-development
Source: https://github.com/ShaggyD/agent-toolkit/tree/main/development/sdlc-4-test-driven-development
Command: npx skills add https://github.com/ShaggyD/agent-toolkit --skill sdlc-4-test-driven-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the lack of verification in development workflows, preventing bugs from reaching production by mandating that tests are written before implementation.

Core Features & Use Cases

  • Red-Green-Refactor Cycle: Provides a structured framework for writing failing tests, implementing minimal code, and refactoring safely.
  • Prove-It Pattern: Ensures bug fixes are permanent by requiring a reproduction test case before applying any code changes.
  • Test Pyramid Strategy: Guides the user on balancing unit, integration, and E2E tests to maximize coverage while maintaining suite speed.

Quick Start

Use the sdlc-4-test-driven-development skill to create a regression test for the reported bug in the user authentication module.

Frequently Asked Questions about sdlc-4-test-driven-development

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

FAQPage Schema
How do I implement test-driven development to prevent code regressions?▼

Test-driven development prevents regressions by enforcing the Red-Green-Refactor cycle, requiring you to write failing tests before implementing minimal code and refactoring safely across all software development phases.

How does the Prove-It pattern work for fixing bugs?▼

The Prove-It pattern ensures bug fixes are permanent by requiring you to write a reproduction test case that verifies the defect before applying any code changes to the implementation.

What is the best way to balance unit, integration, and E2E tests for coverage?▼

The Test Pyramid Strategy guides you in balancing unit, integration, and E2E tests to maximize behavioral coverage while maintaining fast execution speeds for your test suite.

Can I apply TDD workflows to refactoring and bug fixing tasks?▼

Yes, the TDD workflow applies to all software development phases including new feature implementation, bug fixing, and refactoring by mandating rigorous verification through the Red-Green-Refactor cycle.

Why should I write regression tests before fixing an authentication module bug?▼

Writing regression tests before fixing an authentication module bug ensures the reported defect is permanently resolved by proving the error exists and verifying your code changes correct it without regressions.

Related Skills

Explore More Software Engineering Skills→
ReinaMacCredyReinaMacCredy
223

test-driven-development

Enforce the Red-Green-Refactor cycle with failing tests before implementation.

Community
Intermediate
GainInsightDevGainInsightDev

af-analyse-test-coverage

Analyze test coverage reports to identify untested code paths and gaps.

Official
Intermediate
DevelopersGlobalDevelopersGlobal
65

ci-cd-pipelines

Automate CI/CD pipelines with quality gates and deployment processes.

Official
Advanced
maystudiosmaystudios
10

tdd

Guide teams through red-green-refactor cycles with atomic commits per phase.

Community
Intermediate