Can I customize where the skill scans for requirements?

Yes, scanning behavior and directory paths for source, requirements, and tests can be configured via a .aiwg/config/traceability.yaml file.

What is 'rogue code' in the reports?

Rogue code refers to functions or files that have no identified link to an existing requirement, suggesting undocumented features or technical debt that needs review.

Does this skill generate a visual report?

It generates a detailed Markdown-based traceability matrix and an executive summary report including coverage percentages and critical action items.

What requirement formats does this skill support?

It recognizes standard ID patterns including UC-NNN (Use Cases), REQ-NNN (Requirements), NFR-NNN (Non-Functional Requirements), and US-NNN (User Stories).

How does it find links in the code?

The skill scans source files for requirement IDs within comments, JSDoc annotations, function names, and even commit messages.

Traceability Check

Name: Traceability Check
Author: jmagly

byjmagly

•

Security & Testing

Audits and validates the alignment between requirements, source code, and test suites to ensure full project coverage.

About

Traceability Check is a specialized SDLC skill for Claude Code that automates the verification of bidirectional links between documentation and implementation. It scans for requirement IDs (such as UC, REQ, or NFR) across your codebase and tests, identifying implementation gaps, untested features, and 'rogue' code that lacks a formal requirement. This skill is essential for maintaining high-quality software standards, ensuring regulatory compliance, and providing project stakeholders with clear visibility into implementation progress and test readiness.

Key Features

Generates comprehensive traceability matrices and gap analysis reports
Scans source code for requirement references and implementation links
Maps test cases to functional requirements to determine coverage
Identifies orphan requirements and untested code blocks
67 GitHub stars
Extracts requirement IDs from documentation (UC, REQ, NFR, US)

Use Cases

Identifying legacy code or rogue features that lack documentation
Ensuring 100% requirement coverage before a major production release
Automating compliance audits for projects in regulated industries

About

Key Features

Generates comprehensive traceability matrices and gap analysis reports
Scans source code for requirement references and implementation links
Maps test cases to functional requirements to determine coverage
Identifies orphan requirements and untested code blocks
67 GitHub stars
Extracts requirement IDs from documentation (UC, REQ, NFR, US)

Use Cases

Identifying legacy code or rogue features that lack documentation
Ensuring 100% requirement coverage before a major production release
Automating compliance audits for projects in regulated industries