# Verification Checklist

Use this checklist after changing `AGENTS.md` or `agent-docs/`.

- Did you run the strongest repository validation that actually applies?
- If the change touched AGENTS or `agent-docs` structure, did you run `scripts/validate_agent_docs.py --repo-root <repo-root>`?
- If the change touched this skill suite, did you run `scripts/validate_agent_docs.py --skill-suite-root <skills-root>`?
- For docs-only work with no stronger validator, did you at least run `git diff --check`?
- If routing changed, did you re-check root reachability?
- If cross-links changed, did you re-check for stale references or direct cycles where relevant?
- If the validator reported depth or out-degree warnings, did you decide whether the structure is still acceptable or should be refactored?
- If root routing, child references, conflict rules, or required follow-up workflow changed, did you test 1 to 3 representative prompts?
- Did you record each representative prompt with `behavior-check-template.md`?
- Did those representative prompts confirm that the agent read the root entrypoint first, chose the intended specialized workflow, ran required follow-up checks, and surfaced ambiguity instead of guessing?
- Did any representative prompt skip the root entrypoint, miss a required follow-up check, or guess through ambiguity? If so, the behavior check failed.
- Which result level applies: `fully verified`, `structurally verified only`, `behavior check failed`, or `verification incomplete`?
- If findings or residual warnings remain, did you label them with the shared severity model?
- Did the final summary follow the verification shape from `report-format.md`?
- Does the completion claim match the commands actually run?
- If part of the change was not verified, is that limitation stated explicitly?