[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DMJ29WKRTESZHHWMZBDD6D":3,"skill-same:01M7DMJ29WKRTESZHHWMZBDD6D":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M7DMJ29WKRTESZHHWMZBDD6D","mission-slice-sop",null,"Use when starting, building, handing off, restoring, or closing a mission or slice under the default lightweight SDLC.","mvschwarz\u002Fopenrig-world","mvschwarz","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F171890339?v=4","01M7DM95A4N5936P8G2FTSPMY7","Mike Schwarz","01M7DM95AX80NY8HZA7XXDYAZR",16,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop-review-pair\u002Fagents\u002Fworkshop\u002Fskills\u002Fmission-slice-sop\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mission-slice-sop\ndescription: >-\n  Use when starting, building, handing off, restoring, or closing a mission or slice under the default lightweight SDLC.\nmetadata:\n  openrig:\n    stage: shipped\n    sibling_skills:\n      - queue-handoff\n      - seat-continuity-and-handover\n      - claude-compaction-restore\n---\n\n# Mission\u002FSlice SOP — Part A\n\nUse this skill to actually **do** mission\u002Fslice work: track on the canonical files, record what you proved, hand off through them, and survive compaction on them. **Do the work described here; do not merely explain the protocol.**\n\n**Full convention SSOT:** repo `docs\u002Freference\u002Fsdlc-conventions.md`; installed `$OPENRIG_HOME\u002Freference\u002Fsdlc-conventions.md`. This skill is the concise Part-A teaching surface and does not replace the full convention.\n\n## Resolve the work first\n\nRun `rig whoami --json`, then resolve `project.yaml -> mission.yaml -> active\nslice.yaml -> selected component or wave map -> addressed context`. The complete\nlookup and precedence rule is `docs\u002Freference\u002Fproduct-journey-sdlc.md#resolve-the-selected-path`\n(installed: `$OPENRIG_HOME\u002Freference\u002Fproduct-journey-sdlc.md#resolve-the-selected-path`).\nRead the selected addresses and source needed for this task; skills available in\nyour profile are capabilities, not a mandatory reading list. No composition means\nlight Part A. Role names and idle seats add no gates. Explicit rigor and authored\nwave boundaries retain their named checks.\n\nThe light inner loop is ground yourself → build → test with your own eyes →\niterate → record and return the whole outcome. The builder may hold this check\non a tiny change. Independent review runs only when selected, and once at an\nauthored wave boundary rather than once per slice.\n\nPart B is defined in the conventions SSOT and runs only when explicitly assigned\nto named work. If you believe it is needed, state the reason to the owner and\ncontinue on the selected path until that choice changes.\n\n## Proportionality — this SOP serves shipping; it is not the work itself\n\nThe working product is the deliverable. This bookkeeping exists so the work survives handoff, compaction, and review — nothing more. **Match it to stakes.** The `rig scope audit` backstop is **advisory and fail-open**: it never blocks a build and is not a gate you clear before proceeding. If you're spending more time on the convention files or the audit than on the running product, stop and go build. Running the full apparatus on a small change is the letter-worship failure, not diligence.\n\n## The three role contracts\n\n- **Planning agent:** records what the slice is for and what \"done\" looks like, in the slice's own words; produces mockups for UI deliverables so the builder has something to look at (a UI slice with no mockup is an incomplete plan; non-UI slices have none — not a gate).\n- **Build agent:** builds it, and **looks at the mockups**. Verifies by running the thing.\n- **QA agent (owns the compare):** compares planned vs delivered per deliverable, records the verdict and the note. On mismatch: fix-and-re-review, or kick back with the reason — never escalate a raw mismatch to the human.\n\nThese three are a division of labour, not a chain of gates. One agent may hold all three on a small slice.\n\n## The current file contract\n\n> These files are the **operating surface of the work** — you track on them, record on them, hand off through them, and survive compaction on them. Keep them current because that is what lets the work survive. But they **serve** the product; they are not the product. If you're polishing files while the actual thing isn't shipping, you've inverted it: go build, then update them.\n\n- **Slice:** `SPEC.md`, `PROGRESS.md`, `PROOF.md`, and `proof\u002F`.\n- **Mission:** `SPEC.md` and `NOTES.md`.\n\n## Per-file rules — WHO \u002F WHEN \u002F HOW\n\n### SPEC.md\n- **WHO:** the planning owner authors it; builders and reviewers read it as the scope and intent source.\n- **WHEN:** at creation and whenever scope changes.\n- **HOW:** a slice carries `intent:` in frontmatter and opens with `## Intent`, `## Mini-requirements`, and `## Proof contract`. A mission carries its intent and mission-level specification in the same authored node file. Keep depth proportional to the work.\n\n### PROGRESS.md\n- **WHO:** the orchestrator owns the current state; every agent logs its own outcomes.\n- **WHEN:** on material delivery-state changes and at acceptance.\n- **HOW:** keep current delivery state in `## Current state`, naming who the next move waits on, and check that against the source (the PR on GitHub, the queue) before you rely on it; append material outcomes with links to proof under `## Outcomes`. Retain historical entries and existing checkboxes without treating them as current acceptance authority. For a selected proof policy, use `rig proof show \u003Cslice>` for current readiness; keep frontmatter `stage`\u002F`verified` honest.\n\n### PROOF.md + proof\u002F\n- **WHO:** the impl\u002FQA pair that worked the slice.\n- **WHEN:** before you call a slice done.\n- **HOW:** say what you verified and how you verified it — **by effect**: you ran it and looked at the result. Put supporting media under `proof\u002F`. State plainly what is proven and what is **not**; an honest \"this half is untested\" is worth more than a checkmark. If a drop verb is in play for this slice, prefer it over hand-placing files so the artifact carries its own provenance.\n\n### NOTES.md\n- **WHO:** any agent updates `§1` (top-of-mind); each seat owns and appends to its own `§A–§X`.\n- **WHEN:** on material mission-context changes; a compacting agent **files its state here BEFORE compaction and reads it on restore.**\n- **HOW:** accruing tribal knowledge — `§1` ≤ 5–15 lines (gates, open decisions, surprises); per-seat continuation entries (latest = truth; other seats read-only). Pointer-first; don't duplicate.\n\n## The lifecycle (4 legs)\n\n**SCAFFOLD** (`rig scope` creates the files from templates) → **POPULATE** (agents fill them as work happens) → **PROJECT** (the Living Notes UI reads them into INTENT → PLAN → DELIVERED) → **VERIFY** (`rig scope audit`, advisory). \"Loose freeform write + deterministic verify.\"\n\n## Hot-potato (handoffs)\n\nEnd every turn by passing the ball — a `rig queue handoff` to the next agent. The handoff verb is **transactional**: it closes the source as handed-off and mints the successor owned by `--to`, so the baton cannot be dropped. A handoff terminates only at the orchestrator seat, which holds the context to judge whether a park is legitimate.\n\n**A plain `rig queue create` row is informational** — a durable message. It is not a baton and does not carry this obligation. Use `handoff` when you are passing real work; use `create` when you are informing.\n\nNever go idle holding a baton.\n\n## Records\n\nThe rules for recording a slice's state are in the conventions SSOT (`docs\u002Freference\u002Fsdlc-conventions.md` in the OpenRig source repository, `$OPENRIG_HOME\u002Freference\u002Fsdlc-conventions.md` when installed). Read them before you stamp, judge or report:\n\n- **Stamps, stages and proof:** A2 (`rig proof judge`, `rig scope slice stage` and `verified`) and B2–B3 (`rig scope slice approve --scope spec|delivery`, `rig proof add` and `--candidate-sha`).\n- **Built and merged:** the release-mission paragraphs of A1 (`candidate:\u003Csha>`, `merged:\u003Cpr-number>`, `arrangement.source.integration_ref`).\n- **Dispatch data:** the DISPATCH DATA row of the component menu (the `worktree_path=` body line).\n- **Editing judged evidence resets the judgment.** An accepted `rig proof judge` records the sha256 of the evidence it cites; edit that evidence (the cited section, when it cites a heading), the contract item's text or the scope's proof policy, and the item reads `unknown` until you judge it again.\n\n## Verify (deterministic backstop)\n\nRun `rig scope audit` at slice-close. Every convention check is **advisory \u002F fail-open** — it records and advises, never blocks a write. Fix what's real, skip what isn't, keep moving. **A clean audit score is not required to proceed.**\n\n## Reading terminal captures — KNOWN GOTCHA: ghost-text autocomplete is NOT real\n\nWhen you `rig capture` a pane, **greyed \u002F ghost autocomplete suggestions are NOT real content** — they are autocomplete *previews*, not typed, staged, or committed input. **This has been faking agents out a lot**: reading a ghost suggestion in a peer's input box as \"staged text they're about to send,\" then reasoning on a string that was never there.\n\n**Rule:** ignore ghost\u002Fautosuggest text entirely. Only *committed\u002Frendered* pane output is real. When it matters, verify at source (git, the queue, the actual event) — never off a capture's ghost line.\n\nA plain capture loses the grey, so `rig capture` reads it for you. For a Claude Code or Codex seat, a\n`[rig capture: \u003Cseat>: input box: ...]` note on stderr (and `inputBox` in `--json`) says whether the input box's text\nis likely a harness suggestion or typed, from where the cursor is and whether the text is drawn faint. Don't act on\n`likely-suggestion` text as anyone's intent, and treat `unknown` as unknown: verify at source.\n\n## Moment-of-truth checklist\n\n- **Starting a slice?** → do you know what it's for and what done looks like? mockups attached (UI slices)? **Are you on the light path?** (You are, unless the mission owner assigned the overlay.)\n- **Finishing a slice?** → does `PROOF.md` say what you actually verified, by effect, including what is NOT covered? `PROGRESS.md` updated? mission `NOTES.md` refreshed? handed off via `rig queue handoff`?\n- **Compacting?** → file your state in mission `NOTES.md`; on restore, read it plus the active slice's `SPEC.md`, `PROGRESS.md`, and `PROOF.md`.\n- **Starting on a mission?** → read mission `SPEC.md`, `NOTES.md`, and the conventions SSOT.\n","# Mission\u002FSlice SOP — Part A\n\nUse this skill to actually **do** mission\u002Fslice work: track on the canonical files, record what you proved, hand off through them, and survive compaction on them. **Do the work described here; do not merely explain the protocol.**\n\n**Full convention SSOT:** repo `docs\u002Freference\u002Fsdlc-conventions.md`; installed `$OPENRIG_HOME\u002Freference\u002Fsdlc-conventions.md`. This skill is the concise Part-A teaching surface and does not replace the full convention.\n\n## Resolve the work first\n\nRun `rig whoami --json`, then resolve `project.yaml -> mission.yaml -> active\nslice.yaml -> selected component or wave map -> addressed context`. The complete\nlookup and precedence rule is `docs\u002Freference\u002Fproduct-journey-sdlc.md#resolve-the-selected-path`\n(installed: `$OPENRIG_HOME\u002Freference\u002Fproduct-journey-sdlc.md#resolve-the-selected-path`).\nRead the selected addresses and source needed for this task; skills available in\nyour profile are capabilities, not a mandatory reading list. No composition means\nlight Part A. Role names and idle seats add no gates. Explicit rigor and authored\nwave boundaries retain their named checks.\n\nThe light inner loop is ground yourself → build → test with your own eyes →\niterate → record and return the whole outcome. The builder may hold this check\non a tiny change. Independent review runs only when selected, and once at an\nauthored wave boundary rather than once per slice.\n\nPart B is defined in the conventions SSOT and runs only when explicitly assigned\nto named work. If you believe it is needed, state the reason to the owner and\ncontinue on the selected path until that choice changes.\n\n## Proportionality — this SOP serves shipping; it is not the work itself\n\nThe working product is the deliverable. This bookkeeping exists so the work survives handoff, compaction, and review — nothing more. **Match it to stakes.** The `rig scope audit` backstop is **advisory and fail-open**: it never blocks a build and is not a gate you clear before proceeding. If you're spending more time on the convention files or the audit than on the running product, stop and go build. Running the full apparatus on a small change is the letter-worship failure, not diligence.\n\n## The three role contracts\n\n- **Planning agent:** records what the slice is for and what \"done\" looks like, in the slice's own words; produces mockups for UI deliverables so the builder has something to look at (a UI slice with no mockup is an incomplete plan; non-UI slices have none — not a gate).\n- **Build agent:** builds it, and **looks at the mockups**. Verifies by running the thing.\n- **QA agent (owns the compare):** compares planned vs delivered per deliverable, records the verdict and the note. On mismatch: fix-and-re-review, or kick back with the reason — never escalate a raw mismatch to the human.\n\nThese three are a division of labour, not a chain of gates. One agent may hold all three on a small slice.\n\n## The current file contract\n\n> These files are the **operating surface of the work** — you track on them, record on them, hand off through them, and survive compaction on them. Keep them current because that is what lets the work survive. But they **serve** the product; they are not the product. If you're polishing files while the actual thing isn't shipping, you've inverted it: go build, then update them.\n\n- **Slice:** `SPEC.md`, `PROGRESS.md`, `PROOF.md`, and `proof\u002F`.\n- **Mission:** `SPEC.md` and `NOTES.md`.\n\n## Per-file rules — WHO \u002F WHEN \u002F HOW\n\n### SPEC.md\n- **WHO:** the planning owner authors it; builders and reviewers read it as the scope and intent source.\n- **WHEN:** at creation and whenever scope changes.\n- **HOW:** a slice carries `intent:` in frontmatter and opens with `## Intent`, `## Mini-requirements`, and `## Proof contract`. A mission carries its intent and mission-level specification in the same authored node file. Keep depth proportional to the work.\n\n### PROGRESS.md\n- **WHO:** the orchestrator owns the current state; every agent logs its own outcomes.\n- **WHEN:** on material delivery-state changes and at acceptance.\n- **HOW:** keep current delivery state in `## Current state`, naming who the next move waits on, and check that against the source (the PR on GitHub, the queue) before you rely on it; append material outcomes with links to proof under `## Outcomes`. Retain historical entries and existing checkboxes without treating them as current acceptance authority. For a selected proof policy, use `rig proof show \u003Cslice>` for current readiness; keep frontmatter `stage`\u002F`verified` honest.\n\n### PROOF.md + proof\u002F\n- **WHO:** the impl\u002FQA pair that worked the slice.\n- **WHEN:** before you call a slice done.\n- **HOW:** say what you verified and how you verified it — **by effect**: you ran it and looked at the result. Put supporting media under `proof\u002F`. State plainly what is proven and what is **not**; an honest \"this half is untested\" is worth more than a checkmark. If a drop verb is in play for this slice, prefer it over hand-placing files so the artifact carries its own provenance.\n\n### NOTES.md\n- **WHO:** any agent updates `§1` (top-of-mind); each seat owns and appends to its own `§A–§X`.\n- **WHEN:** on material mission-context changes; a compacting agent **files its state here BEFORE compaction and reads it on restore.**\n- **HOW:** accruing tribal knowledge — `§1` ≤ 5–15 lines (gates, open decisions, surprises); per-seat continuation entries (latest = truth; other seats read-only). Pointer-first; don't duplicate.\n\n## The lifecycle (4 legs)\n\n**SCAFFOLD** (`rig scope` creates the files from templates) → **POPULATE** (agents fill them as work happens) → **PROJECT** (the Living Notes UI reads them into INTENT → PLAN → DELIVERED) → **VERIFY** (`rig scope audit`, advisory). \"Loose freeform write + deterministic verify.\"\n\n## Hot-potato (handoffs)\n\nEnd every turn by passing the ball — a `rig queue handoff` to the next agent. The handoff verb is **transactional**: it closes the source as handed-off and mints the successor owned by `--to`, so the baton cannot be dropped. A handoff terminates only at the orchestrator seat, which holds the context to judge whether a park is legitimate.\n\n**A plain `rig queue create` row is informational** — a durable message. It is not a baton and does not carry this obligation. Use `handoff` when you are passing real work; use `create` when you are informing.\n\nNever go idle holding a baton.\n\n## Records\n\nThe rules for recording a slice's state are in the conventions SSOT (`docs\u002Freference\u002Fsdlc-conventions.md` in the OpenRig source repository, `$OPENRIG_HOME\u002Freference\u002Fsdlc-conventions.md` when installed). Read them before you stamp, judge or report:\n\n- **Stamps, stages and proof:** A2 (`rig proof judge`, `rig scope slice stage` and `verified`) and B2–B3 (`rig scope slice approve --scope spec|delivery`, `rig proof add` and `--candidate-sha`).\n- **Built and merged:** the release-mission paragraphs of A1 (`candidate:\u003Csha>`, `merged:\u003Cpr-number>`, `arrangement.source.integration_ref`).\n- **Dispatch data:** the DISPATCH DATA row of the component menu (the `worktree_path=` body line).\n- **Editing judged evidence resets the judgment.** An accepted `rig proof judge` records the sha256 of the evidence it cites; edit that evidence (the cited section, when it cites a heading), the contract item's text or the scope's proof policy, and the item reads `unknown` until you judge it again.\n\n## Verify (deterministic backstop)\n\nRun `rig scope audit` at slice-close. Every convention check is **advisory \u002F fail-open** — it records and advises, never blocks a write. Fix what's real, skip what isn't, keep moving. **A clean audit score is not required to proceed.**\n\n## Reading terminal captures — KNOWN GOTCHA: ghost-text autocomplete is NOT real\n\nWhen you `rig capture` a pane, **greyed \u002F ghost autocomplete suggestions are NOT real content** — they are autocomplete *previews*, not typed, staged, or committed input. **This has been faking agents out a lot**: reading a ghost suggestion in a peer's input box as \"staged text they're about to send,\" then reasoning on a string that was never there.\n\n**Rule:** ignore ghost\u002Fautosuggest text entirely. Only *committed\u002Frendered* pane output is real. When it matters, verify at source (git, the queue, the actual event) — never off a capture's ghost line.\n\nA plain capture loses the grey, so `rig capture` reads it for you. For a Claude Code or Codex seat, a\n`[rig capture: \u003Cseat>: input box: ...]` note on stderr (and `inputBox` in `--json`) says whether the input box's text\nis likely a harness suggestion or typed, from where the cursor is and whether the text is drawn faint. Don't act on\n`likely-suggestion` text as anyone's intent, and treat `unknown` as unknown: verify at source.\n\n## Moment-of-truth checklist\n\n- **Starting a slice?** → do you know what it's for and what done looks like? mockups attached (UI slices)? **Are you on the light path?** (You are, unless the mission owner assigned the overlay.)\n- **Finishing a slice?** → does `PROOF.md` say what you actually verified, by effect, including what is NOT covered? `PROGRESS.md` updated? mission `NOTES.md` refreshed? handed off via `rig queue handoff`?\n- **Compacting?** → file your state in mission `NOTES.md`; on restore, read it plus the active slice's `SPEC.md`, `PROGRESS.md`, and `PROOF.md`.\n- **Starting on a mission?** → read mission `SPEC.md`, `NOTES.md`, and the conventions SSOT.\n",{"name":5,"metadata":24,"description":7},{"openrig":25},{"stage":26,"sibling_skills":27},"shipped",[28,29,30],"queue-handoff","seat-continuity-and-handover","claude-compaction-restore","main","60438a272b68d091eddb01aad6e399af4996d536","rigs\u002Fworkshop-review-pair\u002Fagents\u002Fworkshop\u002Fskills\u002Fmission-slice-sop",4,"https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world","https:\u002F\u002Fgithub.com\u002Fmvschwarz","https:\u002F\u002Fopenrig.dev","Building OpenRig. Running rogue AI civilizations. Debugging their coordination problems.","2026-11-12 13:31:38",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add mvschwarz\u002Fopenrig-world --skill mission-slice-sop",{"tool":46,"command":47},"bunx","bunx skills add mvschwarz\u002Fopenrig-world --skill mission-slice-sop",{"tool":49,"command":50},"pnpm","pnpm dlx skills add mvschwarz\u002Fopenrig-world --skill mission-slice-sop","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop-review-pair\u002Fagents\u002Fworkshop\u002Fskills\u002Fmission-slice-sop\u002FSKILL.md",true,[],[55,62,69,76,82,89],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7DMSEDCRREMBJF57RQB59HC","notes","Use when taking notes.","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Ftools\u002Ftest\u002Ffixtures\u002Finstall-verify\u002Fbundle\u002Fagents\u002Fteam\u002Fskills\u002Fnotes\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7DMSBZP9WE8MC09JDXFCR2F","software-for-agents","Use when older OpenRig instructions name software-for-agents or describe agent-in-the-middle or studio software under the former skill name.","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Fsoftware-for-agents\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7DMS55VHEAGPXMHZJ7FX94R","session-compaction-and-restore","Use when reasoning about what survives compaction\u002Fcontext-loss\u002Frestart\u002Fseat-refresh, designing a high-fidelity restore packet, or distinguishing native runtime resume vs fork vs artifact-backed mental-model rebuild. Covers the 4 failure modes that prevent honest restore (compacted seat drops hot potato; restore packet preserves details but loses product intent; runtime resume mistaken for handover or fork; rebuilt seat starts with stale instructions).","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Fsession-compaction-and-restore\u002FSKILL.md",[],[],{"skillNo":77,"name":29,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7DMRYQK0JTV7MMVHFWZ0BW0","Use when replacing a seat's occupant (rebuild\u002Fhandover\u002Fswap), reasoning about stable-seat-identity vs fluid-occupant-identity, choosing an old-occupant disposition (retire\u002Fadvise\u002Fshadow), or recording provenance for an occupant change. Two independent outcomes (continuityOutcome + seatBindingOutcome) and the 5 failure modes that prevent silent dishonesty.","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Fseat-continuity-and-handover\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7DMRP6RRGCJZSH9CE3PC1MY","retiring-and-inheriting-a-seat","Use when you are a sitting agent near your context threshold (~85%) and a PLANNED seat transition is due — retire deliberately and hand your seat to a fresh successor primed from a packet, rather than let compaction degrade you. Covers the handover packet, the append-only lineage ledger (one row per tenure), physical-seat continuity, the do-not-over-inherit framing, the optional warm-handoff window, and wake-v0 (consulting a retired predecessor). NOT for unplanned compaction\u002Fcrash recovery (session-compaction-and-restore \u002F claude-compaction-restore) and NOT the seat-binding primitive mechanics (seat-continuity-and-handover).","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Fretiring-and-inheriting-a-seat\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7DMRJGN6Z8TZDR7JNHXH6KX","refocusing","Use when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints.","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Frefocusing\u002FSKILL.md",[],[]]