devrites 5.10.2 → 5.11.0

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

@@ -0,0 +1,185 @@
+---
+name: rite-plan
+description: "Re-plan existing work when reality invalidates the plan: reslice a slice that is too big, repair drift, reorder dependencies, split boundaries, or unblock work. Not first-pass decomposition."
+argument-hint: "[mode: decompose|reslice|repair|reorder|split|unblock|course-correct|revise]"
+---
+
+# /rite-plan: (re)plan an active feature
+
+Update a plan invalidated by evidence, drift, or user decision. **Read the active workspace
+first.** Missing `.devrites/ACTIVE`/workspace stops to `/rite-spec <feature>`. **Revise is
+artifact-only**: reconcile
+`spec.md` / `architecture.md` / `plan.md` / `tasks.md` / `traceability.md` without
+editing source code.
+
+## Rules consulted (read on demand from `.devin/skills/devrites-lib/reference/standards/`)
+Pull [`development-workflow.md`](../devrites-lib/reference/standards/development-workflow.md) via `Read` when reshaping slice cadence or DoD
+criteria.
+Load [`repository-topology.md`](../devrites-lib/reference/standards/repository-topology.md), [`data-integrity.md`](../devrites-lib/reference/standards/data-integrity.md), or [`integration-reliability.md`](../devrites-lib/reference/standards/integration-reliability.md)
+when the spec applicability map or observed drift triggers them.
+Before classifying any Reslice, read `.devin/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
+
+<!-- BEGIN RESLICE ROUTE-TO-ACTION -->
+- `FOLD` → reconcile `architecture.md`, `plan.md`, `tasks.md`, and `traceability.md` atomically; invalidate Vet/readiness; Vet.
+- `GUARD_AND_REPAIR` → no planning writes; Spec Drift Guard → Clarify → Plan repair → Vet.
+- `BLOCKED_INPUT` → no planning writes; exact diagnostic; recover input; reclassify.
+<!-- END RESLICE ROUTE-TO-ACTION -->
+
+## Operating rules
+- Update the spec when needed, but never plan around a known-wrong assumption.
+- Keep each slice small enough for one focused build → prove cycle.
+- **Derive slice count:** reslice when work cannot build+prove in one cycle, not to hit a
+  requested tally. Treat counts as hints and explain honest differences; see
+  [`slicing.md`](reference/slicing.md).
+- **Size by complexity, order by dependency.** A slice carries a `Complexity: N/5` score (from
+  `/rite-define`); a slice scoring **>3** is a reslice trigger unless its inline reason justifies
+  the irreducible complexity. Honor each slice's `depends_on:`: the next *buildable* slice is the
+  lowest pending one whose dependencies are all built. This preserves one-slice-at-a-time execution.
+- **Root writes; drafter proposes.** Follow
+  [`agents.md`](../devrites-lib/reference/standards/agents.md). The controlling chat owns
+  human questions, decisions, reconciliation, and planning writes.
+- **Nested repair preserves its caller.** When `state.md` contains a valid
+  technical-backtracking return cursor, preserve any valid return cursor
+  byte-for-byte. `/rite-vet` is the next internal prerequisite, not a command to
+  hand back to the human.
+
+## Workflow
+0. Read `.devin/skills/devrites-lib/reference/standards/core.md` (operating rules) before reshaping anything.
+   Then resolve the explicit or active slug, require its `state.md`, and read
+   the cursor directly.
+1. Read `spec.md`, `decision-coverage.md`, `plan.md`, `tasks.md`, `state.md`, `drift.md`,
+   `eng-review.md`, and the current `git diff` (if a repo). Read `decisions.md` and
+   `assumptions.md`. Require `Decision coverage: CLEAR`; otherwise STOP → `/rite-clarify`.
+   Apply `.devin/skills/devrites-lib/reference/standards/tooling.md`: use the
+   primary available structural index, and cross-check only for a named unresolved
+   predicate rather than reassurance. For an external
+   dependency's current API surface, consult context7 if available.
+2. **Pick the mode** (`$ARGUMENTS` or infer): Apply the marked action before writes and
+   retain its decision/coverage evidence.
+   - **decompose:** first/again break the feature into vertical slices.
+   - **reslice:** a slice is too large; split into thinner end-to-end slices.
+   - **repair:** a Spec Drift Guard event; fold the resolution into plan + tasks.
+   - **reorder:** fix the dependency order.
+   - **split:** separate backend/frontend contracts (see `devrites-api-interface`).
+   - **unblock:** a verification failed; re-route around the blocker.
+   - **course-correct:** mid-build user pivot; apply the marked action, choose
+     rollback/forward-fix, and update permitted artifacts atomically (`MVP cut` is the named retreat).
+   - **revise:** reconcile a requested artifact revision; propose/confirm its file set and
+     **never edit source**. Only explicit `/rite-upgrade` with a `repairable` assessment naming
+     rule, evidence, gate, paths, and delta can authorize its neutral workspace edit—not source/history.
+     **Revise or new?** Same intent? >50% scope survives? Original not completable without it?
+     Two “no” answers mean new work: seal/ship current scope (`MVP cut` if named), then
+     `/rite-spec`, and stop.
+   See [replan-and-repair](reference/replan-and-repair.md) for each mode's steps.
+2a. **Draft fresh.** Dispatch `devrites-plan-drafter` in `repair` mode with frozen mode,
+   affected artifacts, settled contract, and failure/drift. Await one atomic, read-only
+   the drafter's `candidate_files` bundle; human choices return separately.
+   When the observed failure is missing or ambiguous consumptive-action evidence,
+   require the drafter to apply [`one-shot-actions.md`](../devrites-lib/reference/standards/one-shot-actions.md) and return the bounded
+   diagnostic-amplification design, injective boundary map, per-seam fixtures, and
+   collision mutant. Past evidence loss is not terminal. The drafter supplies no bodies.
+   A repair candidate carries a delta self-check scoped to what the patch
+   touches: which intersected invariants it re-verified, with evidence of no
+   correction-created regression. Global re-derivation (ID/edge/HZN counts,
+   acyclicity) runs on materialized artifacts at the step-7 gate — the drafter
+   never re-derives them by exhaustive search. It also carries a bounded
+   self-attack over the delta (`self_attack_exposures`), catching the shallow
+   next-round findings before Vet's dispatch rather than after a full loop.
+   Root dispositions every exposure — fold as a finding, accept as a declared
+   residual, or reject with reason; none silently drops.
+   Packet mechanics: dedupe at assembly — findings with an identical
+   required-fix and site set merge into one entry that closes all their
+   fingerprints. The packet may carry digest-pinned site excerpts so the
+   drafter spot-verifies anchors instead of re-scanning whole files, and root
+   may partition findings into anchor-disjoint clusters with one drafter per
+   cluster in parallel — findings sharing any anchor or mirrored clause stay
+   in one cluster, and each bundle applies independently. A `partial`-
+   continuation re-dispatch continues the same packet; it does not advance the
+   same-seam counter. Count consecutive repair packets whose findings' cited clause sets overlap
+   the immediately previous packet's — the overlap is the seam. Carry it as an explicit
+   integer `same_seam_count` in every packet (previous value + 1 when the seam repeats,
+   else 1) so the threshold is counted rather than judged; a packet that reports the same
+   seam without the counter is malformed. At the third
+   same-seam packet, mark it `convergence_pressure: true` with the seam named.
+   Under pressure the drafter may close a finding marked as a refinement of an
+   already-pinned clause by folding an explicit, bounded declared
+   residual/limitation into the contract text instead of another precision
+   pin — never for a `new_failure_mode` finding. Every finding still gets one
+   disposition; none is skipped. A fourth same-seam packet that still carries
+   `new_failure_mode` findings means the seam is under-specified, not
+   under-repaired: route a declare-limitation-or-continue choice to
+   `/rite-clarify`. AFK records the suspect seam in `state.md` and continues
+   within budgets — a coverage limitation is a product decision and is never
+   auto-declared.
+   Bind exact active `.devrites/work/<slug>/` targets and executable contract; after Vet READY, root
+   materializes the exact vetted workflow-artifact paths under
+   [`workflow-artifacts.md`](../devrites-lib/reference/standards/workflow-artifacts.md)
+   without dispatching the product wright.
+3. Reason about dependencies: [dependency-graph](reference/dependency-graph.md).
+   Reconcile the horizon register against `../rite-define/reference/plan-template.md`.
+   Preserve every `HZN-###` and unresolved item. Cite evidence when reclassifying the earliest
+   honest decision point; resolution or supersession also needs evidence. Never silently delete
+   an item. Planning choices resolve from source evidence or become bounded risk spikes with
+   discriminating criteria and fallback branches; local/checkpoint entries retain their owner,
+   trigger, bounds/fallback, and proof. A new human-owned blocker stops to `/rite-clarify`.
+   Reconcile `plan.md`'s canonical `Shared contract proof`: changed provider/consumer
+   boundaries keep one reused contract artifact ahead of both asserting tests, and unaffected
+   plans retain the specific no-impact statement. Missing, one-sided, duplicated-contract, vague, or
+   non-consuming proof routes to `/rite-vet` only after repair.
+   Reconcile the spec applicability map and retain every applicable standard's required
+   topology/data/integration owner, failure/recovery, deployment order, and proof output.
+   **Completion:** the slice graph is cycle-free and every dependency names an existing slice.
+4. Re-slice using vertical-slice rules: [slicing](reference/slicing.md) and
+   [task-breakdown](reference/task-breakdown.md). Prefer thin, shippable, verifiable.
+   **Completion:** every slice is independently shippable/provable or carries an irreducibility reason.
+5. Reconcile the candidate against steps 3 and 4, then the root updates `plan.md`, `tasks.md`,
+   `state.md`, and appends rationale to `decisions.md`. A rejected candidate
+   (malformed bundle, stale or non-unique anchor) or a drafter `Outcome: gap`
+   is one no-progress outcome on every open fingerprint in the fold; the
+   re-dispatch packet must name the rejection so the same hunks don't recur.
+   A gap naming genuinely human-owned information routes to `/rite-clarify`.
+   A drafter `Outcome: partial` is progress: materialize its complete findings,
+   then re-dispatch a narrowed packet for `remaining_findings` with anchors
+   re-derived from the just-updated files — same repair pass, fresh context.
+   A partial covering zero findings counts as no-progress. Findings in
+   `blocked_findings` route to `/rite-clarify`, never the re-dispatch.
+   Any change to `architecture.md`, `plan.md`, `tasks.md`, or `traceability.md` invalidates
+   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,
+   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`,
+   re-scan affected coverage, assumptions, uncertainty, and gates. Partial/Missing, unowned
+   material assumption, or open blocking/escalating question routes `/rite-clarify`/HITL.
+   Restore `CLEAR` only from current evidence.
+7. **Done when:** every slice is sized (builds + proves in one cycle; no slice scoring >3
+   left unjustified), the dependency order is acyclic, every open `drift.md` entry
+   was folded in one pass and marked resolved, the delta self-check is recorded,
+   revised artifacts agree with each other, no source files changed in
+   `revise` mode, the marked action is complete, and every changed
+   plan ends at `/rite-vet` rather than returning directly to build; horizon IDs stay stable,
+   reclassifications cite evidence, and no unresolved item vanished. The `Shared contract proof`
+   table or justified no-impact statement must still match the revised boundary set.
+   If any check fails, loop back: don't hand off a half-reshaped plan.
+
+When invoked inline by a controlling rite, return the completed Plan checkpoint
+to that caller so it can invoke Vet immediately. The phase boundary is not a
+user-facing stop unless a genuine HITL, safety/access, or exhausted-recovery
+condition was recorded.
+
+When invoked directly with no controlling caller and a planning artifact
+changed, become the caller for the mandated next step: save a return cursor
+(`return_phase`/`return_next_action`) naming this Plan pass as the caller —
+a direct Plan has no caller above it, so without the saved cursor Vet reads
+itself as top-level and its verdict becomes a user-facing command. Invoke
+`/rite-vet` inline and consume its results — `NEEDS REPLAN` re-enters repair
+internally under the fingerprint caps and is never emitted as a user-facing
+command; `NEEDS CLARIFICATION` and human-owned gates still reach the user.
+Stop only at Vet's boundary (READY readback; next step `/rite-build`). An
+unchanged plan keeps its recorded next step.
+
+> **Mid-flight discipline.** Do not change product behavior without confirmation or
+> absorb drift silently. See [`anti-patterns`](reference/anti-patterns.md).

package/pack/generated/devin/skills/rite-plan/reference/anti-patterns.md

@@ -0,0 +1,34 @@
+# rite-plan: anti-patterns
+
+Load this when standing a non-trivial re-plan decision, or when the agent
+feels reluctance toward asking the user before a behavior change.
+
+Pack-wide rationalizations + red flags: see [standards/anti-patterns.md](../../devrites-lib/reference/standards/anti-patterns.md).
+
+Authority: `.devin/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
+
+<!-- BEGIN RESLICE ROUTE-TO-ACTION -->
+- `FOLD` → reconcile `architecture.md`, `plan.md`, `tasks.md`, and `traceability.md` atomically; invalidate Vet/readiness; Vet.
+- `GUARD_AND_REPAIR` → no planning writes; Spec Drift Guard → Clarify → Plan repair → Vet.
+- `BLOCKED_INPUT` → no planning writes; exact diagnostic; recover input; reclassify.
+<!-- END RESLICE ROUTE-TO-ACTION -->
+
+## Phase-specific rationalizations
+
+| Excuse | Rebuttal |
+| --- | --- |
+| "User didn't ask for a re-plan." | A Spec Drift Guard event *is* a re-plan trigger: ask is courtesy, the route is automatic. |
+| "I can fix the slice mid-build, no need to update tasks." | `tasks.md` is the contract `/rite-build` reads. A fix that isn't there isn't visible to the next phase. |
+| "Reordering slices is cosmetic." | Dependency order controls risk discovery; risk-first wins because it surfaces blockers early. |
+| "This drift is small enough to absorb silently." | Silent drift = unrecorded decision = future "why does this work?" debugging session. |
+| "I can change product behavior to make the plan fit." | **RSLICE-PLAN-001** — Implementation convenience cannot rewrite product behavior. |
+| "Topology or a small criterion delta decides the route." | **RSLICE-PLAN-002** — Topology/count and “small” never override the canonical classifier; sufficient authoritative contract delta follows its mapped action. |
+| "Chat, stale material, or the convenient map is enough." | **RSLICE-PLAN-003** — Exact current byte-bound directives are authority; cached, remembered, summarized, paraphrased, or inferred chat and stale material are not. |
+
+## Red Flags
+
+- About to change product behavior, acceptance, or scope without asking the user.
+- `drift.md` entry unresolved while planning the next slice.
+- A "mode" invented that isn't one of `decompose / reslice / repair / reorder / split / unblock / course-correct / revise`.
+- Slices reordered without updating dependency notes: order changed, rationale didn't.
+- Repairing a drift event by silently widening the spec rather than narrowing the plan.

package/pack/generated/devin/skills/rite-plan/reference/dependency-graph.md

@@ -0,0 +1,48 @@
+# Dependency graph
+
+Order slices by what must exist before what. Keep it in `plan.md` as plain text.
+
+## Build the graph
+1. For each slice, list its hard prerequisites (a model it queries, an endpoint it
+   calls, a component it composes, a contract/schema/config it consumes, or a deployable
+   version that must already tolerate the change).
+2. Draw edges prerequisite → dependent.
+3. Topologically sort. Independent slices can be built in any order (or noted as
+   parallelizable for the user).
+
+```
+SLICE-001 (schema)  ->  SLICE-002 (write API)  ->  SLICE-003 (UI form)
+                   \->  SLICE-004 (read API)   ->  SLICE-005 (UI list)
+SLICE-006 (config)  -> independent
+```
+
+## Within a tier: risk-first
+Among slices that are equally unblocked, do the **riskiest** first: the one most
+likely to invalidate the plan (new integration, uncertain library behavior, migration).
+Finding drift early is cheap; finding it at seal time is not.
+
+## Smells
+- A slice with many prerequisites → probably too big; reslice for a thinner cut that
+  stands alone.
+- A cycle (A needs B needs A) → the boundary is wrong; split the contract
+  (`devrites-api-interface`) so one side can land against one canonical contract.
+  Do not hide the cycle with duplicated types, a service locator, or an unowned stub.
+- Everything depends on slice 1 → slice 1 is doing too much.
+- File-disjoint slices share a database migration chain, generated contract, lockfile,
+  queue/port, environment, or deployable → serialize that resource or isolate it explicitly.
+
+## Cross-boundary edges
+Mark edges that cross a frontend/backend or service boundary. Those slices should
+define the contract first (so both sides can proceed) and trigger `devrites-doubt`
+before standing the interface.
+
+After editing `tasks.md`, run `devrites-engine check task-graph <slug>` before Vet.
+`check readiness` and `check seal` also reject cycles, unknown dependencies,
+malformed tokens, duplicate slice IDs, a missing `Dependencies`/`depends_on`
+line, and a `depends_on` set that disagrees with `Dependencies`. Cycles or
+unknown dependencies block readiness.
+
+For monorepos/multiple repositories, annotate the proven root and deployable on each node.
+For data/integration changes, include recovery ordering: expand before new writers,
+backfill before contract, consumer compatibility before provider exposure, and monitoring
+before rollout. The graph is incomplete if code order is safe but deploy order is not.

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

@@ -0,0 +1,105 @@
+# Re-plan & repair modes
+
+`/rite-plan` runs in one of these modes. Pick from `$ARGUMENTS` or infer from state.
+
+Authority: `.devin/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
+
+<!-- BEGIN RESLICE ROUTE-TO-ACTION -->
+- `FOLD` → reconcile `architecture.md`, `plan.md`, `tasks.md`, and `traceability.md` atomically; invalidate Vet/readiness; Vet.
+- `GUARD_AND_REPAIR` → no planning writes; Spec Drift Guard → Clarify → Plan repair → Vet.
+- `BLOCKED_INPUT` → no planning writes; exact diagnostic; recover input; reclassify.
+<!-- END RESLICE ROUTE-TO-ACTION -->
+
+## decompose
+
+First (or fresh) breakdown into vertical slices. Use `task-breakdown.md` +
+`slicing.md`. Output: a populated `tasks.md` and an ordered `plan.md` graph.
+
+## reslice
+
+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.
+
+## repair (after Spec Drift Guard)
+
+A drift event stopped the build. Steps:
+
+1. Read the `drift.md` entries and their classifications. Fold EVERY open entry
+   and accepted finding for the affected artifacts in ONE pass, never serially.
+2. If the user answered a drift question, encode that decision in `decisions.md`.
+3. Update `spec.md` (only the affected sections) and `plan.md`/`tasks.md` to match
+   reality. Adjust acceptance criteria if they were wrong.
+   **Write the pointer, not the history.** Name the findings a fold closes by ID, one line
+   of meaning each; never restate prior folds, prior DEC lists, or closed-round narrative in
+   `architecture.md`/`plan.md`/`tasks.md`/`traceability.md`. That text belongs in
+   `decisions.md`, or in `history/` via [Budget relocation](#revise) once closed, so each
+   fold appends a bounded line. A banner that grows with the round count is the defect.
+4. Mark each `drift.md` entry **resolved** with the resolution + date.
+5. **Self-check and self-attack the repaired candidate on the delta before
+   handoff** — re-verify every invariant the correction touched (acyclic
+   dependency graph, bidirectional traceability, Shared contract proof vs
+   boundary set, sizing, no correction-created regression), then probe the
+   delta against the reviewers' attack classes (race/observation windows,
+   alias escapes, ordering gaps, capability gaps, unbounded blocking,
+   happy-path-only coverage); fold a fix or a named bounded residual into
+   the same pass. Record both in the Plan
+   checkpoint; Vet's recheck verifies it rather than rediscovering the defect a
+   loop later.
+6. Resume at the corrected slice.
+Never quietly delete a requirement; use the marked action before contract edits.
+
+## reorder
+
+Dependency order is wrong or suboptimal. Recompute the graph (`dependency-graph.md`),
+re-sort risk-first within tiers, update `plan.md`'s implementation order.
+
+## split (backend/frontend contract)
+
+A slice couples two sides too tightly. Define the contract first (shape, status codes,
+errors: `devrites-api-interface`), then split into a backend slice (can land with a
+stub consumer) and a frontend slice (can land against a mock/real contract).
+
+## unblock
+
+An exhausted fingerprint blocks diagnosis, not symptom. Route around/reslice; escalate
+only for scope change. If proof removed that cause but symptom remains, keep the dead
+end and plan a new diagnosis/proof fingerprint. Never clear/reuse old one.
+
+## course-correct
+
+Mid-build user pivot. Apply the marked action, choose rollback or forward-fix, and
+update permitted artifacts atomically (`MVP cut` is the named retreat). Invalidate
+Vet/readiness when contract or topology changes.
+
+**Feature-ceiling cut.** When unbuilt slices exceed the
+[feature ceiling](slicing.md#feature-ceiling-split-an-epic-never-override-the-budget),
+`MVP cut` keeps the built slices plus the thinnest shippable unbuilt subset here; the
+remaining slices, their REQ/AC IDs and proof rows move verbatim into a named
+continuation list (spec `Non-goals` → future `/rite-spec <slug>-2`, `-3`, …) through
+the Spec Drift Guard. IDs never renumber; each ID is owned by exactly one workspace.
+Record the sequence once in `decisions.md`.
+
+## revise
+
+Artifact-only reconciliation of `spec.md`, `architecture.md`, `plan.md`, `tasks.md`,
+or `traceability.md` — never source. Propose/confirm the file set first. Only explicit
+`/rite-upgrade` with a `repairable` assessment may authorize neutral workspace edits.
+
+Unchanged acceptance/behavior with non-equivalent `proposed_coverage` is a
+contradictory input: the canonical classifier blocks it — there is no fourth
+route (see [`acceptance-preserving-reslice.md`](../../devrites-lib/reference/standards/acceptance-preserving-reslice.md)).
+
+**Budget relocation** (admitted by `/rite-upgrade`, or by the phase owner when
+`orient` reports `over: true`): move checkpoint narrative, historical fold text and
+closed-round accounts verbatim from `state.md`/`tasks.md`/`plan.md`/`architecture.md`/
+`eng-review.md` into `history/<file>-<YYYYMMDD>.md`, packets/accounts from the root
+into `packets/`, leaving a one-line pointer. Cursor, live slices, open findings, IDs,
+answers, decisions and bindings stay unchanged; nothing is deleted or reworded.
+Re-emit the readiness binding when a readiness input moved.
+
+## Always
+
+Update `state.md` (phase, next step) and append a dated line to `decisions.md`
+explaining *why* the plan changed. Preserve mapped-action decisions.

package/pack/generated/devin/skills/rite-plan/reference/slicing.md

@@ -0,0 +1,168 @@
+# Slicing
+
+DevRites builds in **thin vertical slices**: each slice cuts through every layer it
+needs (data → logic → API → UI) and leaves the system in a working, testable state.
+
+## Vertical, not horizontal
+Horizontal layering delays integration feedback. Vertical slicing delivers a usable path:
+```
+SLICE-001: Create a task   (DB + API + minimal UI)   -> user can create + test passes
+SLICE-002: List tasks      (query + API + UI)         -> user can see them
+SLICE-003: Edit a task     (update + API + UI)        -> user can modify
+SLICE-004: Delete a task   (delete + API + UI + confirm) -> full CRUD
+```
+
+## Sizing a slice
+A slice is the right size when it:
+- delivers one observable capability end-to-end;
+- can finish its writer, independent review, and slice proof within `/rite-build`;
+- has acceptance criteria you can verify with evidence;
+- can be rolled back on its own;
+- is worth its own review gate: a reviewer could meaningfully reject *this* slice while
+  approving its neighbor. If two slices can only pass or fail together, they're one slice.
+
+Size by independent invariants, failure modes, and proof seams, not file count or
+the word "and". Split independently acceptable/provable responsibilities; several
+files may serve one inseparable capability. Full feature `/rite-prove` follows all
+slices; slice proof never replaces final integration or acceptance proof.
+
+For `Complexity` and irreducible boundaries, use the canonical
+[`tasks.md` slice grammar](../../devrites-lib/reference/workspace-artifact-schema.md#canonical-slice-grammar).
+Keep the smallest cut that stands alone end-to-end; do not add slices or gates for
+fragments that can only pass together. No slice size guarantees first-pass correctness.
+
+## How many slices?: derive, don't dictate
+The slice **count is an output, not an input.** It falls out of the work: one slice per
+independently-shippable vertical increment that satisfies one (or a tight group of)
+acceptance criteria and passes the sizing test above. A 2-criterion feature is 1-2 slices;
+a 12-criterion feature is however many thin end-to-end cuts those 12 need.
+
+- **Never slice to a target number.** Don't pad a small feature into "5 slices" or
+  compress a large one into "3" because a figure was named.
+- **A user-supplied count is a hint at most.** If the user says "do it in 4", slice the
+  work logically first; if your honest decomposition differs, present the logical count
+  and *why*, then let them redirect: don't silently force their number.
+- **Re-size by the rule, not the tally** (`/rite-plan reslice`): split a slice because it
+  failed the sizing test, not to hit a count.
+
+`.devrites/AFK` `max_slices` limits unattended execution, never plan decomposition.
+
+## Feature ceiling: split an epic, never override the budget
+
+The derived count is also a size signal. A decomposition that cannot fit the
+`tasks.md` / `plan.md` / `traceability.md` budgets in
+[`workspace-artifact-schema.md`](../../devrites-lib/reference/workspace-artifact-schema.md)
+(about ten canonical slices) is an epic: every Vet/Doubt/Build review re-reads the
+whole surface, each round finds new material, and the loop never converges.
+`Budget override` never covers slice or acceptance-criteria count.
+
+- Keep the thinnest independently shippable subset here; the rest becomes spec
+  `Non-goals` (via the Spec Drift Guard), each continuation a named future `/rite-spec`
+  workspace. Record the sequence once in `decisions.md`.
+- Acceptance-preserving: every REQ/AC keeps its ID, owned by exactly one workspace.
+- Earliest owner wins: Temper's one-sentence test → Define/Plan decomposition → Vet §0
+  scope finding → `/rite-plan course-correct` (`MVP cut`). Mid-build, unbuilt slices
+  beyond the ceiling move; built slices stay.
+- The ceiling bounds one **workspace**, never the product: the sequence delivers every
+  slice, in order, each with its own Vet/Build/Review loop. A human may still accept a
+  single larger workspace by recording the decision in `decisions.md` and a structural
+  `Budget override:` in the affected artifacts; the extra review rounds on the whole
+  surface are then the accepted, named cost. The deterministic gate
+  (`check readiness`/`check seal`) blocks only a material overshoot without such an
+  override, so the choice stays explicit rather than accidental.
+
+### Continuation workspaces
+
+Granularity is a real cost choice, not a formality: a workspace costs ~8–12 fixed
+dispatches (drafter, plan reviewer, proof runner, spec/code reviewers, seal roster;
+Temper is skippable when the parent's `strategy.md` already covers the scope) plus
+~3–5 per slice. The split does not remove per-slice cost; it bounds each round's
+context, stops the non-convergent whole-surface loop, isolates a plan defect's blast
+radius to its own workspace, and lets independent continuations run in parallel.
+
+Make each continuation cheap and drift-free:
+
+- `brief.md` names the parent slug and the sequence position; `decisions.md` holds the
+  sequence once (in the parent).
+- The child's `state.md` seeds the durable cursor at creation — `sequence_parent` =
+  parent slug, `sequence_position` = parent position + 1,
+  `sequence_workspaces_remaining` = parent remaining − 1, and `sequence_role:
+  release` only when the recorded entry is the sequence's release milestone.
+  Values derive from the parent's `state.md` and its `decisions.md` record,
+  exactly once; resume re-derives the same values rather than charging again.
+  A workspace that is not a recorded continuation leaves all four rows absent.
+  This is what `state merge-manifest` walks and what the release-union gate reads,
+  so a manually opened continuation needs the same seeding as an armed run.
+- Read the parent's `architecture.md`, `plan.md`, `decisions.md` (or its archived copy)
+  as **design input** — never re-derive settled architecture, dependency choices, or
+  interfaces. Proof is always fresh for the new candidate; parent evidence is cited as
+  input, never as proof for this workspace.
+- Shared interfaces, data shapes, and contracts are pinned **once**, in the workspace
+  that introduces them, and referenced afterwards. A continuation that must change a
+  pinned contract does so through its own `plan.md` shared-contract proof and an ADR
+  that names the superseded owner — never by silently re-deciding it.
+- A request that names a recorded continuation is a new workspace, not
+  `/rite-plan revise` on the parent.
+- Phases chain automatically only **inside** one workspace (`/rite-autocomplete`
+  drives spec → clarify → temper → define → vet → build × slices → prove → polish →
+  review → seal; plain HITL chains plan↔vet inline and stops at each other boundary).
+  Next continuation is a new invocation by default. Same-run chaining is
+  `continue_sequence: true` (Deferred-ship).
+
+### Release milestone (full-picture gate)
+
+Milestone gates are feature-scoped: `prove` proves *that* workspace's acceptance,
+`review`/`seal` judge *that* candidate. A product release therefore needs one more
+workspace — the **release milestone** — planned last, whose subject is the assembled
+product:
+
+- Its ACs are product-level: cross-milestone integration, end-to-end journeys,
+  performance/release budgets, docs/rollout. Milestone ACs stay owned by their
+  milestones and are **referenced** here, never re-owned.
+- Its candidate manifest lists the union of shipped surfaces, so one `prove` → `review`
+  → `seal` binds the whole product, and one `ship` commits/pushes/tags the release.
+  Its `state.md` cursor carries `sequence_role: release` (seeded when the recorded
+  continuation is the sequence's release entry); `check candidate`/`check seal`
+  then require the manifest to cover the whole recorded chain. Build that union
+  deterministically: `devrites-engine state merge-manifest <release-slug>` walks
+  the recorded `sequence_parent` chain (live `work/` first, then `archive/`) and
+  folds every predecessor's manifest into the release `## Candidate manifest`;
+  on a path collision the later sequence position's row wins. An explicit
+  ordered `<pred>...` argument exists for chains recorded before the sequence
+  cursor fields.
+- Earlier milestones keep their own slice-level proof and their own prove/review/seal;
+  that is what stops a late defect from invalidating 170 slices of work. Skipping a
+  milestone's proof is allowed only by recording the decision — the release milestone
+  then carries the full acceptance burden, and that cost is the named trade-off.
+- The capability ledger (`.devrites/specs/<capability>/spec.md`) accumulates the
+  product picture across milestones; Polish folds each milestone's deltas.
+- **Deferred-ship sequence** (`.devrites/AFK` `continue_sequence: true`, `max_workspaces: N`):
+  milestones are sealed but not shipped, and the armed run opens the next recorded
+  continuation automatically; local `WIP(<slug>):` checkpoints still land with
+  human summaries (never a slice id),
+  so the tree stays clean. One release ship at the end collapses the sequence's
+  checkpoints into the single release commit, pushes/tags it, and may archive the
+  sealed predecessors. Because no milestone boundary was shipped, later work can touch
+  an earlier milestone's surfaces without an affected-re-proof trigger — so the release
+  milestone re-proves the union acceptance map, and that full re-proof is this mode's
+  named cost. Trade-off against per-milestone ship: no shared-history rollback point
+  per increment, one Git approval at the end.
+- What is full-surface here is the **review**: reviewers see the whole product diff.
+  Re-proof stays targeted — this milestone's product ACs, everything a later milestone
+  touched, and any uncertain closure. Milestone evidence is cited only under
+  [evidence validity](../../devrites-lib/reference/candidate-integrity.md#evidence-validity)
+  with explicit unchanged-input/dependency justification and a link to the original
+  account; a blind re-proof of every milestone AC is a recorded decision, not a default.
+
+## First slice
+Make slice 1 the **thinnest useful end-to-end path**. It flushes out integration and
+convention surprises early, while changes are cheap.
+
+**Risk-first exception.** When the biggest risk is a technical *unknown*: "will this library
+even do X?", "can we hit the latency target?": let slice 1 (or a throwaway spike ahead of it)
+prove that unknown, even if it isn't the thinnest user-facing path. Fail the risky bet first,
+while pivoting is still cheap.
+
+## Slice independence
+Order by dependency, but minimize coupling. A slice that needs three other slices first
+is a smell: look for a thinner cut that stands alone.

package/pack/generated/devin/skills/rite-plan/reference/task-breakdown.md

@@ -0,0 +1,42 @@
+# Work-item breakdown
+
+How to turn a spec into ordered, vertical slices in `tasks.md`.
+
+## Each slice is one task
+
+Use the complete canonical grammar in
+[`workspace-artifact-schema.md`](../../devrites-lib/reference/workspace-artifact-schema.md#canonical-slice-grammar).
+This reference owns decomposition; the shared schema owns field names and meanings.
+
+## Process
+1. List the capabilities the spec promises.
+2. Map each to a vertical slice (thinnest end-to-end cut).
+3. Order by dependency; risk-first within a tier (do the scary slice early while it's
+   cheap to change).
+4. Mark which slices touch UI (→ frontend craft + browser proof), map each to the design
+   brief states, and give each a binary visual acceptance target. Mark which slices cross
+   a module/service boundary (→ `devrites-api-interface`, `devrites-doubt`). For a changed
+   provider/consumer boundary, map the plan's `Shared contract proof` artifact before its
+   provider- and consumer-side asserting tests; both tests consume that same artifact and
+   their slice dependencies preserve the order. Do not duplicate the contract in each slice.
+   For each applicable topology/data/integration row, assign its owner, failure/recovery
+   case, and proof to a slice; preserve deployment/resource ordering from the plan.
+5. Write or update `traceability.md` so every `AC-###` maps to ≥1 `SLICE-###`, a
+   planned proof, evidence status, and likely touched files.
+6. Sanity check: every acceptance criterion in `spec.md` maps to ≥1 slice; no slice has
+   an unowned criterion.
+7. Resolve every foreseeable human-owned checkpoint now. Keep a build-time checkpoint only
+   when it needs evidence unavailable before code or mandatory action-time approval, and say why.
+8. Make every `Tests/proof` entry executable: exact command, working directory, prerequisites,
+   expected signal, and mutable inputs whose provenance evidence must bind.
+
+## Keep it honest
+- **Interfaces prevent cross-slice drift.** A slice-wright sees only its own contract; the
+  `Interfaces` line is how it learns the names and types neighboring slices use. A function
+  called `clearLayers()` in slice 3 and `clearFullLayers()` in slice 7 is a planning bug:
+  name shared symbols once, here.
+- Don't pre-write code in the task: describe the outcome, not the implementation.
+- Don't bundle "while we're here" work into a slice. That's scope creep; log it as a
+  follow-up instead.
+- Don't slice to a target number: the count comes from the capabilities + the sizing
+  rule (`slicing.md`), not a figure anyone named.