check-requirement-coverage

Requirements traceability identifies REQ-* entries in documentation and verifies matching implementations in src/ and tests in tests/ or features/ directories. This Skill scans for these identifiers, assesses coverage, and reports which requirements are missing code or test coverage for remediation.

Requirements coverage ensures every documented requirement has corresponding implementation and test artifacts. Gaps indicate untracked or partially implemented features. This Skill detects those gaps by cross-referencing REQ-* keys across documentation, source code, and test suites to surface missing pieces.

Yes. This Skill applies to documentation-driven projects and scales across multiple lifecycles. It scans REQ-* identifiers in docs, verifies implementations and tests exist, computes coverage metrics, and generates actionable gap reports to track requirements through iterations.

Run a coverage scan to locate all REQ-* keys in documentation, check for corresponding code in src/ and tests in tests/ or features/, compute coverage metrics, and produce a gap report. The report highlights which requirements lack implementation, tests, or both.

Requirements without matching tests are flagged in the gaps report. The Skill identifies unverified requirements so you can add test coverage or update documentation to close the traceability gap.