test-driven-development

Enforce test-first development with RED-GREEN-REFACTOR cycles in Python projects.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/LamseyahElias/jarvis-cloud-v2 --skill test-driven-development-lamseyahelias
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/LamseyahElias/jarvis-cloud-v2/tree/main/hermes-agent/skills/software-development/test-driven-development
Command: npx skills add https://github.com/LamseyahElias/jarvis-cloud-v2 --skill test-driven-development-lamseyahelias

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Projects often ship code without automated tests, leading to regressions and fragile features. This skill codifies a test-first mindset to prevent defects by requiring tests before implementation.

Core Features & Use Cases

  • Test-first discipline: enforce writing tests before production code to crystallize expected behavior.
  • Red-Green-Refactor workflow: guide development through rapid cycles of failing tests, minimal code, and refactoring.
  • Real-world use case: when adding a new feature, start with a failing test, implement the smallest necessary code to pass, then refactor for quality and maintainability.

Quick Start

Write a failing test first, then implement the minimal production code required to pass.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
What is test-driven development and how does it prevent software regressions?

Test-driven development is a test-first workflow requiring you to write a failing test before production code, ensuring expected behavior is crystallized upfront to prevent regressions and fragile features.

How do I apply red-green-refactor cycles when adding a new feature in Python?

To apply red-green-refactor cycles, write a failing test first, implement the minimal production code required to pass that test, then refactor the code for quality and maintainability before repeating the cycle.

Can I use this test-first workflow for bug fixes and refactoring existing code?

Yes, test-first development applies to feature work, bug fixes, and refactors in Python projects by guiding implementation through writing a failing test before modifying any production code.

Do I need pytest to enforce strict test-driven development in my software projects?

This skill enforces strict test-driven development in Python projects using tests to guide implementation, making pytest the targeted testing framework for executing the required red-green-refactor cycles.

What is the best way to start a unit-testing cycle for a new software feature?

The best way to start unit-testing is to write a failing test first that defines the expected behavior, then implement the smallest necessary production code to pass it before refactoring.

Why write a failing test before writing any production code?

Writing a failing test before production code crystallizes expected behavior and enforces a test-first discipline, ensuring the feature is defined by its requirements rather than its implementation.