defining-test-scenarios

What problem does it solve?

This Skill converts ambiguous or high-level behavioral specifications into unambiguous, granular test scenarios so downstream test-writing agents can generate executable tests without making behavioral decisions. It bridges the gap between "what the system should do" and a deterministic set of observable acceptance checks.

Core Features & Use Cases

• Spec expansion: Expand a single feature ID from a behavioral spec into a suite of GIVEN / WHEN / THEN scenarios scoped to that feature.
• Constraint enforcement: Enforce strict rules (no code, no architecture assumptions, observable outcomes only) and deterministic entity labeling to ensure scenarios are implementation-agnostic.
• Assumption & cross-feature handling: Flag and encode [ASSUMPTION] behaviors, include cross-feature traceability notes, and produce a Coverage Summary for traceability.
• Use Case: QA Architects preparing acceptance criteria for an autonomous test-writing agent that will generate end-to-end or unit tests from the produced scenarios.

Quick Start

Expand feature F-05 in specs/enrollment.md into a complete specs/enrollment.test.F05.md file containing precise GIVEN / WHEN / THEN scenarios and a Coverage Summary.