devrites 7.1.1 → 7.1.2

package/pack/generated/devin/skills/rite-autocomplete/reference/loop.md

@@ -1,7 +1,6 @@
 # The autocomplete loop: arm AFK, drive every phase
 
-Autocomplete sequences existing `/rite-*` workflows without pausing between
-routine phases. Acceptance-preserving Reslice authority is
+Autocomplete chains existing `/rite-*` workflows without routine-phase pauses. Acceptance-preserving Reslice authority is
 `.devin/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
 
 <!-- BEGIN RESLICE ROUTE-TO-ACTION -->
@@ -23,7 +22,7 @@ allow_gates: [advisory, validating]
 # notify: "<cmd>"
 ```
 
-Read an existing sentinel first. Preserve it byte-for-byte when valid, except
+Read existing sentinel first. Preserve valid bytes, except
 when this invocation contains `--parallel N`: then write or replace only
 `max_parallel: N` and leave every other key unchanged. Stop if the sentinel is
 malformed. Do not stop because it names `max_slices` / `max_agents` /
@@ -41,10 +40,9 @@ remaining. AFK configuration itself stays unchanged.
 
 ### Admit each unattended cycle
 
-Before every phase, review fan-out, recovery, or writer dispatch: cheapest
+Before each phase, review fan-out, recovery, or writer dispatch: cheapest
 readiness check first; reject overlap. Do not stop on `max_agents`,
-`max_minutes`, or `max_review_queue`. Count every leaf result. A new activation
-gets fresh activation-local counters but retains durable slice/recovery state.
+`max_minutes`, or `max_review_queue`. Count every leaf result. New activations reset activation-local counters, retaining durable slice/recovery state.
 
 [Build return](../../rite-build/reference/output.md#caller-owned-continuation).
 Pass `--parallel N`; ignore leftover cap/headroom, remaining-0,
@@ -57,7 +55,7 @@ without recommendations, and Seal judgment (`slice: seal`) still pause.
 
 ## Phase arc
 
-Workspace files carry state; chat does not. Read and execute each phase skill:
+Workspace files, not chat, carry state. Read/execute each phase skill:
 
 | Step | Phase | Completion / edge |
 | --- | --- | --- |
@@ -73,9 +71,8 @@ Workspace files carry state; chat does not. Read and execute each phase skill:
 | 10 | `/rite-seal` | GO/NO-GO; no Git |
 | 11 | `/rite-ship` | only after GO; `--ship` never authorizes Git; stop at literal-GO/native approval |
 
-Before advancing, check
-[stop-conditions.md](stop-conditions.md). After source edits, discard stale pass
-evidence. Re-read the active workspace before each phase. On a cold resume or
+Check [stop-conditions.md](stop-conditions.md) before advancing. Discard stale
+pass evidence after source edits. Re-read active workspace before each phase. On a cold resume or
 new activation, run `devrites-engine check regression <slug>`: `BLOCKED` names a
 durable fact lost since the last checkpoint — restore or route it through its
 owning phase before continuing; `unproven` does not block. After each phase's
@@ -92,37 +89,35 @@ step 10 does not end the run: leave the sealed workspace unshipped with its
 (`/rite-spec <parent>-<n> "<objective>"` from the parent's `decisions.md` sequence)
 and re-enter step 1. Spend one workspace per opened continuation.
 
-When that workspace already exists because a [lookahead](lookahead.md) session
-planned it, do not specify it again. Wait while `devrites-engine claim check
---workspace <child>` exits 3 (a live lookahead holds it), then set
-`.devrites/ACTIVE` to the child and resume from its cursor at step 1. A
-predecessor replan since its Vet blocks the child's readiness with
-`DRV-GATE-READINESS-STALE`; route that to `/rite-vet` before Build.
-
-Spend accounting is durable in `state.md` cursors, not chat. Before invoking the
-continuation, ensure the current workspace's `sequence_workspaces_remaining` is
-set — absent, write `max_workspaces - 1` and `sequence_position: 1` first — and
-`> 0`. `/rite-spec` seeds the child's sequence cursor at creation per the
+For a child already planned by [lookahead](lookahead.md), do not re-specify.
+Wait while `devrites-engine claim check --workspace <child>` exits 3 (live
+lookahead), then set `.devrites/ACTIVE` to the child and resume its cursor at
+step 1. A predecessor replan since its Vet blocks child readiness with
+`DRV-GATE-READINESS-STALE`; route to `/rite-vet` before Build.
+
+Before invoking a continuation, require durable `state.md`
+`sequence_workspaces_remaining > 0`; if absent, first write
+`max_workspaces - 1` and `sequence_position: 1`. `/rite-spec` seeds the child's sequence cursor at creation per the
 [continuation contract](../../rite-plan/reference/slicing.md#continuation-workspaces);
-after the child's `state.md` exists, verify it — `sequence_parent` = the current
-slug, `sequence_position` = parent position + 1,
+verify the created child's `state.md`: `sequence_parent` = current slug,
+`sequence_position` = parent position + 1,
 `sequence_workspaces_remaining` = parent remaining − 1, and — when the recorded
 entry is the sequence's release milestone — `sequence_role: release` (gates then
-require the union manifest). On resume, a child whose
-fields are missing is re-seeded from its `brief.md` parent/position and the
-parent's counter (same values, never a second charge); a child with no recorded
-parent/position is not a sequence member and the chain stops.
-
-Stop instead when: no recorded next entry; the cap or review-queue bound is
-reached; a human-owned, safety, access, or parked-recovery stop fires; or Seal returns
-`NO-GO`. On stop, report the sequence position, the sealed-but-unshipped workspaces, and
-the single release command (`/rite-autocomplete <release milestone> --ship`, or
+require the union manifest). On resume, re-seed missing child fields from its `brief.md` parent/position and
+parent counter (same values, no second charge). No recorded parent/position
+means no sequence membership: stop the chain.
+
+Stop sequence continuation when: `continue_sequence: false`; no recorded next
+entry (the final milestone); the `max_workspaces` cap is reached; or a genuine
+human-owned, safety, access, or parked-recovery stop fires. `max_review_queue`
+never stops Autocomplete; agent-owned Seal `NO-GO` enters recovery, not a handoff.
+Intermediate sealed milestones continue without `--ship` and without Git mutation. On stop, report sequence position, sealed/unshipped workspaces, and
+one release command (`/rite-autocomplete <release milestone> --ship`, or
 `/rite-ship` for the current sealed workspace when the sequence is complete).
 
 ## Backtrack without handing off
 
-The active Autocomplete root remains caller whenever a later phase exposes an
-agent-owned earlier-phase gap:
+Autocomplete remains caller for agent-owned earlier-phase gaps:
 
 1. Save the originating phase/action unless a valid native return cursor exists.
 2. On cold resume, reconcile the terminal cursor against durable fingerprint
@@ -152,6 +147,8 @@ and park it after three escalations while independent work continues.
 
 ## Continuous caller obligation
 
+Green slice/phase checkpoints consume their recorded `next_action` internally;
+only the caller replies finally at completion or a genuine stop.
 No user-facing reply is permitted while durable state contains agent-owned
 `NEEDS_REPLAN`, an intermediate Plan/Vet action, a distinct retained
 Critical/Important fingerprint below its cap or with an escalation left, runnable
@@ -162,7 +159,6 @@ already names a ranked recommended option. Invoke the next internal repair or
 `state resolve` exits 1 on every call and the loop re-invokes it without end. A narrow reviewer closing one finding and exposing another
 Critical/Important invariant is progress, not exhaustion.
 
-The number of completed repair/Vet cycles is not a stop condition. Context
-pressure, compaction, session duration, and nested completion do not convert an
-internal checkpoint into a handoff. Persist it and resume until the requested
-rest point or a shared human/safety/access/parked-recovery condition.
+The number of completed repair/Vet cycles, context pressure, compaction, session
+duration, and nested completion never turn checkpoints into handoffs. Persist and
+resume to the requested rest point or shared human/safety/access/parked-recovery stop.

package/pack/generated/devin/skills/rite-autocomplete/reference/stop-conditions.md

@@ -1,9 +1,8 @@
 # Stop conditions: when autocomplete pauses
 
-On a real stop, write `state.md` as `awaiting_human` or `blocked`, persist the
-reason, and include one resume command. Agent-owned recovery never ends the run:
-a spent strategy escalates and a fully escalated fingerprint parks while other
-work continues ([retry contract](../../devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve)).
+On real stops, persist `state.md` `awaiting_human` or `blocked`, reason, and one
+resume command. Agent-owned recovery never ends the run: spent strategies
+escalate; fully escalated fingerprints park while other work continues ([retry contract](../../devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve)).
 `--ship` never bypasses a stop.
 
 Authority: `.devin/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
@@ -16,7 +15,7 @@ Authority: `.devin/skills/devrites-lib/reference/standards/acceptance-preserving
 
 ## Always stop
 
-Regardless of flags or AFK ceiling:
+Flags/AFK ceiling never override:
 
 - destructive data migration;
 - auth/authz boundary change;
@@ -24,8 +23,8 @@ Regardless of flags or AFK ceiling:
 - external-service contract change; or
 - filesystem destruction outside the workspace.
 
-Red proof cannot advance. Run bounded Debug Recovery and escalate spent
-strategies; a fully escalated fingerprint parks unless the remaining owner is human.
+Red proof cannot advance. Run bounded Debug Recovery; escalate spent strategies.
+Fully escalated fingerprints park unless remaining owner is human.
 
 ## Not stops: internal technical routing
 
@@ -34,13 +33,12 @@ forward work, persists the return cursor, and invokes Plan repair plus Recovery
 Vet inline. The same applies to nested `STOP`/`Next step` when its decision is
 agent-owned.
 
-Agent-owned backtracking is not a stop condition while the exact causal
-fingerprint has budget. Invoke the earlier phase, affected Vet, remediation, and
-proof; then resume the origin. Three no-progress corrections of that exact
-fingerprint spend only its current strategy: escalate to the next correction
-class inline (shared root cause, diagnostic amplification, boundary redesign)
-with a fresh budget, never asking permission. After three escalations in this
-activation the fingerprint parks; finish all independent work, then stop once.
+Agent-owned backtracking is not a stop condition while its exact causal
+fingerprint has budget: invoke earlier phase, affected Vet, remediation, proof;
+resume origin. Three no-progress corrections spend only that fingerprint's current
+strategy: escalate inline to the next class (shared root cause, diagnostic
+amplification, boundary redesign) with fresh budget, without permission. After
+three escalations per activation it parks; finish independent work, then stop once.
 Preserve reproduction, attempts, and dead ends; never offer `/rite-plan unblock`
 or another routine phase command. A new user-issued `/rite-autocomplete`
 reopens parked fingerprints with fresh escalation; wakes and compaction do not.
@@ -52,11 +50,10 @@ It blocks another execution; retained new Critical/Important evidence still
 enters offline recovery. After affected Vet is READY, pause for fresh action
 authorization and never reuse old GO.
 
-Past evidence being irretrievable is not by itself terminal. If an in-scope
-trusted seam can uniquely discriminate the next failure, run diagnostic-
-amplification Plan repair and narrow Vet inline, then pause for fresh GO before
-one evidence-acquisition attempt. Without a safe seam, escalate to the next
-class or park; only a real human/risk/scope gate stops for a human.
+Past evidence being irretrievable is not by itself terminal. If an in-scope trusted seam
+uniquely discriminates the next failure, run diagnostic-amplification Plan repair
+and narrow Vet inline; pause for fresh GO before one evidence-acquisition attempt.
+Without a safe seam, escalate or park; only a real human/risk/scope gate stops for a human.
 
 <!-- workflow-artifact-adapter: {"module":"devrites-lib/reference/standards/workflow-artifacts.md","entry":"classifier returns owner-busy, exhausted, or existing hard gate","action":"escalate BLOCKED_EXHAUSTED; on WAIT_ACTIVE_OWNER run independent work and recheck; stop on exact BLOCKED_GATE result","return":"unchanged cursor plus fixed route-owned output"} -->
 ## Other stop classes
@@ -76,10 +73,9 @@ class or park; only a real human/risk/scope gate stops for a human.
 - **Clarify:** material `open`/unowned decision coverage or a
   low-confidence high-consequence assumption. Continue the initial interview;
   never arm AFK early.
-- **Seal:** remaining NO-GO after recommended-option questions are closed, with
-  every remaining blocker and fix direction. Never round up to GO. An open
-  recommended-option blocking question is not a Seal stop: resolve it, recover
-  agent-owned findings, then re-enter Seal. A first NO-GO is not a stop either:
+- **Seal:** report remaining NO-GO with every blocker/fix direction; never round
+  up to GO. Resolve recommended-option blocking questions internally; recover
+  agent-owned findings and re-enter Seal. A first NO-GO is not a stop:
   recover every agent-owned blocker (missing or unbound proof, a reviewer gap root
   can close, a finding with a fix direction, a missing `review.md` verdict), then
   re-enter Seal. The unattended `N` to accepting Important risks means repair, not
@@ -97,23 +93,26 @@ class or park; only a real human/risk/scope gate stops for a human.
 - **Resource envelope:** overlapping run or missing AFK after arm still stops.
   Do not stop on `--max-slices`, `max_agents`, `max_minutes`, or `max_review_queue`.
 - **Confidence:** intent still cannot become testable acceptance after interview.
-- **Repeated failure:** not a stop. Escalate; a fully escalated fingerprint parks,
-  and the run stops only once no independent work remains.
-- **Resolver failure:** `devrites-engine state resolve` not found, or nonzero exit.
-  Never hand-edit `questions.md`/`state.md` in its place. Not found stops at once;
-  nonzero allows one identical re-run (the fingerprint is command + exit code +
-  decisive stderr line; an unchanged re-run is not a correction, so no further
-  attempts). Then stop `blocked` with the exact command, exit code, and stderr line,
-  and resume action `/rite-doctor`.
+- **Repeated failure:** not a stop. Escalate; fully escalated fingerprints park.
+  Stop only when no independent work remains.
+- **Resolver failure:** `devrites-engine state resolve` missing or nonzero.
+  Never hand-edit `questions.md`/`state.md` instead. Missing stops immediately;
+  nonzero permits one identical re-run (fingerprint: command + exit code + decisive
+  stderr line; unchanged re-run is no correction, no further attempts). Then stop
+  `blocked`: exact command, exit code, stderr line; resume via `/rite-doctor`.
 
 ## Final GO and durable stop
 
-`--ship`/`--yolo` never authorizes Git. With a flag, complete Ship preflight,
-disclose the exact plan, and stop for literal `GO` plus native approval. Without
-one, stop at Seal GO with `/rite-ship`. Seal GO, AFK, prior approval, and flags
-never satisfy Ship approval.
+With a recorded continuation, no opt-out, and workspace budget, Seal GO stays
+internal: continue without `--ship`, leaving milestones sealed/unshipped. Only the
+final milestone, explicit `continue_sequence: false`, or exhausted sequence cap
+ends green sequence continuation.
 
-A cold-resumable stop records `state.md` status, exact reason, and one resume
-action: the human-owned action, or `/rite-autocomplete` to reopen parked
-fingerprints; the owning question/drift/seal entry explains it. The user-facing line says what stopped
-and, only when applicable, what human action resumes it.
+There, `--ship`/`--yolo` requires [Ship preflight](../../rite-ship/reference/git-ship.md#before-type-go):
+disclose exact plan; stop for fresh literal `GO` plus native approval.
+Without flags, stop at Seal GO with `/rite-ship`. Seal GO never authorizes Git
+or satisfies Ship approval; neither do AFK, prior approval, or flags.
+
+Record cold-resumable `state.md` stops: status, exact reason, one resume action
+(human-owned or `/rite-autocomplete` to reopen parked fingerprints). Explain in
+owning question/drift/seal entry. Tell user what stopped and any required human action.

package/pack/generated/devin/skills/rite-define/SKILL.md

@@ -146,21 +146,18 @@ Pull these via `Read` when shaping the plan:
    cross-slice boundary names producer, consumer, invariant, integration step, and proof.
    Map each applicable topology/data/integration risk to a slice, failure/recovery path,
    and discriminating proof; a risk cannot live only in the architecture narrative.
-4a. **Persist traceability natively.** The drafter proposes and root writes
+4a. **Persist traceability natively.** Drafter proposes; root writes
    `traceability.md` (`AC/REQ ID → slice → proof → evidence ID → files → status`).
-   Re-read spec, tasks, and proof fields: every ID must exist and every mapping
-   preserve meaning, not just labels. Reject orphans, inventions, and false mappings;
-   `/rite-prove` and `/rite-seal` read this file directly. Reference the plan's
-   `Shared contract proof` rows from existing slice/proof mappings; do not create a second
-   traceability system.
-5. **Complexity and deviations gate:** justify anything outside DevRites defaults (new dep,
-   extra abstraction, second design system) in the plan; if you can't justify it, simplify.
-   **Principles conformance:** read `.devrites/principles.md` (if present) and confirm the
-   approach honors every declared invariant. A plan that conflicts with one is not "a deviation
-   to justify away": either reshape the approach to conform, or, when the conflict is genuine and
-   intended, route it through the Spec Drift Guard plus a recorded decision and a scoped principle
-   exception a human approves. Never ready a plan that silently violates an invariant. (Re-scored
-   as a blocking gate at `/rite-vet`; no file → none declared → nothing to check.)
+   Re-read spec/tasks/proof: require real IDs, meaning-preserving mappings, not
+   just labels. Reject orphans/inventions/false mappings. `/rite-prove` and
+   `/rite-seal` read it directly. Reference plan `Shared contract proof` rows from
+   existing slice/proof mappings; never create a second traceability system.
+5. **Complexity and deviations gate:** justify deviations from DevRites defaults
+   (new dep, extra abstraction, second design system) in plan; else simplify.
+   **Principles conformance:** honor all `.devrites/principles.md` invariants
+   (absent → none). Reshape conflicts; intended genuine conflicts need Spec Drift
+   Guard, a recorded decision, and a human-approved scoped principle exception.
+   Never ready silent violations; `/rite-vet` re-scores this blocking gate.
 6. **Write** `architecture.md`, `plan.md`, `tasks.md`, and `traceability.md` — save the
    accepted bundle under `packets/` and apply it with `devrites-engine state
    apply-bundle <slug> <bundle.json>` before root reconciliation edits; update
@@ -168,27 +165,31 @@ Pull these via `Read` when shaping the plan:
    `flows.md` (**Mermaid-first**). If a richer reviewable visual earns it, emit
    `visual/<flow>.html` + `visual/<flow>.outline.md` after loading matching playbooks from
    [`../devrites-lib/reference/visual-playbooks/index.md`](../devrites-lib/reference/visual-playbooks/index.md)
-   (progressive; never preload all seven), link the pair from `flows.md`, treat outline as
-   SSOT (outline wins), and never require Lavish or a new phase.
-6a. **Cross-artifact gate.** Read spec, tasks, and traceability together: every
-   buildable AC/REQ maps to an existing slice/proof, every slice maps to real
-   acceptance, and names/prose agree. Missing, duplicate, contradictory, or
-   meaning-changing mappings block. Then run
+   (progressive; never preload all seven), link both from `flows.md`; outline is
+   SSOT (wins). No Lavish or new phase required.
+6a. **Cross-artifact gate.** Read spec/tasks/traceability together: each buildable
+   AC/REQ maps to existing slice/proof; each slice maps to real acceptance;
+   names/prose agree. Missing, duplicate, contradictory, or meaning-changing
+   mappings block. Run
    `devrites-engine check task-graph <slug> --strict`; a malformed dependency graph, or a
    shared path written by `hubAdvisoryMin`+ slices with no `Serial rationale:`, blocks
-   before Vet rather than spending a reviewer context on invalid tasks. Resolve each
+   before Vet; no reviewer context for invalid tasks. Resolve each
    `ADVISORY size:`/`hub:`/`chain:` line now (split or seam slice, or a rationale);
    `--strict` refuses the contended plan, the default run only advises.
 7. **Readiness gate** (`plan-template.md`): require CLEAR coverage; complete acceptance,
    wiring, shared-contract proof, applicable outputs, and rollback; risk-first acyclic order;
    justified deviations; and every horizon item present, with blockers resolved, planning
    items resolved/validly spiked, and local/action entries bounded and owned.
-   **Stop and confirm** before code. Render the review-before-code
-   digest first: `Intent` (one sentence from the spec), `Done means` (acceptance coverage x/y),
-   `Plan sanity` (slice count + riskiest boundary/gate), `Expected build interruptions`
-   (`none` or only justified action-time gates), and `Build exactly this?` (yes → approve;
-   no → `/rite-plan revise`). When the human confirms the plan, write `Plan approved: <iso>` to
-   `state.md` (see [state-workspace](../rite-spec/reference/state-workspace.md)).
+   **Standalone: stop and confirm** before code. Render digest: `Intent` (one
+   spec sentence), `Done means` (AC coverage x/y), `Plan sanity` (slice count +
+   riskiest boundary/gate), `Expected build interruptions` (`none` or justified
+   action-time gates), `Build exactly this?` (yes → approve; no → `/rite-plan revise`).
+   Human confirmation writes `Plan approved: <iso>` to `state.md`
+   ([state-workspace](../rite-spec/reference/state-workspace.md)).
+   Under active `/rite-autocomplete`, once this readiness gate is green and no
+   unresolved human-owned decision, irreversible-risk, scope, or access gate remains,
+   root writes autonomous approval to existing `Plan approved: <iso>` cursor and records Autocomplete provenance and rationale in `decisions.md`;
+   never claim human approval. Return internally for `/rite-vet`. Plan approval grants no protected-path, Git, or safety authority.
 
 ## tasks.md slice format
 

package/pack/generated/devin/skills/rite-plan/SKILL.md

@@ -171,8 +171,13 @@ Before classifying any Reslice, read `.devin/skills/devrites-lib/reference/stand
    the previous vet verdict: set `Phase: plan`, `Next step: /rite-vet`, and, when
    `eng-review.md` exists, set `Implementation readiness: NEEDS REPLAN`. Never retain READY
    across changed planning inputs. Preserve `Plan approved` only for behavior/acceptance-neutral
-   technical repair; clear it for a contract-changing or newly blocking horizon item and
-   reconfirm only after Clarify and Vet close it. If you stopped for drift,
+   technical repair; clear it for a contract-changing or newly blocking horizon item.
+   Settle human decisions and restore current `CLEAR` coverage through Clarify,
+   then obtain renewed Plan approval BEFORE Vet using only
+   [`rite-define`'s readiness/approval rule](../rite-define/SKILL.md), not its initial
+   decomposition. Under active Autocomplete, retain that rule's explicit autonomous
+   provenance in `decisions.md` — never claim human approval. Approval grants no
+   protected-path, Git, or safety authority. If you stopped for drift,
    mark the `drift.md` entry resolved. Never remove or overwrite a valid caller
    return cursor while writing the Plan checkpoint.
 6. After editing `brief.md`, `spec.md`, `decisions.md`, `assumptions.md`, or `questions.md`,

package/pack/generated/devin/skills/rite-plan/reference/replan-and-repair.md

@@ -19,8 +19,11 @@ First (or fresh) breakdown into vertical slices. Use `task-breakdown.md` +
 
 A slice proved too large (couldn't build+prove in one cycle, or its goal has multiple
 "and"s). Split into thinner end-to-end slices, preserving acceptance coverage: split
-**by the sizing rule, not to a target count**. Update `tasks.md`; renumber; fix
-dependency edges.
+**by the sizing rule, not to a target count**. Update `tasks.md` under the canonical
+[ID contract](../../devrites-lib/reference/workspace-artifact-schema.md#id-contract):
+preserve unaffected IDs; never renumber or fill retired gaps. New meanings get the
+next unused IDs; record relationships in `decisions.md` or `drift.md` before updating
+downstream dependency edges and traceability.
 
 ## repair (after Spec Drift Guard)
 

package/pack/generated/devin/skills/rite-resolve/SKILL.md

@@ -39,9 +39,11 @@ Pull these via `Read` when shaping the resolve:
 - **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).
-- **If the answer materially changes scope, architecture, or acceptance**, route it
-  through the Spec Drift Guard (`/rite-plan repair`) **after** writing the answer: do
-  not modify `spec.md` / `plan.md` inside this skill.
+- **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
@@ -66,8 +68,9 @@ Pull these via `Read` when shaping the resolve:
    - `--batch <plain-text-file>`: bulk resolve, one entry per qid (see
      [`reference/answer-protocol.md`](reference/answer-protocol.md) for the batch
      format).
-2. **Load context.** Read `state.md`, `questions.md`, and the relevant slice from
-   `tasks.md`. Confirm the qid is `status: open`. If `state.md` `Status` is not
+2. **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).
 3. **Apply explicit consent.** Supplying `<qid> "<answer>"`, `--drop`, or `--batch` is the
@@ -86,13 +89,16 @@ Pull these via `Read` when shaping the resolve:
    writer left them.
    **Completion:** zero exit, or the failure reported with no hand edit.
 
-   On resume, and only after a zero exit, also clear or update the unblocked slice's `Slice mode` in `state.md`: if
+   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.
-5. **Post-resolve hand-off.** If the answer changes product behavior or acceptance →
-   recommend `/rite-plan repair`. Otherwise → recommend the slice's natural next action
-   (typically `/rite-build` for the slice that was awaiting).
+5. **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.
 6. **STOP.** User-invoked `/rite-resolve` does not run `/rite-build` itself: the
    user re-enters the workflow explicitly. A controlling `/rite-autocomplete`
@@ -101,6 +107,7 @@ Pull these via `Read` when shaping the resolve:
    already names a ranked recommended option.
 
 > **Mid-flight discipline.** Don't edit `spec.md` / `plan.md` to "incorporate" the
-> answer. That's `/rite-plan repair`. Don't silently retry a build after the answer
+> 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.

package/pack/generated/devin/skills/rite-resolve/reference/answer-protocol.md

@@ -87,12 +87,23 @@ writes one block at a time and pauses. When `/rite-resolve` matches the block's
 
 If `state.md`'s `Status` is `awaiting_human` but no `Awaiting human` block matches the
 qid (drift between the two files), `/rite-resolve` flags the inconsistency and refuses
-to silently fix it. Use `/rite-plan repair` to reconcile.
+to silently fix it. Report it to the current phase owner; once a plan exists,
+reconciliation uses `/rite-plan repair`.
+
+## Phase-aware handoff and slice context
+
+Read `tasks.md` and update `Slice mode` only for an actual `SLICE-###` question,
+never for `slice: spec | plan`; the update is allowed only after the writer exits zero.
+Before planning artifacts exist, recommend the current phase owner's action emitted
+by `state resolve` (for example, `/rite-spec`), not Plan repair. Never create planning
+artifacts as part of Resolve.
 
 If the answer materially changes spec/plan, **do not** edit `spec.md` or `plan.md` inside
-`/rite-resolve`. That's `/rite-plan repair`'s job. The skill's post-resolve hand-off
-recommends `/rite-plan repair` whenever the answer touches acceptance criteria, scope,
-or architecture.
+`/rite-resolve`. Once a plan exists, material acceptance, behavior, scope, or architecture
+changes route through the Spec Drift Guard (`/rite-plan repair`); otherwise retain the
+emitted phase-native next action. User-invoked resolutions use `state resolve --human`;
+an internal Autocomplete caller uses the same writer without `--human` and continues.
+Resolve itself never auto-runs the recommended phase owner.
 
 ## Multi-question awaiting
 
@@ -109,8 +120,9 @@ This shape is reserved: current `/rite-build` writes one question per pause.
 
 The user types the next command explicitly. Reasons:
 
-1. The answer may need a `/rite-plan repair` first; auto-continuing would build against
-   a stale plan.
+1. Before planning artifacts exist, the emitted current phase owner must resume;
+   once a plan exists, material changes may need `/rite-plan repair` first.
+   Auto-continuing a build would skip that owner or use a stale plan.
 2. The user may want to `/rite-status` before resuming.
 3. Atomicity: one verb, one mutation. Chaining is a hidden side-effect that hides bugs.
 

package/pack/generated/devin/skills/rite-review/SKILL.md

@@ -31,7 +31,7 @@ Pull these via `Read` when the diff demands them:
 - [`principles.md`](../devrites-lib/reference/standards/principles.md): declared project invariants (`.devrites/principles.md`); a diff that violates one with no recorded exception is a Critical, blocking finding.
 - [`testing.md`](../devrites-lib/reference/standards/testing.md): confirm that passing tests actually prove the spec.
 - [`agents.md`](../devrites-lib/reference/standards/agents.md): when to fan out to which review subagent.
-- [`security.md`](../devrites-lib/reference/standards/security.md): when input / auth / data / integrations / secrets are in scope.
+- [`security.md`](../devrites-lib/reference/standards/security.md): when the shared [`parallel-dispatch.md`](../devrites-lib/reference/parallel-dispatch.md#roster) roster triggers the security auditor.
 - [`security-checklist.md`](../devrites-lib/reference/standards/security-checklist.md): for the same security-sensitive scope, the compact trust-boundary sweep.
 - [`repository-topology.md`](../devrites-lib/reference/standards/repository-topology.md), [`data-integrity.md`](../devrites-lib/reference/standards/data-integrity.md), [`integration-reliability.md`](../devrites-lib/reference/standards/integration-reliability.md): only
   when the spec applicability map or final diff triggers their ownership/failure/proof checks.
@@ -138,9 +138,9 @@ Pull these via `Read` when the diff demands them:
      [performance-checklist](reference/performance-checklist.md)). No UI/route/style
      paths: record `Not-applicable: no relevant paths in diff`.
 5. **Security:** `devrites-security-auditor`
-   ([security-review](reference/security-review.md)) joins the step-3 cohort when
-   input, auth, data,
-   secrets, or permissions are in the diff; else `Not-applicable: no relevant paths in diff`.
+   ([security-review](reference/security-review.md)) joins the step-3 cohort under the
+   canonical [parallel-dispatch roster trigger](../devrites-lib/reference/parallel-dispatch.md#roster),
+   including a dependency-only diff; else `Not-applicable: no relevant paths in diff`.
 6. **Performance:** `devrites-performance-reviewer`
    ([performance-review](reference/performance-review.md),
    [performance-checklist](reference/performance-checklist.md)) joins the step-3 cohort

package/pack/generated/devin/skills/rite-review/reference/security-review.md

@@ -1,7 +1,9 @@
 # Security review (feature-scoped)
 
-Apply when the feature involves user input, auth/authz, data storage, external
-integrations, secrets, or permissions. Delegates to `devrites-audit security`.
+Use the canonical [parallel-dispatch roster trigger](../../devrites-lib/reference/parallel-dispatch.md#roster),
+including dependency and integration changes. A dependency-only diff still requires
+`devrites-security-auditor`; a docs-only diff with no matching surfaces records
+`Not-applicable: no relevant paths in diff`. Delegates to `devrites-audit security`.
 
 ## OWASP-Top-10-oriented checks