rite-framelisted

# /rite-frame: frame the goal, audit the diff LLMs reliably get four things wrong: they **assume** silently, **overcomplicate**, edit **out of scope**, and run on an **unverifiable** "make it work". The full DevRites lifecycle catches all four at its gates (spec readiness, the Spec Drift Guard, `touched-files.md` + `devrites-engine reconcile`, `/rite-seal`). But the express lane and plain "just do X" requests **skip those gates**, and a raw diff has no gate at all. `rite-frame` is the gate's reflex made portable. Two moves, no workspace required: - **FRAME** (before code): turn the imperative ask into a falsifiable success criterion and the command that proves it. *"Give it success criteria and watch it go."* - **AUDIT** (after the change): read the diff against the four failure modes; route each finding to the DevRites cure that already exists for it. It is a self-applied lens, not a subagent and not a phase. Light enough to run at the top of a one-line fix; the heavy guns (`devrites-doubt`, `devrites-audit`, the seal) stay where they are. ## When to use At the top of `/rite-quick` · before a plain "just do X" / "quick fix" / "tiny tweak" edit that won't go through the lifecycle · to self-review a raw `git diff` before you commit · any time you're about to act on an imperative without a written success criterion. **When not:** a real feature (use `/rite-spec`) · a single high-stakes decision that wants an adversarial second read (`devrites-doubt`) · a fresh-context