What problem does it solve? Teams often ship stories without knowing whether every acceptance criterion is actually covered by tests, leaving gaps that surface as production defects. This Skill builds a requirements traceability matrix that maps each acceptance criterion to concrete test cases and exposes uncovered or partially covered requirements. ## Core Features & Use Cases - Requirement Extraction: Pulls testable requirements from acceptance criteria, user stories, tasks, and non-functional requirements. - Coverage Mapping: Documents which unit, integration, and e2e tests validate each requirement using Given-When-Then descriptions, with coverage levels (full, partial, none, integration, unit). - Gap Analysis & Gate Output: Identifies coverage gaps with severity ratings, suggests new tests, and emits a gate YAML block plus a dated traceability report for quality gate decisions. - Use Case: Before closing a login story, run this Skill to confirm AC1 through AC5 each have tests, discover that the password-reset timing requirement has no coverage, and record the gap in the quality gate. ## Quick Start Ask the QA agent to trace the requirements of the current story and generate a traceability matrix with coverage gaps.
