verify — the evidence gate before "done"

verify is the post-implementation gate in the rsc-sdd chain. Implementation just finished; nobody is allowed to call it done, fixed, working, or ready to merge until the evidence exists and has been read. This skill produces that evidence: it runs the project's real quality gate, walks every task's done-check and every acceptance criterion from the spec, and records the result. Pass or fail, the verdict is grounded in command output you actually saw — never in a hunch.

The one rule everything else serves: a claim of done is a claim about evidence. No evidence, no claim. A green feeling is not green output.

This is a process skill. It does not own the lint/type/test tooling — the stack skills do (../fastapi/SKILL.md, ../go/SKILL.md, ../nextjs/SKILL.md, ../flutter/SKILL.md, each shipping scripts/verify.sh; data-layer checks come from ../postgresdb/SKILL.md, security from ../secure-coding/SKILL.md). verify orchestrates them and judges the whole against the spec.

Not this phase: still writing tests or production code → ../implement/SKILL.md (TDD lives there); a check is failing and you need to know why → ../debug/SKILL.md (verify reports the failure and hands off, it does not diagnose); reading the diff adversarially for design/correctness smells a test can't catch → ../review/SKILL.md, or ../code-review/SKILL.md when there is no spec/plan chain to key off; nothing to verify against → you're earlier in the chain, go to ../specify/SKILL.md / ../plan/SKILL.md / ../tasks/SKILL.md first.

Model tier — balanced (opt-in routing)

This phase's default model tier is balanced — it runs the checks and interprets failures with judgment. Routing is off unless models.enabled: true in 02-DOCS/wiki/sdd/config.yaml. When on: resolve this phase's tier (models.overrides wins over models.phases), map it to a model via models.tiers, and apply per ../sdd/references/model-routing.md — announce the switch per the accompaniment dial when it differs from the session model, and dispatch any Task/parallel subagents on that model. Routing off or no profile → honor the session model silently. Never fake a switch a tool can't make; skip routing on a one-line change.

Read the room first (accompaniment dial)

Before running anything, read 02-DOCS/wiki/harness/user-profile.md for the technical + accompaniment level; no profile yet → default to non-technical framing. The verdict itself (pass / fail per item) never changes with the dial — only how much you explain around it.