What problem does it solve? Teams often lack visibility into which requirements are actually covered by tests and whether a release is safe to ship. This Skill builds a requirements-to-tests traceability matrix, classifies coverage per criterion, identifies gaps, and produces a deterministic quality gate decision (PASS / CONCERNS / FAIL / WAIVED). ## Core Features & Use Cases - Traceability Matrix Generation: Maps acceptance criteria, OpenAPI endpoints, or inferred user journeys to discovered tests across E2E, API, component, unit, and live verification levels, with FULL / PARTIAL / NONE / UNIT-ONLY / INTEGRATION-ONLY coverage statuses. - Gap Analysis & Risk Prioritization: Flags uncovered P0-P3 criteria, endpoint gaps, missing auth negative-path tests, and happy-path-only coverage, with concrete test recommendations. - Quality Gate Decision: Applies deterministic rules over test results, coverage, NFR evidence, and waiver registers to emit gate-decision.json and e2e-trace-summary.json for CI/CD enforcement. - Use Case: Before merging a story, ask the agent to analyze test coverage; it discovers tests, maps them to acceptance criteria, reports that a P0 criterion has only unit coverage, and blocks the release with a FAIL gate decision. ## Quick Start Ask the agent to create a traceability matrix and analyze test coverage for the current story or release.