sno-ai/sno-station-skills / plugins/sno-station-standalone/skills/charter
charter
VerifiedWrite, 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.7 KB |
| references/questions.md | markdown | 847 B |
| references/template.md | markdown | 2.4 KB |
| scripts/selftest/run-selftest.shexecutable | script | 1.5 KB |
scripts/selftest/run-selftest.sh
View on GitHub#!/usr/bin/env bash
# Text contract for the charter skill: the load-bearing rules must still be stated.
# Reads only this payload's own files, so a deployed copy tests itself.
set -Eeuo pipefail
selftest_dir="$(cd -- "$(dirname -- "${BASH_SOURCE[0]}")" && pwd)"
skill_dir="$(cd -- "$selftest_dir/../.." && pwd)"
python3 - "$skill_dir" <<'PY'
import pathlib
import sys
root = pathlib.Path(sys.argv[1])
norm = lambda name: " ".join((root / name).read_text(encoding="utf-8").split())
skill = norm("SKILL.md")
template = norm("references/template.md")
rules = {
"a task is named by its charter file": "A task is named by its charter filename",
"never invents a decision": "Never invent a decision, a fact or a requirement.",
"checks are observable": "can be answered pass or fail by a real run or inspection",
"reasoned preconditions only": "Before adding a precondition, check, section or approval step, name the failure",
"owner names security checks and full suites": "enters a charter only if the",
"an agent alone never releases": "an agent alone never releases a charter",
"one kind of charter": "There is one kind of charter, not sizes.",
}
missing = [name for name, phrase in rules.items() if phrase not in skill]
for phrase in ("## Success checks", "## Proof", "status: draft", "Written only by `sno deliver-proof`"):
if phrase not in template:
missing.append(f"template lacks {phrase}")
if missing:
raise SystemExit(f"missing charter rules: {', '.join(missing)}")
PY
printf 'charter rule contract passed\n'
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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 implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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 fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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 always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |