rite-vetlisted

# /rite-vet: review the plan before build Review a defined plan for implementation scope, architecture, code quality, test coverage, performance, failure modes, and parallel work. Cite the source for every finding and design the test coverage that `/rite-build` will use. Fold accepted engineering changes into the canonical plan before code is written. Run this step on **every** plan; depth varies with risk. `/rite-autocomplete` always includes it, and `--cross-model` adds a second opinion from another model. **Read the active workspace first**; if there is no `plan.md`, tell the user to run `/rite-define`. `/rite-temper` reviews product scope and strategy in the spec. `/rite-vet` reviews how to implement that settled scope. ## 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 product ambition.** Treat the scope established by `/rite-temper` as settled. Check whether the plan is simple, well tested, and low risk, and challenge only implementation scope creep. - **The root updates the plan; the reviewer judges.** Vet is the plan-hardening phase, so behavior-preserving plan refinements (test requirement