skills.rest
xxih
xxihCOMMUNITY
Explore all skills by this author →
GitHub

quality-tdd

Enforce test-first development by requiring failing tests before minimal implementations.

1|Updated Mar 18, 2026
Search Tags:#tdd#refactor#quality-assurance#bugfix#test-driven-development#tests
One-click install
npx skills add https://github.com/xxih/ai-harness-zh --skill quality-tdd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quality-tdd
Source: https://github.com/xxih/ai-harness-zh/tree/main/packages/quality-workflows/targets/codex/skills/quality-tdd
Command: npx skills add https://github.com/xxih/ai-harness-zh --skill quality-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill enforces a test-first approach, requiring failing tests before implementing features and guiding developers to produce minimal, purpose-built changes while preserving behavior.

Core Features & Use Cases

  • Fail-first testing discipline: write tests that fail before coding to define expected behavior.
  • Minimal implementation: implement only what is necessary to satisfy the failing tests, avoiding over-engineering.
  • Quality recording: capture TDD phase outcomes in a designated log (e.g., .quality/quality-check.md) for traceability.

Quick Start

Write a failing test for the target behavior, implement the minimal code to pass it, and record the results in .quality/quality-check.md.

Frequently Asked Questions about quality-tdd

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

FAQPage Schema
How do I enforce test-driven development discipline for feature development and bug fixes?▼

Test-driven development discipline is enforced by requiring failing tests before writing production code, then implementing minimal changes to satisfy those tests and recording outcomes in a .quality directory.

What is the minimal implementation approach in test-first development?▼

Minimal implementation in test-first development means writing only the production code necessary to pass the failing tests, avoiding over-engineering while preserving expected behavior.

How do I guide refactoring with tests to preserve existing behavior?▼

Refactoring with tests requires writing failing tests that define expected behavior first, then making minimal code changes to pass them, ensuring reliable behavior preservation.

Does test-driven development require a specific directory structure for quality recording?▼

Test-driven development quality recording uses a designated log file, specifically .quality/quality-check.md, to capture TDD phase outcomes and ensure traceability of test results.

When should I not use a fail-first testing discipline approach?▼

Fail-first testing discipline may not suit exploratory coding or throwaway prototypes where defining expected behavior upfront is impractical, as it strictly requires failing tests before implementation.

Related Skills

Explore More Software Engineering Skills→
Magnatrix-LabMagnatrix-Lab
1

webapp-testing

Automate web application testing with Playwright and generate summary reports.

Community
Intermediate
phrazzldphrazzld
13

build

Implement code through iterative test-driven development cycles.

Community
Intermediate
gautam-achieveaigautam-achieveai
2

clean-builds

Automates code quality tools and package version validation in .NET projects.

Community
Advanced
baphledbaphled
1

bdd-workflow

Define executable Gherkin specifications for RSpec, Ginkgo, and Jest workflows.

Community
Intermediate