What problem does it solve? Teams often lack executable proof that stated requirements actually work at the boundaries users and external systems observe. This Skill builds reproducible acceptance tests that produce durable evidence of requirement compliance without touching production code. ## Core Features & Use Cases - Requirement-to-test mapping: Derives expected behavior from requirements, contracts, and independent oracles rather than from the implementation under test. - Project-native execution: Detects the existing test runner, layout, fixtures, and CI invocation so new tests fit the repository's conventions. - Evidence preservation: Records commands, environments, outputs, and first failures, and reports product defects instead of repairing them. - Use Case: After a feature ticket specifies new API behavior, use this Skill to create acceptance tests against a disposable integration environment, run them, and receive a requirements matrix marking each outcome PASS, FAIL, or UNPROVEN. ## Quick Start Create and run acceptance tests for the requirements in this ticket using the repository's existing test runner, and report the verdict with evidence.