What problem does it solve? Teams working with OpenSpec Changes need test cases derived strictly from accepted Requirements, Scenarios, and Proposal constraints, plus a clear view of which requirements lack coverage. Manually tracing every Requirement to a test case is error-prone and often produces cases based on assumptions rather than confirmed sources. ## Core Features & Use Cases - Requirement-grounded test case generation: Builds test cases only from accepted Requirements, Scenarios, or explicit Proposal constraints, returning BLOCKER or unknown when sources are missing or contradictory. - Coverage analysis: Lists requirements and scenarios without test cases, cases without sufficient basis, and open questions that make expected results ambiguous. - Read-only OpenSpec integration: Uses standard OpenSpec CLI artifacts and MCP context (get_change_context, artifact paths) without modifying Changes, Master Specs, tasks, or implementation. - Zephyr export support: Produces neutral export records with case_id, steps, expected results, and automation priority when explicitly requested. - Use Case: A QA engineer selects an OpenSpec Change and asks for test cases; the Skill reads the proposal, delta specs, design, and tasks, then returns a Russian-language table with stable IDs, test levels, repository placement, and automation priorities. ## Quick Start Ask the agent to compose test cases and check requirement coverage for a specific OpenSpec Change by providing its change-id.
