mvschwarz/openrig / packages/daemon/assets/plugins/openrig-core/skills/openrig-operating-model
openrig-operating-model
VerifiedUse when you do not know WHERE something belongs: you learned a lesson and are unsure which file takes it; you are about to create a new doc, folder, or convention; you are asking "should this be a skill, a note, or a chain file?"; you inherited a seat and want to know what SHOULD exist; or you are about to duplicate knowledge that already has a home. Also the trace-to-root: how a seat orients by reading one filename at each level from where it stands up to the fleet.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 24.4 KB |
| scripts/compose.pyexecutable | script | 28.7 KB |
| scripts/scaffold.shexecutable | script | 2.1 KB |
| scripts/trace-due.shexecutable | script | 1.5 KB |
| scripts/trace-stamp.shexecutable | script | 231 B |
| scripts/trunk-diff.shexecutable | script | 966 B |
| templates/LEARNED.md | markdown | 1.6 KB |
| templates/NOTES.md | markdown | 370 B |
| templates/PLAYBOOK.md | markdown | 184 B |
| templates/SOP.md | markdown | 676 B |
| templates/SPEC.md | markdown | 2.5 KB |
templates/SPEC.md
View on GitHub---
node: <project | mission | slice>
intent: >-
<ONE sentence: what this node is FOR. This composes UP the chain, so write it to be
read from below by someone standing on a slice. Say the purpose, never the location —
"deferred features land here" is a routing rule and orients nobody.>
id: <OPR.x.y[.n] — minted by the PM; omit if unminted>
stage: wip
# stage: wip | provisional | established | canonical | superseded | retired
status: UNSEEDED
---
<!-- ONE authored file per work node. README.md and IMPLEMENTATION-PRD.md fold into this.
PROOF.md stays separate and is good. PROGRESS.md is the authored acceptance checklist:
checkbox items are stored marks; every roll-up above them is derived, never hand-authored.
Legacy README.md nodes stay valid indefinitely; nothing is forced to migrate.
PROJECT nodes carry stable intent. MISSION nodes carry intent and proportional
mission-level specification in this same authored file, organizing slices and
giving them shared scope. SLICE nodes carry concrete implementation scope.
Keep body depth proportional; do not repeat all slice details at mission level.
WHATEVER BODY YOU DO WRITE, two tests per sentence:
PORTABILITY — if it would read correctly on a stranger's machine it is knowledge
about a KIND; it belongs in the operating-model skill, not on the tree.
VOLATILITY — a SHA, a count, a status, a roster: write the COMMAND that derives it,
never the answer. A value here is stale by the next fold.
And check the tree: traps and how-we-work live in LEARNED.md on the topology tree,
not here. This file is what is being BUILT.
Follow the selected mission-slice-sop and any explicit operating-mode overlay.
Use the required sections for that work; the generic body below is a starting
shape, not an additional gate or a requirement for every mission. -->
# <name>
## What must be built
<!-- The change itself, at the altitude a builder can act on. -->
## Why this is the shape
<!-- The reasoning a reader would otherwise have to reconstruct — especially any option
considered and rejected. This is the part that survives you. -->
## How we will know it works
<!-- Verified by EFFECT: run it, look at the result. Name the command and what it should
print, not the feeling of being done. -->
## Scope fences
<!-- What this deliberately does NOT include, so it neither swallows the release nor grows
during the build. Fences written after the fact are excuses; written now they hold. -->
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: 463k | Updated | Claude CodeCodex | Verified | 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: 463k | Updated | Claude CodeCodex | Verified | Install |
| discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.). | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |