What problem does it solve? Writing acceptance criteria for a change request and writing Cucumber scenarios for the test suite are usually done separately, so the two drift apart and the suite checks different behavior than the CR promised. This Skill enumerates the observable cases a behavior must satisfy once, then renders that single case list as both collapsed-Gherkin acceptance criteria and full Given/When/Then scenarios. ## Core Features & Use Cases - Case enumeration from three sources: Accepts a filed CR or issue, a subject-area topic, or a single feature/use-case doc, and derives a variation matrix covering happy paths and independent failure modes. - Observable-channel grounding: Verifies every case outcome attaches to an observable channel (log line, error message, emitted request, output file) and that inputs actually trigger the behavior, flagging ungroundable cases instead of rendering vacuous tests. - Dual rendering: Produces collapsed acceptance criteria for CRs and full Cucumber scenarios that reuse the existing suite's step vocabulary, with support for pre-code (design-only) and post-code verification. - Use Case: Given a CR describing a new validation in the qubership-envgene pipeline, generate the acceptance criteria for the issue body plus paste-ready .feature scenarios covering each pipeline flow and failure mode. ## Quick Start Ask the assistant to draft Gherkin scenarios and acceptance criteria for a specific feature doc, topic, or change request in the qubership-envgene repository.
