traceability

Keeping requirements, code, and tests in sync is a manual nightmare that usually fails during the first audit. This skill provides a structured framework to maintain a traceability matrix, ensuring every functional requirement maps directly to specific source files, API endpoints, and test suites. It replaces vague "documentation is up to date" claims with a machine-validated CSV that serves as a single source of truth for developers, testers, and auditors.

What it does

• Requirement mapping links functional and non-functional requirement IDs to specific code components.
• Coverage validation identifies implemented requirements that lack associated tests or design documentation.
• API tracking maps endpoints to gateway routes and technical design sections for contract consistency.
• Decision linking connects architectural decision records (ADRs) to the requirements they fulfill.
• CI integration provides a zero-dependency Python script to break the build when traceability gaps are detected.

How it works

1. Initialize the matrix by creating a standardized CSV structure based on the project's requirements.
2. Update specific columns (components, endpoints, tests) during the development and testing cycles.
3. Verify consistency by running the validation script to check file paths, unique IDs, and document sections.
4. Audit the project using the matrix to provide bi-directional proof of implementation for every requirement.

Frameworks & tools

This skill uses a standardized CSV schema and a standalone Python validation script. It is designed to work within any git repository and integrates into CI/CD pipelines via standard shell execution.

Why this beats prompting it yourself

Generic prompts often fail to maintain the rigid structure required for formal audits or forget to cross-reference file paths against the actual filesystem. This skill enforces a multi-role ownership model and provides a specialized validation script that turns traceability into an automated check rather than a manual guessing game.

Use cases

• Map requirement RF-102 to specific Go handlers, unit tests, and design docs.
• Identify which requirements are missing tests before a production release.
• Audit the relationship between API endpoints and their corresponding gateway routes.
• Link architectural decisions to the specific features they influenced.

Known limitations

Does not perform static code analysis to verify logic; it only validates the existence of paths and structural consistency of the matrix. Requires manual updates of CSV rows during development.