traceability-check

Verify bidirectional traceability from requirements to code and tests.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/robit-man/transcribe-cli --skill traceability-check-robit-man
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: traceability-check
Source: https://github.com/robit-man/transcribe-cli/tree/main/.claude/skills/traceability-check
Command: npx skills add https://github.com/robit-man/transcribe-cli --skill traceability-check-robit-man

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical challenge of ensuring that all requirements are implemented, tested, and that no code or requirements are left unaccounted for, preventing costly gaps and technical debt.

Core Features & Use Cases

  • Bidirectional Traceability: Maps requirements to code and code to tests.
  • Gap Analysis: Identifies orphan requirements, untested code, and rogue features.
  • Coverage Reporting: Generates detailed reports on traceability status and coverage percentages.
  • Use Case: A project manager can use this skill to verify that all user stories (UC-) and non-functional requirements (NFR-) are linked to specific code modules and have corresponding test cases, ensuring a robust and verifiable development process.

Quick Start

Run the traceability-check skill to verify requirements coverage for the entire project.

Frequently Asked Questions about traceability-check

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

FAQPage Schema
How do I verify bidirectional traceability from requirements to code and tests?

Bidirectional traceability is verified by scanning requirement IDs in documentation, code comments, and test descriptions to build a comprehensive traceability matrix mapping requirements to code and code to tests.

How do I identify orphan requirements and untested code in my SDLC process?

Identify orphan requirements and untested code by running a gap analysis that scans for requirement IDs across the SDLC, detecting unlinked features and rogue code without corresponding test cases or documentation.

What is requirements gap analysis and how does it prevent technical debt?

Requirements gap analysis is the process of detecting unimplemented requirements, untested code, and rogue features to ensure all SDLC elements are accounted for, preventing costly gaps and technical debt.

Can I generate code coverage statistics from requirement IDs in documentation?

Yes, coverage statistics are generated by scanning requirement IDs in documentation and test descriptions, producing detailed reports on traceability status and coverage percentages across the project.

Do I need specific tags or formats for requirement IDs to perform traceability checks?

Traceability checks rely on finding consistent requirement IDs, such as UC-* for user stories or NFR-* for non-functional requirements, embedded within documentation, code comments, and test descriptions.

What is the best way to map user stories to specific code modules and test cases?

The best way to map user stories is to use an automated traceability matrix that scans for requirement IDs across documentation, code, and tests, generating comprehensive coverage reports and identifying missing links.