Read-set manifest: devrites-engine context --skills-root .pi/skills <slug> --phase quick bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
/rite-quick: express lane for small changes
The full DevRites lifecycle is right for real features; it is ceremony for a typo, a
copy tweak, a one-function fix, or a small config change. /rite-quick keeps the
discipline that matters (idiom, TDD, evidence, escape-to-full-lifecycle) and drops the
artifacts that don't, in a single pass. Senior-engineer "right step, right time" made
executable, not advisory. This lane uses the Quick depth profile from
devrites-lib/reference/orchestration-profiles.md.
The significance gate (the whole safety story)
Run this first. If ANY of these holds, STOP and route to /rite-spec. Do NOT use the
express lane:
- Touches auth / authz, a data migration, a public API contract, or any
destructive / data-loss path in the irreversible-risk list. See
../devrites-lib/reference/standards/afk-hitl.md.
- Spans more than one vertical slice, or more than a couple of files of real logic.
- Ambiguous scope: you'd have to guess what "done" means, or the ask hides a design
decision (data model, new dependency, second design system).
- Security-sensitive input handling, or a measurable performance-critical path.
- Would break a declared project principle (
.devrites/principles.md) with no recorded,
human-approved exception: the express lane never relaxes a project gate; a needed exception is
a deliberate human decision, so route it to /rite-spec.
If none hold, the change is small + reversible + unambiguous → proceed. When in doubt,
escalate: the cost of the full lifecycle on a small change is minutes; the cost of the
express lane on a risky one is the failure mode the lifecycle exists to prevent.
Rules consulted (read on demand from .pi/skills/devrites-lib/reference/standards/)
Load this lane's conditional standards when needed:
coding-style.md: naming, guard clauses, reuse-first.
testing.md: TDD, completeness (every touched behavior/element asserted) +
assertion strength (no tautological tests; see it fail first), scaled to the change.
error-handling.md / security.md: only if the change touches input/errors.
principles.md: when .devrites/principles.md exists; a change that breaks an invariant is a gate, not a quick fix.
definition-of-done.md: standing Done bar: acceptance mapped, fresh proof, no open hard gates, scoped edits, rollback/docs where needed.
Workflow
- Orient. Read
core.md. If a .devrites/ workspace is active, read its
state.md directly; /rite-quick does not require
a workspace and does not create the full tree.
- Significance gate (above). Fail → STOP, tell the user to run
/rite-spec <feature>.
If the only failing item is size (more than one slice) and no risk item holds, name
/rite-fast <task> as the lighter option.
- One-line contract. Restate in 1-3 lines: the change, its acceptance (how you'll
know it works), and the scope boundary (what you will NOT touch). This is the entire
"spec + plan" for a quick change: keep it in the chat; optionally drop a
brief.md +
evidence.md under an unused .devrites/work/<slug>/ (no state.md; not a workspace
cursor) if the user wants a record. This is the
/rite-frame FRAME move: if the acceptance won't reduce to a check that could be false,
the ask is ambiguous → escalate per the significance gate. Its AUDIT pass is the diff
self-review in step 5.
- Build with TDD. Failing test first when behavior changes (see it fail for the right
reason) → smallest complete change in the project's idiom (reuse before you write,
anti-AI-slop) → cover every touched behavior / interactive element with a real
assertion. UI → check the states + a browser glance. The root never edits source/tests:
dispatch exact
devrites-slice-wright with an exact-path contract per
wright-dispatch.md § Standalone correction and the
source-writing boundary;
reject any returned path outside it.
- Prove (scoped). Run the targeted tests + typecheck / lint for what changed (not
the whole suite) → green. Record the command + output — resolve the project's real
typecheck/lint commands with
devrites-engine detect commands rather than guessing.
Engine missing or erroring, or zero detected commands for the changed surface:
stop with unproven: <what could not run>, never green and never a guessed command.
A tautological test that can't
fail is not proof.
- Review-lite + ship. Self-review the diff for correctness, scope, and idiom. If
.devrites/principles.md exists, confirm that no declared invariant is broken. This is
/rite-frame's AUDIT pass: one pass, no subagent fan-out. Show the diff. A change that belongs to the
active feature's candidate is not committed here: append its exact paths to
touched-files.md, then route to /rite-prove →
/rite-review → /rite-seal (/rite-ship needs Seal GO). Otherwise, on the
user's confirm, commit it standalone (Conventional Commits, atomic). Never push without the user asking.
Escalation (mid-flight): the Spec Drift Guard still applies
If the "small" change turns out to be not small: a second slice appears, a real design
decision surfaces, scope grows past the boundary, or you hit an irreversible-risk item:
STOP, say so, and route to /rite-spec / /rite-define. Don't quietly grow a quick
fix into an unreviewed feature; that's the exact drift the lifecycle guards against.
If the quick boundary does not hold or an escalation remains, use Stopped / blocked
and route to the full lifecycle; do not render Done.
DO NOT use this lane to dodge the gate: the express lane is for changes that are
genuinely small, not for shipping risky work faster.
1---2name: rite-quick-53description: "Express lane for a small reversible change: typo/copy/config, rate-limit constant, error message, local variable rename, feature flag, README link, one-file/function fix."4argument-hint: "<what to change>"5user-invocable: true6metadata:7 source: https://skillmd.com/skills/viktorsbaikers/rite-quick-58---910<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/definition-of-done.md","devrites-lib/reference/orchestration-profiles.md"],"triggers":{"coding":["devrites-lib/reference/standards/coding-style.md"],"testing":["devrites-lib/reference/standards/testing.md"],"errors":["devrites-lib/reference/standards/error-handling.md"],"security":["devrites-lib/reference/standards/security.md"],"principles":["devrites-lib/reference/standards/principles.md"],"afk":["devrites-lib/reference/standards/afk-hitl.md"]},"workspace":["state.md"],"rootOnly":["devrites-lib/reference/orchestration-profiles.md","devrites-lib/reference/standards/afk-hitl.md"]} -->11> Read-set manifest: `devrites-engine context --skills-root .pi/skills <slug> --phase quick` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.121314# /rite-quick: express lane for small changes1516The full DevRites lifecycle is right for real features; it is **ceremony** for a typo, a17copy tweak, a one-function fix, or a small config change. `/rite-quick` keeps the18discipline that matters (idiom, TDD, evidence, escape-to-full-lifecycle) and drops the19artifacts that don't, in a **single pass**. Senior-engineer "right step, right time" made20executable, not advisory. This lane uses the **Quick** depth profile from21[`devrites-lib/reference/orchestration-profiles.md`](../devrites-lib/reference/orchestration-profiles.md).2223## The significance gate (the whole safety story)2425**Run this first. If ANY of these holds, STOP and route to `/rite-spec`. Do NOT use the26express lane:**27- Touches **auth / authz**, a **data migration**, a **public API contract**, or any28 **destructive / data-loss** path in the irreversible-risk list. See `../devrites-lib/reference/standards/afk-hitl.md`.29- Spans **more than one vertical slice**, or more than a couple of files of real logic.30- **Ambiguous scope:** you'd have to guess what "done" means, or the ask hides a design31 decision (data model, new dependency, second design system).32- Security-sensitive input handling, or a measurable performance-critical path.33- Would **break a declared project principle** (`.devrites/principles.md`) with no recorded,34 human-approved exception: the express lane never relaxes a project gate; a needed exception is35 a deliberate human decision, so route it to `/rite-spec`.3637If none hold, the change is small + reversible + unambiguous → proceed. **When in doubt,38escalate**: the cost of the full lifecycle on a small change is minutes; the cost of the39express lane on a risky one is the failure mode the lifecycle exists to prevent.4041## Rules consulted (read on demand from `.pi/skills/devrites-lib/reference/standards/`)42Load this lane's conditional standards when needed:43- [`coding-style.md`](../devrites-lib/reference/standards/coding-style.md): naming, guard clauses, reuse-first.44- [`testing.md`](../devrites-lib/reference/standards/testing.md): TDD, **completeness** (every touched behavior/element asserted) +45 **assertion strength** (no tautological tests; see it fail first), scaled to the change.46- [`error-handling.md`](../devrites-lib/reference/standards/error-handling.md) / [`security.md`](../devrites-lib/reference/standards/security.md): only if the change touches input/errors.47- [`principles.md`](../devrites-lib/reference/standards/principles.md): when `.devrites/principles.md` exists; a change that breaks an invariant is a gate, not a quick fix.48- [`definition-of-done.md`](../devrites-lib/reference/standards/definition-of-done.md): standing Done bar: acceptance mapped, fresh proof, no open hard gates, scoped edits, rollback/docs where needed.495051## Workflow520. **Orient.** Read [`core.md`](../devrites-lib/reference/standards/core.md). If a `.devrites/` workspace is active, read its53 `state.md` directly; `/rite-quick` does **not** require54 a workspace and does **not** create the full tree.551. **Significance gate** (above). Fail → STOP, tell the user to run `/rite-spec <feature>`.56 If the only failing item is size (more than one slice) and no risk item holds, name57 `/rite-fast <task>` as the lighter option.582. **One-line contract.** Restate in 1-3 lines: the change, its **acceptance** (how you'll59 know it works), and the **scope boundary** (what you will NOT touch). This is the entire60 "spec + plan" for a quick change: keep it in the chat; optionally drop a `brief.md` +61 `evidence.md` under an unused `.devrites/work/<slug>/` (no `state.md`; not a workspace62 cursor) if the user wants a record. This is the63 `/rite-frame` FRAME move: if the acceptance won't reduce to a check that could be *false*,64 the ask is ambiguous → escalate per the significance gate. Its AUDIT pass is the diff65 self-review in step 5.663. **Build with TDD.** Failing test first when behavior changes (see it fail for the right67 reason) → smallest complete change in the **project's idiom** (reuse before you write,68 anti-AI-slop) → cover every touched behavior / interactive element with a **real**69 assertion. UI → check the states + a browser glance. The root never edits source/tests:70 dispatch exact `devrites-slice-wright` with an exact-path contract per71 [wright-dispatch.md § Standalone correction](../rite-build/reference/wright-dispatch.md#standalone-correction) and the72 [source-writing boundary](../devrites-lib/reference/standards/agents.md#source-writing-boundary);73 reject any returned path outside it.744. **Prove (scoped).** Run the **targeted** tests + typecheck / lint for what changed (not75 the whole suite) → green. Record the command + output — resolve the project's real76 typecheck/lint commands with `devrites-engine detect commands` rather than guessing.77 Engine missing or erroring, or zero detected commands for the changed surface:78 stop with `unproven: <what could not run>`, never green and never a guessed command.79 A tautological test that can't80 fail is not proof.815. **Review-lite + ship.** Self-review the diff for correctness, scope, and idiom. If82 `.devrites/principles.md` exists, confirm that no declared invariant is broken. This is83 `/rite-frame`'s AUDIT pass: one pass, no subagent fan-out. Show the diff. A change that belongs to the84 active feature's candidate is not committed here: append its exact paths to85 `touched-files.md`, then route to `/rite-prove` →86 `/rite-review` → `/rite-seal` (`/rite-ship` needs Seal GO). Otherwise, on the87 user's confirm, commit it standalone (Conventional Commits, atomic). **Never push without the user asking.**8889## Escalation (mid-flight): the Spec Drift Guard still applies90If the "small" change turns out to be not small: a second slice appears, a real design91decision surfaces, scope grows past the boundary, or you hit an irreversible-risk item:92**STOP, say so, and route to `/rite-spec` / `/rite-define`**. Don't quietly grow a quick93fix into an unreviewed feature; that's the exact drift the lifecycle guards against.9495If the quick boundary does not hold or an escalation remains, use `Stopped / blocked`96and route to the full lifecycle; do not render `Done`.9798**DO NOT** use this lane to dodge the gate: the express lane is for changes that are99genuinely small, not for shipping risky work faster.