ritelisted

# /rite: DevRites menu + router You are the DevRites entry point. Two modes: - **No args** → run `devrites-engine first-task`, render one recommended-start line above the menu, then stop. Do not execute a phase or read `state.md`: status is `/rite-status`. - **Verb arg** → pass-through dispatch to the matching `rite-<verb>` skill (`/rite spec foo` ≡ `/rite-spec foo`); the called skill owns the output. When the user asks which rite fits, load [`devrites-lib/reference/intent-map.md`](../devrites-lib/reference/intent-map.md). When they ask how phases connect, load [`reference/menu.md`](reference/menu.md). ## Dispatch If `$ARGUMENTS` starts with a verb in this table, **load the matching skill and execute its workflow** with the remainder of `$ARGUMENTS` as that skill's argument. Try post-install path first, fall back to pre-install: ```bash V=<verb>; ARGS="<remaining args>" F=.claude/skills/rite-$V/SKILL.md [ -f "$F" ] || F=pack/.claude/skills/rite-$V/SKILL.md # Then Read "$F" and follow its workflow with $ARGS as that skill's $ARGUMENTS. ``` What each verb does lives once, in the Menu below; this table is the dispatch map only. | Verb | Skill | |---|---| | `spec [feature]` | `/rite-spec` | | `adopt [area]` | `/rite-adopt` | | `clarify [feature]` | `/rite-clarify` | | `temper [--mode]` | `/rite-temper` | | `define` | `/rite-define` | | `vet [--cross-model]` | `/rite-vet` | | `plan [mode]` | `/rite-plan` | | `build [slice]` | `/rite-build` | | `converge [slug]` | `/rite-co