hf-test-driven-dev

Enforce test-design approval before RED/GREEN cycles in HF workflows.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/hujianbest/garage-agent --skill hf-test-driven-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hf-test-driven-dev
Source: https://github.com/hujianbest/garage-agent/tree/main/packs/coding/skills/hf-test-driven-dev
Command: npx skills add https://github.com/hujianbest/garage-agent --skill hf-test-driven-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a disciplined entry point for HF's test-driven development workflow, ensuring that a single active task is tackled with test designs approved before any implementation, and that handoffs and evidence are properly documented.

Core Features & Use Cases

  • Enforces test-design approval prior to RED/GREEN cycles for the active task.
  • Bridges task planning, design, implementation, and review gates with a single entry point.
  • Captures Refactor Notes, Hat Discipline, and Architectural Conformance evidence to support traceability and audits.

Quick Start

先产出测试设计并等待确认,然后进入 RED/GREEN/REFACTOR 循环。

Frequently Asked Questions about hf-test-driven-dev

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

FAQPage Schema
How do I enforce test design approval before starting RED/GREEN cycles?

Test design approval before RED/GREEN cycles is enforced by automating a disciplined test-driven development workflow that gates implementation until the test design is explicitly confirmed for the active task.

What is the best way to track refactor notes and architectural conformance during TDD?

Tracking refactor notes and architectural conformance during TDD is handled by capturing hat discipline evidence and conformance checks, recording them directly into specified feature folders for auditability.

How do I bridge task planning and design-review gates for a single active task?

Bridging task planning and design-review gates for a single active task is achieved through a unified entry point that connects post-approval implementations, controlled hotfixes, and gate-reviewed handoffs.

Can I use this TDD workflow for post-approval task implementations and hotfixes?

Yes, this TDD workflow applies to post-approval task implementations and controlled hotfixes, automating the entire test-driven development cycle while maintaining design-review discipline.

Does this test-driven development workflow require specific folder structures for evidence?

Yes, the test-driven development workflow requires specified feature folders to properly record architectural conformance checks, hat discipline, and refactor notes evidence for traceability.

Why do I need to wait for confirmation before entering the RED/GREEN/REFACTOR loop?

Waiting for confirmation before entering the RED/GREEN/REFACTOR loop ensures strict test-driven development discipline by requiring explicit test design approval prior to any implementation work.