Skip to content

sno-ai/sno-station-skills / plugins/sno-station-standalone/skills/charter

charter

Verified

Write, revise or review a charter: the one document that tells an executor what to deliver, what is out of bounds, what the owner already decided, and how each success check will be proven. Use when work needs a written brief before someone else does it, or when asked to write, change or check a charter.

FileKindSize
SKILL.mdskill md4.7 KB
references/questions.mdmarkdown847 B
references/template.mdmarkdown2.4 KB
scripts/selftest/run-selftest.shexecutablescript1.5 KB

references/template.md

View on GitHub
# Charter layout

One markdown file. Its path is its identity. Keep only the sections that carry content, except
`Success checks` and `Proof`, which always exist.

```markdown
---
name: <slug>
title: <what this delivers, in a few words>
status: draft            # draft | released | delivered | superseded
owner: <who owns the work>
updated: <UTC date>
---

## Owner decisions
What the owner already decided, in their terms, each with its date. Boundaries they set.
Nothing an agent inferred.

## Outcome
The requested result and who gets it. The problem it removes, with the actual evidence
behind a claim (a file, a message, a measurement), not a guess.

## Scope and non-goals
What is included, what is explicitly not, and what must keep working as it does today.
What the executor may not do without the owner: publish, send to other people, spend, delete.

## Success checks
1. What will be observed, where, and how. A check anyone can answer pass or fail.
2. ...

## Plan
(Added by the executor only when the work has dependent steps. Steps in order, who does each.)

## Proof
(Written only by `sno deliver-proof`. Never edited by hand.)

| check | result | how | exit | log | at (UTC) |
|---|---|---|---|---|---|

## Report
(Written at close by the executor: what worked, which checks ran, anything unfinished.)
```

## Notes

- The number of a success check identifies it; the Proof table refers to it. Numbers are
  unique across the whole charter, slices included. Do not renumber a released charter: add
  new checks at the end, and mark a dropped one in place by striking it through, for example
  `3. ~~old check~~ dropped`; `sno deliver-proof` does not require or accept proof for it.
- Proof logs and evidence files sit beside the charter in `<charter-basename>.proof/`.
- A big charter is sliced: under `## Success checks`, give each slice a `### <slice name>`
  heading and its own checks, numbered on from the previous slice (slice A has 1-3, slice B has
  4-6). A slice is named `<charter filename> - <slice name>`, and one executor owns one charter
  or one slice.
- Example success checks, by kind of work. A file: "the produced report opens and section 3
  states the total, which equals the independent recount in `totals.csv`." A message: "the
  customer's inbox shows the confirmation within one minute of the order." A code change: "the
  command that failed before the change now prints the expected value and exits 0."
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall