test-driven-development

Enforce test-driven development with failing tests before implementation.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/stabilefrisur/panmetis --skill test-driven-development-stabilefrisur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/stabilefrisur/panmetis/tree/main/src/panmetis/skills/test-driven-development
Command: npx skills add https://github.com/stabilefrisur/panmetis --skill test-driven-development-stabilefrisur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces test-driven development in software projects.

Core Features & Use Cases

  • Encourages writing failing tests first to guide implementation.
  • Improves code quality and regression safety across features and bugfixes.
  • Use case: apply TDD for new features, bug fixes, and refactors to ensure behavior is test-driven.

Quick Start

Create a failing test first, then implement the minimal code to pass it, and repeat.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
How do I enforce test-driven development for new features and bug fixes?

To enforce test-driven development, you write a failing test first to define behavior, then implement the minimal code required to pass that test, and repeat the cycle for features and bug fixes.

What is the best way to start a TDD workflow for code refactoring?

The best way to start a TDD workflow for refactoring is to create a failing test that defines the expected behavior, implement the code changes to pass it, and repeat to ensure regression safety.

Does test-driven development improve code quality during software development?

Yes, test-driven development improves code quality by requiring tests to define behavior before coding, which increases regression safety across feature work, bug fixes, and refactoring tasks.

How do I set up a project to apply TDD discipline across my team?

You set up TDD discipline by configuring a SKILL.md frontmatter with a name and description, then using the Markdown body for execution instructions, with optional scripts and references directories for extended guidance.

When should I use a tests-first approach instead of writing tests later?

You should use a tests-first approach whenever you need to ensure tests define behavior before coding, specifically when applying TDD to new features, bug fixes, and refactors to maintain regression safety.