What problem does it solve? Teams lose track of which design documents, implementation files, and verification artifacts cover each requirement, making change impact analysis and completeness audits manual and error-prone. This Skill resolves requirement-to-artifact traceability directly from explicit ADF-COVERS declarations embedded in source files, without relying on derived graphs or semantic inference. ## Core Features & Use Cases - Coverage queries: List all artifacts covering a requirement (forward lookup) or all requirements covered by an artifact (reverse lookup), with role tags (design / implementation / verification) and no truncation. - Impact analysis: Given a changed requirement or artifact, enumerate re-confirmation candidates via a fixed two-hop artifact-requirement-artifact traversal, with explicit notes that empty results do not prove absence of impact. - Integrity checks: Run seven deterministic checks (malformed declarations, unknown roles, unknown requirement references, invalid catalog entries, missing implementation, missing verification, unavailable evidence) plus a per-requirement verification classification report. - Use Case: Before closing a case, run the check CLI against the repository root to confirm every current requirement line has at least one implementation declaration and that all mandatory verification lines are covered, failing the gate if any check reports findings. ## Quick Start Ask the agent to run the traceability check over the repository, for example: run bun scripts/src/check.ts with --root pointing at the repo root and report any missing implementation or verification coverage for requirement REQ-0050-014.
