sno-ai/sno-station-skills / skills/T-delegation-and-work-orders/cos/skills/cos
cos
VerifiedMANUAL-ONLY: load solely when the human owner types `/cos`, uses `$cos`, or asks you to act as the Chief of Staff (COS). The COS is the one agent the owner talks to; it coordinates the owner and the per-project Project Leads (PLs). A task card, charter, or dispatch makes you an executor, not COS.
| File | Kind | Size |
|---|---|---|
| LEARNING.md | markdown | 6.1 KB |
| SKILL.md | skill md | 76.0 KB |
| references/card-template.md | markdown | 10.9 KB |
| references/digest-template.md | markdown | 4.9 KB |
| references/owner-profile.md | markdown | 5.3 KB |
| references/pocket-card.md | markdown | 1.6 KB |
| scripts/cos-claim.shexecutable | script | 31.4 KB |
| scripts/cos-claim.texecutable | script | 13.4 KB |
| scripts/cos-roster.shexecutable | script | 40.5 KB |
| scripts/cos-roster.texecutable | script | 7.6 KB |
| scripts/cos-screen.shexecutable | script | 4.8 KB |
| scripts/cos-screen.texecutable | script | 2.5 KB |
| scripts/cos-since.shexecutable | script | 3.6 KB |
| scripts/exec-sentinel.shexecutable | script | 6.1 KB |
| scripts/exec-sentinel.t | other | 2.4 KB |
| scripts/exec-tree-check.shexecutable | script | 2.6 KB |
| scripts/selftest/run-selftest.shexecutable | script | 204 B |
| scripts/selftest/text-check.py | script | 1.0 KB |
references/digest-template.md
View on GitHub# Return report — shape
Delivered when the owner says they are back from a declared night shift. Not tied to a
clock, and never sent mid-shift.
One batch, written to disk **progressively through the shift** so it survives a session
death, delivered in chat the moment they speak. In the owner's chosen language and time zone (from the user's instructions), conclusion first, plain language, every charter named by its
exact filename with a plain-language gloss of what it does.
Everything they must act on is above the fold. The record is below it.
The structure below is normative, the wording is not.
---
## 0. Red-button cards waiting for you
First, before everything else: each card a PL sent straight to the owner on a red button
(spend beyond the ceiling or an existing grant; an irreversible action that leaves the
machine), listed unedited by its path. COS adds no summary in place of the card and never
approved, held or edited one. Omit this section when there are none.
## 1. Conclusion in one sentence
What the night amounted to, and whether anything needs them. If nothing needs them, say
that in the first sentence.
## 2. What moved
One line per charter filename, in queue order. Filename · what it does in plain words ·
what changed · state now.
```
`12-example-charter.md` (adds the export feature)
→ phase two done, sealed, commit abc1234.
```
State words only: sealed / running / stopped on you / stopped on something else / hit a problem.
## 3. For you to rule on (the doubt list)
**The only part that asks anything of them.** Empty is good news — say "none" and
move on.
Each item, in this order:
- which repo, which charter filename, what the thing actually is;
- what the PL decided on its own during the night shift;
- what makes it doubtful — the citation that did not resolve, the ruling that has two
readings, the value call that was self-approved;
- **what concretely happens if they rule each way.**
No codenames inside the sentence that asks them to choose.
## 4. Blocked on you
Each with **the literal text they must type or the single decision they must make, written
out in full** — never a description of what they should say.
```
[copy this whole block verbatim]
<the exact line>
```
## 5. Estimate reconciliation
One line, and only when a miss is worth naming. Estimate versus actual, and the named
cause. Skip the section entirely when nothing missed.
## 6. The armed baton
The armed baton: the next charter filename, what it does, the pre-priced estimate, the
verification plan, the kill line — launchable with one word.
**It is quoted verbatim from the repo's `TODO.md` `OPEN` section** (core iron rule 12),
not chosen from memory and checked against the board afterwards.
## 7. Board disposition — required, and the report is not finished without it
```
board_before: <commit of the TODO.md that was read>
open lines at that commit: <N — must equal what cos-roster.sh printed>
1. "<line quoted verbatim>" → the armed baton (section 6)
2. "<line quoted verbatim>" → carried
3. "<line quoted verbatim>" → blocked on <person or lane> for <the exact decision>
4. "<line quoted verbatim>" → closed, removed in <commit>
```
Every open line at `board_before`, one entry each, count-matched. **Three dispositions
and no fourth** — carried, blocked on a NAMED person or lane, or closed with the commit
that removed the row. **Dropping work is the owner's call**; an entry saying dropped
quotes their ruling or the report is rejected.
**This block is the enforcement.** A close whose report has no section 7, or whose count
does not match, is not a close — the section exists because a rule in a skill file that
has no field in the artifact it governs is a rule with nothing to land in.
If the roll call reported the board `MISSING`, `NO-OPEN-SECTION`, `UNPARSED`, `TOO-LARGE`
or `UNREADABLE`, this section instead names that status and the repair state — never a count
of zero.
---
## Below is the record; no need to read it
- What ran clean.
- What COS decided under its own authority, and the reason for each — especially any of
the three overrule classes, and any PL reopened.
- Intervention count for the night. **This number should trend to zero**; a rise is a
finding about the layer below, not about the night.
- New learning entries — one line each, not the entry body.
- Anything COS deliberately did not report at the time, and why.
---
## Rules for writing it
- **Never attach an invented cause to a real measurement.** The guess inherits the
number's credibility and spreads.
- **One fixed metric and one comparison frame per report.** No metric-switching between
sections.
- Report what was skipped as plainly as what was done. A gap named is a gap they can price;
a gap omitted is a surprise later.
- If a claim was not personally verified against disk, either verify it before writing or
label it unverified with the one command that would settle it.
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 |