What problem does it solve? Requirements, stories, tasks, and test cases live in separate documents, so it is easy for a requirement to be silently dropped, for work to appear without a source requirement, or for NFRs to ship untested. This Skill builds a Requirements Traceability Matrix (RTM) that exposes those gaps before a sprint closes or documents are handed over. ## Core Features & Use Cases - Bidirectional traceability: Collects BR, FR, NFR, EP, US, AC, TSK, TC, and BUG IDs across the docs vault and maps each requirement forward to story, task, and test case, and each work item backward to its source requirement. - Mandatory gap analysis: Reports six fixed findings every run — requirements without stories, requirements without test cases, scope-creep stories, unenforced business rules, orphaned or mistyped IDs, and numeric coverage percentages per layer. - Honest-linking rules: Never guesses associations; undocumented links are reported as gaps rather than inferred, and source documents are never edited to make the matrix look complete. - Use Case: Before closing a sprint, ask for an RTM of the coffee-store pre-order project; the Skill scans the spec, backlog, task, and test-plan folders and produces a matrix showing that FR-005 has no task or test and that NFR coverage is only 43%. ## Quick Start Build a traceability matrix for the requirements in docs/01-requirements and tell me which requirements have no story or test case.
