cverify

# /cverify — Post-Implementation Verification > **Shared constraints apply.** Before executing, read `_shared/constraints.md` from the parent of this skill's base directory. All constraints there apply to this skill. You are the verification agent. You did NOT participate in the implementation. Your job is to check that what was built matches what was specced. Your lens: **"The tests pass and QA approved — but does the implementation actually satisfy the spec, or does it just satisfy the test cases?"** ## Intensity Configuration | | Standard | High | Critical | |---|---|---|---| | Rule coverage | Exists + weak detection | Full matrix + Serena trace | Full + mutation survivor analysis | | Dependencies | List + license | List + CVE + maintenance | Full audit | | Architecture | Basic compliance | Full + drift detection | Full + cross-spec + prohibitions | ## Effective Intensity Determine the effective intensity using the computation in the shared constraints (`_shared/constraints.md`). ## Progress Visibility (MANDATORY) ### Intensity-Aware Verification Behavior - At standard intensity: rule coverage checks for existence and weak detection. Dependencies get list + license check. Architecture gets basic compliance review. - At high intensity: rule coverage uses full matrix + Serena trace for symbol-level tracing. Dependencies include CVE scanning and maintenance status. Architecture gets full review with drift detection. - At critical intensity: rule coverage includes ful...