ada-traceability-audit

Audits requirements traceability matrices against source code to detect stale statuses and missing entries.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/wubing7755/Ada --skill ada-traceability-audit-wubing7755
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ada-traceability-audit
Source: https://github.com/wubing7755/Ada/tree/main/skills/software-development/ada-traceability-audit
Command: npx skills add https://github.com/wubing7755/Ada --skill ada-traceability-audit-wubing7755

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about ada-traceability-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a requirements traceability matrix against source code?

Extract all REQ IDs from the SRS and traceability matrix, diff both directions to find gaps, then verify each status label by grepping the codebase and checking test files. Treat source code as primary evidence and update documentation where it disagrees.

How to find requirements marked Not Implemented that actually exist in code?

Grep the codebase for the REQ number or feature keywords for every requirement labeled "Not Implemented". If matching implementation or test files exist, the status is stale and should be corrected with the file and line evidence recorded.

When should I use a traceability audit versus an SRS review?

Use a traceability audit when checking the matrix against code: statuses, appendix counts, and missing REQ entries. Use an SRS review for documentation-internal issues like terminology consistency, which this audit explicitly excludes from its scope.

Why do traceability appendix line counts become stale?

Appendix file lists and line counts are often copied from older coverage snapshots and never regenerated after refactoring or new phases. Recount every file with tools like find and wc, and flag entries showing placeholder dashes instead of real numbers.

What are the limitations of a traceability matrix audit?

It requires an existing traceability matrix and SRS; it is not suited for single-requirement spot-checks or codebases without secondary documentation. It also stops when a status depends on ambiguous product intent rather than observable implementation evidence.