What problem does it solve? Requirements traceability matrices drift out of sync with actual code: statuses say "Not Implemented" when features exist, appendix file lists and line counts go stale, and REQ entries go missing after SRS updates. This Skill systematically reconciles the matrix against source and test files so documentation reflects reality. ## Core Features & Use Cases - REQ ID Reconciliation: Extracts requirement IDs from the SRS and traceability matrix and diffs both directions to find missing or orphaned entries. - Status Verification: Checks each "Not Implemented", "Implemented", "Tested", or "Partial" label against actual source files and test results, treating code as primary evidence. - Appendix and Statistics Audit: Recomputes file lists, line counts, test method counts, and summary statistics, and checks cross-document consistency across README, SRS, and design docs. - Use Case: After a major development phase, run the audit to discover that a requirement marked "Not Implemented" is fully implemented in a component file, then correct the matrix and recalculate all summary counts. ## Quick Start Ask the agent to audit the requirements traceability matrix against the source code and tests, reporting stale statuses, missing REQ entries, and outdated appendix counts with evidence for each correction.