rite-vetlisted

# /rite-vet: review the plan before build Vet every plan before code for scope, architecture, quality, proof, performance, failure modes, and parallel safety. Cite findings, fold accepted technical hardening into the plan, and design Build tests. Risk sets depth; `/rite-autocomplete` has Vet and `--cross-model` adds one opinion. Missing `plan.md` routes to `/rite-define`. `/rite-temper` owns product scope/strategy; Vet owns implementation. Quick/Standard/Full comes from [`orchestration-profiles.md`](../devrites-lib/reference/orchestration-profiles.md), but every profile keeps the exact plan-reviewer gate. ## Rules consulted (read on demand from `.claude/skills/devrites-lib/reference/standards/`) Pull the standard named by the active axis: `principles.md`, `patterns.md`, `coding-style.md`, `testing.md`, `spec-grammar.md`, `performance.md`, `error-handling.md`, `development-workflow.md`, `afk-hitl.md`, `developer-experience.md`, `elicitation.md`, and `definition-of-done.md`. ## Operating rules - **Review implementation, not ambition.** Temper's product scope is settled; challenge only implementation creep, complexity, proof, and risk. - **Root hardens; reviewers judge.** Root alone asks, decides, folds back, writes, and sets readiness. Write behavior-preserving test, boundary, ordering, error, and failure-mode refinements into `plan.md`/`tasks.md`/`test-plan.md`. Acceptance/product changes require the Spec Drift Guard: `drift.md`, recorded decision, then `/rite-pla