reality-check

# Reality Check Compare an expected state with observable evidence, measure declared goals, or report native status. Select the requested question; a snapshot needs no invented completion claim. Return facts and gaps without selecting work. ## Claim comparison 1. Read the exact claim and its source. For a completion claim, enumerate every stated goal, including work that was never started. Give each a disposition: confirmed with evidence, concrete gap or unverifiable. 2. Inspect relevant files, command outcomes and artifacts. Separate confirmed behavior, concrete gaps, incomplete evidence and changed assumptions. Name the missing evidence instead of resolving an untestable claim by assertion. 3. Compare proposed scope with the original goal when asked about a plan. Report additions that lack authority as scope escalation; the report cannot approve them. Repeated measurements use the same question and criteria; a changed question starts a different comparison. 4. Return the cited findings with checked and not-checked scope. Keep native tracker, Git, runtime, deterministic checks and semantic judgments distinct. A quick answer can be inline. A selected durable gap report retains `reality-check-report.v1`: write `reality-check-report.json` under the caller's chosen destination, default `.agents/scratch/reality-check/<run-id>/`, and run `skills/reality-check/scripts/validate-output.sh <report.json>`. Include the checked claim, evidence-backed finding k...