rachidchabane/shallnot
Teaches a coding agent to bind tests to spec requirements with [verifies ID~REV] tags and to pass the shallnot traceability gate before finishing.
Requirement-to-test traceability with the shallnot CLI. Use in any repository that has a shallnot.yaml, whenever you write or change code or tests there, before you report work as done, and whenever a shallnot report, hook or CI check shows findings. The user does not need to mention shallnot. Covers how to bind a test to a requirement with a [verifies ID~REV] tag, how to run the gate, and how to react to each finding.
Write or change requirements in a repository gated by shallnot (it has a shallnot.yaml). Use before implementing any feature, fix or behaviour change that no existing requirement describes, when asked to plan, specify or break down work, and when the meaning of an existing requirement changes. The user does not need to ask for requirements; a request for behaviour is a request to state it first.
Review whether tests really verify their requirements in a repository gated by shallnot (it has a shallnot.yaml). Use when asked to review a change, a branch or a pull request there, when reviewing your own work before reporting it done, and when asked whether a requirement is actually covered. The gate proves a tagged test passed; this review judges whether that test checks what the requirement says.