test-driven-development

Enforce test-first routing and verification for software development tasks.

968|43|Updated Apr 30, 2026

Search Tags:#workflow #testing #tdd #verification #red-green-refactor #coding-standards #preflight

Ready to run

npx skills add https://github.com/GanyuanRan/Aegis --skill test-driven-development-ganyuanran

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/GanyuanRan/Aegis/tree/main/skills/test-driven-development
Command: npx skills add https://github.com/GanyuanRan/Aegis --skill test-driven-development-ganyuanran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces strict Test-Driven Development discipline to ensure tests define behavior before production code, reducing risk and promoting evidence-driven progress.

Core Features & Use Cases

TDD Route guidance: auto vs off modes with strict, light, or skipped decisions to control test-first workflow.
Preflight gate: evaluates complexity signals and routes work to appropriate planning steps before coding.
Red-Green-Refactor lifecycle: codifies the practice of writing failing tests first, then implementing minimal code to pass and refactor with green feedback.
Verification-before-completion: ensures fresh evidence is produced and validated prior to task closure.
Slice-level governance: supports planning, documentation, and traceability for task intent and completion criteria.

Quick Start

Before coding, decide the TDD Route and outline a minimal failing test that proves the intended behavior.

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 strict test-first routing for new features and bug fixes?▼

Strict test-first routing is enforced by evaluating complexity signals during a preflight gate and routing work to outline a minimal failing test that proves intended behavior before production code.

What is the red-green-refactor lifecycle in test-driven development?▼

The red-green-refactor lifecycle codifies writing failing tests first, implementing minimal code to pass them, and then refactoring with continuous green feedback to ensure behavior is proven.

Can I skip test-driven development for low-complexity coding tasks?▼

Yes, you can configure the TDD Route decision as strict, light, or skipped based on complexity evaluation, allowing you to bypass formal verification for low-risk work.

How do I verify code behavior before task closure in a structured workflow?▼

Verification-before-completion discipline ensures fresh evidence is produced and validated prior to task closure, proving behavior is met through slice-level governance and traceability.

When do I need a preflight gate for software refactoring?▼

A preflight gate is needed for high-complexity refactoring to evaluate risk signals, route work to appropriate planning steps, and define completion criteria before coding begins.