rite-resolvelisted

# /rite-resolve: answer the human gate `/rite-resolve` resumes an **async** human gate: a checkpoint that already paused and **stopped the session** (an AFK blocking/escalating/irreversible queue, or a HITL pause left unanswered), plus `--batch`. When `/rite-build` asks a question **inline** via `AskUserQuestion` and the human is present, that pick resolves the gate **in place** through the same `devrites-engine resolve` writer. You don't type `/rite-resolve` for it. For the async case this skill takes the human's answer (or `--drop` / `--batch`), writes it to `questions.md`, updates `state.md` (clears `Awaiting human`, sets `Status: running`), and recommends the next command. It has one verb, one source of truth (`questions.md`), and one cursor (`state.md`). The full AFK / HITL contract lives in [`afk-hitl.md`](../devrites-lib/reference/standards/afk-hitl.md). ## Rules consulted (read on demand from `.claude/skills/devrites-lib/reference/standards/`) Pull these via `Read` when shaping the resolve: - `afk-hitl.md`: gate taxonomy, `questions.md` schema, AFK exception rules. - `documentation.md`: record decisions and rationale where the answer changes scope. ## Operating rules - **Requires an active workspace.** Read `.devrites/ACTIVE` first; if empty or the slug has no `questions.md`, **STOP** and tell the user to run `/rite-spec <feature>` first. - **One mutation per call.** A single qid (or `--batch` file) per invocation; never silently coalesce multiple human dec