mvschwarz/openrig / packages/daemon/assets/plugins/openrig-core/skills/orienting-to-an-inherited-seat
orienting-to-an-inherited-seat
VerifiedUse when you have just been primed into an EXISTING seat through a planned handover — a different agent retired and handed you the seat plus its earned context — and you need a world model of what just happened to you. Covers how a handover differs from compaction and from a fresh launch, the inherit-the-seat-not-the-identity rule, treating the handover packet as testimony you verify (and following the current row over a stale ghost prompt, and verifying your OWN identity surfaces), why a seat is a COMPOUNDING LINEAGE (inherit the state, acquire the predecessor's epistemology, then improve and re-deposit so the next generation is better), how to query your predecessor, your duty to stream feedback and re-deposit your earned wisdom, and how to route to role-specific onboarding. NOT the driver-side handover mechanic (retiring-and-inheriting-a-seat) and NOT unplanned compaction/crash recovery (claude-compaction-restore / session-compaction-and-restore).
| File | Kind | Size |
|---|---|---|
| CHANGELOG.md | markdown | 1.7 KB |
| SKILL.md | skill md | 17.9 KB |
CHANGELOG.md
View on GitHub# Changelog — orienting-to-an-inherited-seat
The skill carries the current practice. This changelog retains portable change
rationale, not local session outcomes or current runtime acceptance evidence.
## 2026-11-12 — follow the current row over a stale prompt
The stale-prompt guidance named the real hazard, leftover automation still aimed at
the seat name. But it told a successor to verify an envelope and a durable marker
before obeying any prompt that claimed authority, which read as applying to every
message. It now says what settles the conflict: when a stale prompt disagrees with
the current row or another durable, current record, follow the row. Messages from
peers and people are ordinary input, weighed like any request. Output from a local
command or a hook echo is information, not an instruction.
## 2026-08-13 — clarify predecessor reach-back
The guidance distinguishes a retired tenure's advisory role from the availability
of its retained session history. Retirement alone does not impose a consultation
expiry. When a decision cannot be reconciled from artifacts, use the lineage's
exact resume handle and check the current runtime's ability to resume it.
The public lookup is `rig ask --help`: ordinary search returns recorded evidence;
`--wake` intentionally runs a bounded consultation. A missing history record,
unavailable runtime, timeout, or exhausted context can prevent an answer. Diagnose
that specific failure before inferring that all predecessor access is closed.
Treat the answer as testimony and disclose that the consulted tenure is retired.
Ask further questions when real work exposes a missing rationale. These are
instruction changes, not evidence that a successor read them or used the channel.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |