What problem does it solve? Requirements, design elements, code, and test cases often live in disconnected documents, making change impact analysis and compliance audits slow and error-prone. This Skill produces a signed, cross-referenced Requirements Traceability Matrix (RTM) that proves coverage in both directions. ## Core Features & Use Cases - Bidirectional Traceability: Maps functional requirements, NFRs, business rules, and use cases forward to design elements, components, and test cases, and backward from tests to requirements. - Horizontal Journey Traceability: Links experience-design journeys and screens to requirements to detect orphan screens and unreachable requirements. - Coverage and Gap Analysis: Computes coverage percentages by priority and category, and lists requirements missing design, tests, or implementation. - Use Case: A project manager preparing for a compliance audit runs this Skill after the functional spec, NFR register, and business rules are signed, producing a signed RTM that shows every requirement's design, test, and verification status. ## Quick Start Ask the agent to run /requirements/traceability to generate the requirements traceability matrix for the current project once the functional spec, nonfunctional spec, and business rules documents are signed.
