test-driven-development

Guide teams through RED-GREEN-REFACTOR cycles for Test-Driven Development.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/bilgrami/corporate-agent --skill test-driven-development-bilgrami
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/bilgrami/corporate-agent/tree/main/skills/test-driven-development
Command: npx skills add https://github.com/bilgrami/corporate-agent --skill test-driven-development-bilgrami

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the Test-Driven Development workflow by guiding teams through RED-GREEN-REFACTOR cycles.

Core Features & Use Cases

  • Structured TDD workflow guiding RED-GREEN-REFACTOR cycles for feature work.
  • Documentation of each cycle with examples and prompts for next steps.
  • Supports knowledge transfer, consistent testing practices, and maintainable code design.

Quick Start

Run a new TDD cycle by writing a failing test, then implement the minimum code to pass, followed by refactoring.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
What is the red-green-refactor cycle in test-driven development?

The red-green-refactor cycle in test-driven development is a workflow where you write a failing test, implement the minimal code to make it pass, and then refactor while preserving test coverage.

How do I automate test-driven development workflows for feature work?

You can automate test-driven development workflows by using structured guidance that prompts your team through writing failing tests, creating minimal implementations, and refactoring code with documented examples for each step.

Can I use pytest for unit testing during red-green-refactor cycles?

Yes, pytest is explicitly supported for unit testing within the test-driven development workflow, guiding you through failing tests, minimal implementations to green, and subsequent refactoring phases.

Does test-driven development work for maintenance tasks and refactoring existing code?

Yes, test-driven development applies to both feature work and maintenance tasks, providing explicit steps for introducing new functionality and refactoring existing code while preserving test coverage.

How do I maintain unit-testing coverage when refactoring code?

You maintain unit-testing coverage during refactoring by following the test-driven development cycle, which specifies writing failing tests first, implementing minimal code to pass, and refactoring with explicit documentation to preserve coverage.