What problem does it solve? Requirements often contain vague terms like "fast" or "user-friendly" that cannot be verified, and defects in requirements are only discovered after code is written. This Skill derives concrete test cases directly from requirements documents before development begins, exposing ambiguity, incompleteness, and untestable statements early. ## Core Features & Use Cases - Fit Criteria Definition: Converts vague quality requirements into measurable thresholds (e.g., response time <= 3 seconds) so every requirement is objectively verifiable. - Multi-Source Test Derivation: Generates Given/When/Then test cases from use case flows, functional "shall" statements, business rules, state models, and data dictionary constraints, including boundary and exception coverage. - Requirements Gap Detection: Uses the discipline of writing concrete test steps to surface missing or ambiguous requirements, documenting each gap with a suggested resolution. - Use Case: Before handing a specification to developers, a business analyst derives acceptance tests from each use case and requirement, discovering that an expiration-date rule never defines whether same-day assignments are allowed — a gap routed back to the requirements author. ## Quick Start Derive acceptance test cases from my use case document and functional requirements, flagging any requirements that lack measurable fit criteria.
