rite-convergelisted

# /rite-converge: compare live code with intent Read `spec.md`, `plan.md`, and `tasks.md` as the **sole source of intent** (with `.devrites/principles.md` as governing constraints), assess what the **live codebase** implements, and **append every unmet piece as a new traceable `SLICE-###`** at the bottom of `tasks.md` so `/rite-build` can finish it. Use this for a resumed half-built feature, an adopted codebase that drifted from its derived spec, or a build that stalled mid-slice. **Read the active workspace first**; if there's no `spec.md`/`plan.md`/`tasks.md`, tell the user which prerequisite skill to run. > **This is not a diff tool.** `/rite-converge` compares current code with intent. It > does not use git history or compare branches. For a change-scoped > review use `/rite-review`; to prove a finished feature use `/rite-prove`. ## Rules consulted (read on demand from `.claude/skills/devrites-lib/reference/standards/`) Pull on demand: - `principles.md`: the project invariants (`.devrites/principles.md`); code that violates a MUST principle is the highest-severity gap and produces a remediation slice. - `spec-grammar.md`: buildable acceptance criteria vs `## Success metrics` (outcome KPIs the code can't make true and this pass never enqueues); structured `### Requirement:` / `#### Scenario:` blocks, each scenario one behavior to check as built / partial / absent. - `tooling.md`: prefer a code-intelligence index (codebase-memory-mcp → codegraph → graphify, else