ward

Guide red/green/refactor TDD cycles for one behavior at a time.

12|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Alexander-Tyagunov/magician --skill ward
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ward
Source: https://github.com/Alexander-Tyagunov/magician/tree/main/skills/ward
Command: npx skills add https://github.com/Alexander-Tyagunov/magician --skill ward

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces a strict red → green → refactor TDD cycle for one behavior at a time to reduce defects and drive incremental progress.

Core Features & Use Cases

  • One-behavior-per-cycle discipline that guides how to write a failing test, make it pass, and refactor without changing behavior.
  • Clear rules on what constitutes a single behavior (function, endpoint, or UI state) to prevent scope creep.
  • Provides guidance for teams on when and how to stop and certify completion before moving to the next behavior.

Quick Start

Start a new behavior by writing a failing test that describes a single behavior, then implement and refactor until the test passes.

Frequently Asked Questions about ward

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

FAQPage Schema
How do I enforce a strict test-driven development cycle for individual features?

To enforce a strict test-driven development cycle, you write a failing test for a single behavior, implement the minimum code to make it pass, and then refactor. This red-green-refactor discipline ensures incremental progress and reduces software defects before moving to the next feature.

What counts as a single behavior when practicing test-driven development?

A single behavior in test-driven development is defined as a function, an endpoint, or a UI state. Defining behaviors at this granular level prevents scope creep and ensures you complete one cycle before starting the next task.

When should I stop refactoring during a TDD cycle?

You should stop refactoring during a TDD cycle when you can certify completion. This completion signal confirms that the behavior's tests pass and the code is clean, allowing you to safely move on to defining the next behavior.

Can I use test-driven development cycles for debugging existing code?

Yes, test-driven development cycles apply to debugging work as well as feature development. By isolating the bug as a single behavior, you write a failing test that reproduces the issue, fix the code to pass the test, and refactor safely.

Do I need any specific testing frameworks to start writing failing tests for behaviors?

No specific testing frameworks are required. The approach applies across any software project, relying on your existing test runner to execute the red-green-refactor cycle for the behaviors you define.