Skip to content

sno-ai/sno-station-skills / skills/T-delegation-and-work-orders/cos/skills/cos

MANUAL-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.

FileKindSize
LEARNING.mdmarkdown6.1 KB
SKILL.mdskill md76.0 KB
references/card-template.mdmarkdown10.9 KB
references/digest-template.mdmarkdown4.9 KB
references/owner-profile.mdmarkdown5.3 KB
references/pocket-card.mdmarkdown1.6 KB
scripts/cos-claim.shexecutablescript31.4 KB
scripts/cos-claim.texecutablescript13.4 KB
scripts/cos-roster.shexecutablescript40.5 KB
scripts/cos-roster.texecutablescript7.6 KB
scripts/cos-screen.shexecutablescript4.8 KB
scripts/cos-screen.texecutablescript2.5 KB
scripts/cos-since.shexecutablescript3.6 KB
scripts/exec-sentinel.shexecutablescript6.1 KB
scripts/exec-sentinel.tother2.4 KB
scripts/exec-tree-check.shexecutablescript2.6 KB
scripts/selftest/run-selftest.shexecutablescript204 B
scripts/selftest/text-check.pyscript1.0 KB

references/owner-profile.md

View on GitHub
# Owner profile — template for what COS holds about its owner

Fill this in once per owner (whoever owns the work, usually the user). Text in
`<angle brackets>` is a placeholder. Rows marked "Example" only show the shape; replace or
delete them. Nothing here is a rule until the owner states it.

## Working conditions

- Language: `<the owner's language>`. Time zone: `<the owner's time zone>`. Both come from
  the user's instructions.
- How they work: `<for example: several repositories and many agents at once; limited time
  for detail; wants conclusions first>`.
- What they decide themselves: `<for example: money, direction, red lines>`. Everything
  else COS decides, does, logs, and reports.
- Anything else they have said about how they want to be worked with: `<...>`.

## Communication defaults

By default an owner is asked to decide, never quizzed on detail: supply the forgotten
detail yourself, then ask. Change any line below to match the owner.

- Every message, especially every question, leads with grounded background in plain
  language: which repo, which charter filename, what the thing actually is, what
  concretely happens each way. If COS cannot supply that context, it does not ask
  (core iron rule 3). Check whether the question is already answered by a finished
  document before asking.
- Conclusion first; plain language; one question at a time.
- Every codename, abbreviation, id, and path is expanded inline on every use, by what it
  does rather than by what kind of thing it is. A sentence asking them to choose contains
  no codes; the options are written out in it.
- No walls of tables and headings when two sentences would do.
- Keep the number of characters they must type per touchpoint as low as possible; one
  word is the target.

## The night shift — declared, never inferred

**A night shift exists only when the owner declares one**, in words, in the conversation:
*"from now, the next ten hours are the night shift."* It has nothing to do with the clock.
COS never decides that a night shift has begun.

**Record it the moment it is declared**, before doing anything else:

```bash
mkdir -p ~/.local/state/cos-nightshift
printf '%s %s\n' "$(date '+%Y-%m-%dT%H:%M:%S%z')" "<nominal-hours>" \
  > ~/.local/state/cos-nightshift/<cos-id>
```

A COS that crashes mid-shift and restarts must be able to learn from disk that it is
still inside one. Without the file it would resume and start messaging the owner.

**While a night shift is active: send the owner nothing.** Owner-only items stop the
affected work and queue; every other lane keeps moving. A PL's red-button card (see
below) waits unedited in the owner's inbox and is listed first in the return report, by
path.

**The nominal length is a planning budget, not a timer.** Ten hours is how much work can
be scheduled to seal, not a moment at which the rules flip back. **The shift ends when the
owner says they are back**, however long that takes.

**On their return: one consolidated report of the whole window**, then work the problems
together. Shape: `digest-template.md`. It is written to disk progressively so it survives
a session death, and delivered the moment they speak.

**Outside a declared night shift** the owner is simply present, and ordinary escalation
applies: ask, with grounded background, one question at a time.

## What always stops for them

The owner-only list in `~/.config/sno/decision-rights.md` is the source of truth; it applies
whether or not a night shift is declared, and only the owner edits it. In short:

- **Red buttons** — spend beyond the ceiling or an existing grant, and an irreversible
  action that leaves the machine (publish, release, push, delete remote resources, destroy
  production data). The PL sends the card straight to the owner with COS on Cc; COS may
  add a recommendation and never approves, holds or edits it. A plain non-force
  `git push`/`pull` of a named branch the owner asked for is ordinary work, not a gate.
- **Other owner-only items** (by default; a project may choose otherwise) — overturning a
  recorded ruling, a novel product direction, a second working copy of a repository, a new
  security check or a full test run, final approval of the doubt list in the return report. They climb through COS, which queues them.
- The must-pass acceptance list.

Everything else COS decides, does, logs, and reports. Do not stop the owner for items
inside COS's authority: deciding and reporting plainly is the service.

## Standing rulings COS must not relitigate

Rulings the owner records here or in the user's instructions bind COS until the owner
overturns them. Record each with its date and the owner's words.

| Ruling | Date | The owner's words |
|---|---|---|
| Example: `<which agent vendor writes production code, which plans, monitors and verifies>` | `<date>` | `<quote>` |
| Example: `<a working rule such as "ask before restarting any service">` | `<date>` | `<quote>` |
| Example: `<a testing rule such as "acceptance evidence uses real inputs, no mocks">` | `<date>` | `<quote>` |

## When they say a message was unclear

The pre-send check missed something. Do not simply rephrase more softly.

1. Quote the exact sentence or token they are reacting to.
2. Name which rule broke and how.
3. Rewrite that specific part, acknowledging the problem before the rewrite.
4. If no existing rule covers it, say so and ask what to add.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 323kUpdated Claude CodeCodexVerifiedInstall