waiver-completeness-checklisted

# Waiver Completeness Check ## Purpose Confirm that every waiver claimed in a lifecycle artifact carries all 6 fields required by `agent-behavior.yaml`'s `waivers.required_fields` (`waived_gate_or_requirement_id`, `reason`, `residual_risk`, `owner`, `follow_up_action`, `approval_evidence`), and that no waiver attempts to waive false evidence (`waivers.cannot_waive_false_evidence`). This is a power skill, not a lifecycle phase. It is gate-bound: it runs at every phase Exit Gate where a `waivers` block is present in the artifact, without exception. ## Invocation Context Use this skill when: - an artifact's frontmatter or body contains a `waivers` block - a phase's Exit Gate is about to be evaluated and the artifact claims any waiver, skip, or exception - Review, Test, or Ship encounters a chat-stated waiver that has not yet been written into an artifact's `waivers` block Do not invoke it when no waiver is claimed anywhere in the artifact — an artifact with an empty or absent `waivers` block passes trivially without running the check. ## What To Load **Foundation** (confirm in context; load if not already present): - Root `AGENTS.md` - `workflow/router.md` - `workflow/lifecycle.md` - `workflow/rules.md` **Minimum for invocation**: - This file - `references/output-schema.md` **Before starting work**: - `references/field-checklist.md` — the 6 required fields and what counts as non-empty for each - `workflow/agent-behavior.yaml` — `waivers.required_fields` and `waivers.c