Read-set manifest: devrites-engine context --skills-root .devin/skills <slug> --skill rite-resolve (no workspace: --out <path>) bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
/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 ask_user_question and the human is present, that pick resolves the gate in place through
the devrites-engine state 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.
Rules consulted (read on demand from .devin/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 a selected source workspace. Apply phase target binding; if none, STOP and
tell the user to run
/rite-spec <feature> first. If that source has no questions.md,
report the missing required artifact and stop.
- One mutation per call. A single qid (or
--batch file) per invocation; never
silently coalesce multiple human decisions into one log entry.
- Never overwrite an answered question. If the qid's
status is answered or
dropped, refuse with the existing answer; ask the user to open a new qid that
references the old one (the file is the audit trail).
- Phase-aware handoff after writing the answer: before planning artifacts exist,
recommend the current phase owner's action emitted by
state resolve (for example,
/rite-spec), not Plan repair. Once a plan exists, material scope, architecture,
or acceptance changes route through the Spec Drift Guard (/rite-plan repair).
Never modify spec.md / plan.md inside this skill.
- The script is the source of truth. Always invoke
devrites-engine state resolve. It keeps questions.md + state.md consistent and emits the
next-action recommendation. The one state.md field this skill may write by hand is the
unblocked slice's Slice mode (step 4, the named exception); everything else goes through
the script, never by hand.
- Human gates are for human-only decisions, not the agent's work. A
questions.md entry the
human must answer is a genuine decision (a scope / design / risk call only the human can make),
not a task the agent can do. If a question is really agent-doable ("should I write the
test?", "go implement X"), do not record a human answer that returns the agent's work to it:
flag the mis-tag and route it to the right skill (/rite-build, /rite-plan unblock,
devrites-debug-recovery). The human resolves decisions; the agent does the work.
Workflow
Read .devin/skills/devrites-lib/reference/standards/core.md (operating rules + persistence discipline) before
touching the workspace.
Then read the explicit or active workspace's state.md directly.
Parse arguments. $ARGUMENTS is one of:
<qid> "<answer>": answer the single open question.
--drop <qid> (optional "<reason>"): mark the question dropped; record
the reason inline.
--batch <plain-text-file>: bulk resolve, one entry per qid (see
reference/answer-protocol.md for the batch
format).
Load context. Read state.md and questions.md; require the relevant slice
from tasks.md only for an actual SLICE-### question, not slice: spec | plan.
Confirm the qid is status: open. If state.md Status is not
awaiting_human and the question's gate is blocking, surface the inconsistency
before proceeding (don't auto-repair: flag it).
Apply explicit consent. Supplying <qid> "<answer>", --drop, or --batch is the
user's explicit consent for this local workspace mutation. Echo the qid, answer/drop,
and slice being unblocked, then continue immediately; do not ask the user to confirm the
command they just typed.
Mutate. Run devrites-engine state resolve --human with those arguments (a human is resolving). It:
- flips the qid's
status to answered / dropped and stamps answered_at + answer + answered_by: human;
- if the qid is in
state.md's Awaiting human block (single-question pause), clears
that block and sets Status: running;
- appends a
Log line to state.md.
Writer failure: command not found or nonzero exit → STOP. Do not hand-edit
Slice mode, questions.md, or state.md; report the exact command, its exit code,
and the decisive stderr line, and recommend /rite-doctor. Both files stay as the
writer left them.
Completion: zero exit, or the failure reported with no hand edit.
On resume, only for an actual SLICE-### question and after a zero exit, clear or
update the unblocked slice's Slice mode in state.md: if
the answer lets the slice proceed, drop the pause-time Slice mode so /rite-build
re-derives it on the next selection; if the answer re-shapes how the slice should be
built, set Slice mode to match.
Post-resolve hand-off. Before planning artifacts exist, recommend the emitted
phase-native next action (for example, /rite-spec); do not require or create a plan.
Once a plan exists, material scope, architecture, behavior, or acceptance changes →
recommend /rite-plan repair through the Spec Drift Guard. Otherwise → recommend
the emitted phase-native next action (typically /rite-build for a waiting slice).
Completion: the resolved state contains exactly one next command.
STOP. User-invoked /rite-resolve does not run /rite-build itself: the
user re-enters the workflow explicitly. A controlling /rite-autocomplete
caller invokes the same devrites-engine state resolve writer internally (never with --human) and
continues; it must not emit this skill as a user handoff for a question that
already names a ranked recommended option.
Mid-flight discipline. Don't edit spec.md / plan.md to "incorporate" the
answer. Before planning artifacts exist, return to the emitted current phase owner;
once a plan exists, material changes need /rite-plan repair. Don't silently retry a build after the answer
lands: the user types the next command. Don't merge two open questions into one
answered entry: each question is independently auditable.
1---2name: rite-resolve-73description: User-invoked resume verb for answering, dropping, or batch-resolving open `questions.md` gates.4argument-hint: "<qid> \"<answer>\" | --drop <qid> [\"<reason>\"] | --batch <plain-text-file>"5triggers:6 - user7metadata:8 source: https://skillmd.com/skills/viktorsbaikers/rite-resolve-79---1011<!-- loads: {"always":["devrites-lib/reference/parallel-workspaces.md","devrites-lib/reference/standards/core.md","rite-resolve/reference/answer-protocol.md"],"triggers":{"standards":["devrites-lib/reference/standards/afk-hitl.md","devrites-lib/reference/standards/documentation.md"]},"rootOnly":["devrites-lib/reference/parallel-workspaces.md","devrites-lib/reference/standards/afk-hitl.md"]} -->12> Read-set manifest: `devrites-engine context --skills-root .devin/skills <slug> --skill rite-resolve` (no workspace: `--out <path>`) bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.1314# /rite-resolve: answer the human gate1516`/rite-resolve` resumes an **async** human gate: a checkpoint that already paused and17**stopped the session** (an AFK blocking/escalating/irreversible queue, or a HITL pause18left unanswered), plus `--batch`. When `/rite-build` asks a question **inline**19via `ask_user_question` and the human is present, that pick resolves the gate **in place** through20the `devrites-engine state resolve` writer. You don't type `/rite-resolve` for it. For the async case this21skill takes the human's answer (or `--drop` / `--batch`), writes it to `questions.md`, updates22`state.md` (clears `Awaiting human`, sets `Status: running`), and recommends the next command.2324It has one verb, one source of truth (`questions.md`), and one cursor (`state.md`). The25full AFK / HITL contract lives in26[`afk-hitl.md`](../devrites-lib/reference/standards/afk-hitl.md).2728## Rules consulted (read on demand from `.devin/skills/devrites-lib/reference/standards/`)2930Pull these via `Read` when shaping the resolve:3132- [`afk-hitl.md`](../devrites-lib/reference/standards/afk-hitl.md): gate taxonomy, `questions.md` schema, AFK exception rules.33- [`documentation.md`](../devrites-lib/reference/standards/documentation.md): record decisions and rationale where the answer changes scope.3435## Operating rules3637- **Requires a selected source workspace.** Apply [phase target binding](../devrites-lib/reference/parallel-workspaces.md#phase-target-binding); if none, **STOP** and38 tell the user to run `/rite-spec <feature>` first. If that source has no `questions.md`,39 report the missing required artifact and stop.40- **One mutation per call.** A single qid (or `--batch` file) per invocation; never41 silently coalesce multiple human decisions into one log entry.42- **Never overwrite an answered question.** If the qid's `status` is `answered` or43 `dropped`, refuse with the existing answer; ask the user to open a new qid that44 references the old one (the file is the audit trail).45- **Phase-aware handoff after writing the answer:** before planning artifacts exist,46 recommend the current phase owner's action emitted by `state resolve` (for example,47 `/rite-spec`), not Plan repair. Once a plan exists, material scope, architecture,48 or acceptance changes route through the Spec Drift Guard (`/rite-plan repair`).49 Never modify `spec.md` / `plan.md` inside this skill.50- **The script is the source of truth.** Always invoke51 `devrites-engine state resolve`. It keeps `questions.md` + `state.md` consistent and emits the52 next-action recommendation. The one `state.md` field this skill may write by hand is the53 unblocked slice's `Slice mode` (step 4, the named exception); everything else goes through54 the script, never by hand.55- **Human gates are for human-only decisions, not the agent's work.** A `questions.md` entry the56 human must answer is a genuine decision (a scope / design / risk call only the human can make),57 not a task the agent can do. If a question is really agent-doable ("should I write the58 test?", "go implement X"), do not record a human answer that returns the agent's work to it:59 flag the mis-tag and route it to the right skill (`/rite-build`, `/rite-plan unblock`,60 `devrites-debug-recovery`). The human resolves decisions; the agent does the work.6162## Workflow63640. **Read `.devin/skills/devrites-lib/reference/standards/core.md`** (operating rules + persistence discipline) before65 touching the workspace.66 Then read the explicit or active workspace's `state.md` directly.671. **Parse arguments.** `$ARGUMENTS` is one of:68 - `<qid> "<answer>"`: answer the single open question.69 - `--drop <qid>` (optional `"<reason>"`): mark the question `dropped`; record70 the reason inline.71 - `--batch <plain-text-file>`: bulk resolve, one entry per qid (see72 [`reference/answer-protocol.md`](reference/answer-protocol.md) for the batch73 format).742. **Load context.** Read `state.md` and `questions.md`; require the relevant slice75 from `tasks.md` only for an actual `SLICE-###` question, not `slice: spec | plan`.76 Confirm the qid is `status: open`. If `state.md` `Status` is not77 `awaiting_human` and the question's `gate` is `blocking`, surface the inconsistency78 before proceeding (don't auto-repair: flag it).793. **Apply explicit consent.** Supplying `<qid> "<answer>"`, `--drop`, or `--batch` is the80 user's explicit consent for this local workspace mutation. Echo the qid, answer/drop,81 and slice being unblocked, then continue immediately; do not ask the user to confirm the82 command they just typed.834. **Mutate.** Run `devrites-engine state resolve --human` with those arguments (a human is resolving). It:84 - flips the qid's `status` to `answered` / `dropped` and stamps `answered_at` + `answer` + `answered_by: human`;85 - if the qid is in `state.md`'s `Awaiting human` block (single-question pause), clears86 that block and sets `Status: running`;87 - appends a `Log` line to `state.md`.8889 **Writer failure:** command not found or nonzero exit → STOP. Do not hand-edit90 `Slice mode`, `questions.md`, or `state.md`; report the exact command, its exit code,91 and the decisive stderr line, and recommend `/rite-doctor`. Both files stay as the92 writer left them.93 **Completion:** zero exit, or the failure reported with no hand edit.9495 On resume, only for an actual `SLICE-###` question and after a zero exit, clear or96 update the unblocked slice's `Slice mode` in `state.md`: if97 the answer lets the slice proceed, drop the pause-time `Slice mode` so `/rite-build`98 re-derives it on the next selection; if the answer re-shapes how the slice should be99 built, set `Slice mode` to match.1005. **Post-resolve hand-off.** Before planning artifacts exist, recommend the emitted101 phase-native next action (for example, `/rite-spec`); do not require or create a plan.102 Once a plan exists, material scope, architecture, behavior, or acceptance changes →103 recommend `/rite-plan repair` through the Spec Drift Guard. Otherwise → recommend104 the emitted phase-native next action (typically `/rite-build` for a waiting slice).105 **Completion:** the resolved state contains exactly one next command.1066. **STOP.** User-invoked `/rite-resolve` does not run `/rite-build` itself: the107 user re-enters the workflow explicitly. A controlling `/rite-autocomplete`108 caller invokes the same `devrites-engine state resolve` writer internally (never with `--human`) and109 continues; it must not emit this skill as a user handoff for a question that110 already names a ranked recommended option.111112> **Mid-flight discipline.** Don't edit `spec.md` / `plan.md` to "incorporate" the113> answer. Before planning artifacts exist, return to the emitted current phase owner;114> once a plan exists, material changes need `/rite-plan repair`. Don't silently retry a build after the answer115> lands: the user types the next command. Don't merge two open questions into one116> answered entry: each question is independently auditable.