Use when auditing the link between requirements and tests, before changing or deleting a requirement, when deciding whether a test is allowed to exist, or when asked "what verifies X" / "why does this test exist". Convention-based; the audit script is Babashka, ad-hoc searches use ripgrep.
84%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
The invariant: every requirement is verified by at least one test, and every test is justified by at least one requirement. Both directions, always. This is what lets a future session change a requirement and know exactly what else must change — instead of archaeology.
specs/REQ-<AREA>-<NNN>.md (its home).// REQ-SALE-003 (multiple IDs comma-separated on one line if one test
genuinely verifies several requirements — rare; prefer one).Run scripts/trace-audit.bb (copy it to scripts/ in the project).
It checks both directions:
specs/REQ-*.md whose ID appears in no test.
→ Incomplete work. Either write the test (verification-ratchet) or, if the
requirement is dead, mark it superseded — never silently delete.// REQ- comment whose ID has no spec file, or a test
function with no REQ comment at all.
→ The test is pinning behavior nobody asked for. Either write the missing
requirement (spec-authoring) or report the test to the human as a deletion
candidate. Do not delete it yourself — deletion weakens checks (CLAUDE.md).Run the audit: before declaring any feature done, after any change to specs/,
and when starting work in an unfamiliar area of the repo.
rg -n 'REQ-SALE-003' specs/ src/ tests/ — full blast radius first.Three field-proven conventions, all naming-based rather than annotation-based:
search: grep tree content (git_search_files). Every commit maps back
to the reference function it ports — commit ↔ spec-source, greppable
from either end.Path: code → test that forces it (delete-and-see or cargo-mutants tells you) → REQ comment on the test → spec file → ADR links in the spec. If the chain breaks anywhere, you have found either dead code or an orphan — report it.
igouss/gitweb-rs
9ef2429
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.