rite-temperlisted

# /rite-temper: review scope and risk before planning Review a readied spec for outcome ambition, scope, pre-mortem risks, and unnecessary solution surface. Fold accepted decisions into the canonical contract before `/rite-define`. This step is optional for small work and skips low-stakes specs, but `/rite-autocomplete` always invokes it. **Read the active workspace first**; if there is no readied `spec.md`, tell the user to run `/rite-spec`. ## Rules consulted (read on demand from `.claude/skills/devrites-lib/reference/standards/`) Pull on demand: `patterns.md` + `coding-style.md` (the over-engineering / YAGNI rubric (reuse the pack's standard, don't invent one), `documentation.md` (ADR-style `decisions.md` entries), `afk-hitl.md` (irreversible-risk list + gate ceiling), `elicitation.md` (the move-set to deepen a section that needs more than the default pre-mortem) selected by the section's risk). ## Operating rules - **Raise outcome ambition without expanding the solution unnecessarily.** Solve the underlying problem without adding speculative capability or abstraction. - **Route every scope change through the Spec Drift Guard.** A scope change takes effect only when `spec.md` records the confirmed decision. Expansion is **opt-in** (HITL confirm; AFK pauses: see autocomplete policy). Nothing auto-grows into the build. - **Apply maximum caution to hard-to-reverse changes.** Auth, migration, public API, and data-model changes always pause under the irreversible-ris