requirement-coverage-checker
Installation
SKILL.md
Requirement Coverage Checker
Every requirement should trace to at least one of: code that implements it, or a test that verifies it. Preferably both. A requirement with neither is either unimplemented or undocumented — both are problems.
Coverage levels
| Level | Evidence | Confidence |
|---|---|---|
| Tested | A test asserts the required behavior | High — behavior is checked |
| Implemented | Code exists that (claims to) satisfy it | Medium — no automated check |
| Documented | A comment/doc references the requirement | Low — intent, not evidence |
| Uncovered | No trace anywhere | Zero — gap |
Step 1 — Decompose requirements into checkable claims
A requirement like "The API MUST validate input and return 400 on invalid data" is two claims:
- Input is validated.
- Invalid input → HTTP 400.