use-case-to-tdd

Transform reviewed use cases into four-level RED TDD test suite skeletons.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/bflandev/threadline-ai --skill use-case-to-tdd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: use-case-to-tdd
Source: https://github.com/bflandev/threadline-ai/tree/main/skills/use-case-to-tdd
Command: npx skills add https://github.com/bflandev/threadline-ai --skill use-case-to-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Derive a complete, four-layer test suite from reviewed use cases, ensuring every test starts RED before any implementation, thus guiding downstream development and ensuring test-first discipline.

Core Features & Use Cases

  • Maps use-case elements to acceptance, domain unit, interactor, and integration tests.
  • Produces deterministic scaffolds, naming conventions, and stubs ready for wiring to real code.
  • Enforces RED-only tests until Gate 2 approves implementation, supporting end-to-end traceability.

Quick Start

Describe a READY use case and ask this skill to generate the full RED test-suite skeleton.

Frequently Asked Questions about use-case-to-tdd

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

FAQPage Schema
How do I generate a TDD test suite skeleton from use cases?▼

To generate a TDD test suite skeleton from use cases, provide a reviewed use case and the skill maps every element to acceptance, domain unit, interactor, and integration test stubs. This produces deterministic scaffolds with naming conventions ready for implementation.

What is a four-level TDD test suite and how does it map to use cases?▼

A four-level TDD test suite maps use-case elements across acceptance, domain unit, interactor, and integration tests. This ensures every use-case scenario translates directly into specific test artifacts, maintaining end-to-end traceability and test-first discipline.

How do I enforce RED tests before writing implementation code?▼

To enforce RED tests before implementation, the skill generates test stubs designed to fail by default and maintains RED-only status until Gate 2 approves. This guarantees test-first discipline and guides downstream development systematically.

Can I use reviewed use cases to create acceptance and domain tests?▼

Yes, you can use reviewed use cases to create acceptance and domain tests. The skill transforms reviewed use cases into a complete test suite, mapping use-case elements directly to acceptance tests and domain unit tests alongside interactor and integration scaffolds.

What's the best way to start test-first development with use cases?▼

The best way to start test-first development with use cases is to input a READY use case into the skill to generate the full RED test-suite skeleton. This provides deterministic scaffolds and stubs, ensuring all tests fail by design before any coding begins.

Why do my acceptance tests need to stay RED until implementation approval?▼

Acceptance tests need to stay RED until implementation approval to enforce strict test-first discipline and end-to-end traceability. The skill designs all tests to fail by default, blocking implementation until Gate 2 explicitly authorizes downstream development.