When should I use the Requirements Clarification skill?

Use this skill during the pre-RED phase of TDD, particularly when feature descriptions are brief, lack acceptance criteria, or involve complex business logic.

What kind of questions does this skill ask?

The skill focuses on four main categories: functional requirements, edge cases and boundaries, error handling, and technical constraints such as existing interfaces.

Can I skip the clarification phase for simple tasks?

Yes, you can skip it for simple CRUD operations, bug fixes with clear reproduction steps, or when the user provides comprehensive test scenarios upfront.

How does this skill improve the TDD process?

It ensures that the developer understands exactly what behavior to test, reducing logic errors and preventing the 'false green' scenario where tests pass but don't meet business needs.

TDD Requirements Clarifier

Name: TDD Requirements Clarifier
Author: DoubleslashSE

byDoubleslashSE

•

Security & Testing

Facilitates the pre-testing phase of TDD by uncovering ambiguities, defining acceptance criteria, and identifying edge cases before code is written.

About

The Requirements Clarification skill is designed to optimize the Test-Driven Development (TDD) workflow by ensuring developers have a precise understanding of 'what' to test before the RED phase begins. It uses a structured inquiry framework to identify missing business rules, boundary conditions, and error-handling requirements that are often overlooked in initial feature descriptions. By formalizing acceptance criteria and technical constraints early, the skill helps prevent logic errors and reduces the need for expensive rework caused by misunderstood specifications.

Key Features

Pre-RED phase ambiguity detection to identify vague requirements
Formalization of acceptance criteria and expected outputs
Targeted questioning for edge cases, null handling, and boundary values
Technical dependency analysis for existing abstractions and patterns
1 GitHub stars
Standardized requirements summary template for project documentation

Use Cases

Identifying necessary test scenarios for legacy code refactoring
Defining error-handling behavior for API endpoints with vague specs
Clarifying complex business logic before writing initial unit tests

About

Key Features

Pre-RED phase ambiguity detection to identify vague requirements
Formalization of acceptance criteria and expected outputs
Targeted questioning for edge cases, null handling, and boundary values
Technical dependency analysis for existing abstractions and patterns
1 GitHub stars
Standardized requirements summary template for project documentation

Use Cases

Identifying necessary test scenarios for legacy code refactoring
Defining error-handling behavior for API endpoints with vague specs
Clarifying complex business logic before writing initial unit tests