agentleFS
all-source-osall-source-os/all-source/.claude/skills/ritual-full/SKILL.md

ritual-full

Skill4 starsChanged yesterdayApache-2.0View on GitHub

The ritual flow (Think, Spec, Plan, Build, Review, Ship, Reflect on a Chronis epic) with every tool on by default: EGM for brainstorm, draft, review and drift; a Semantic ISA section in every design; two independent fresh-context reviewers; cos hires per step; graphify context; claude-guard hooks. Runs a tool preflight first and stops on anything missing. Triggers on: ritual full, full ritual, full flow, plan this feature with every tool, ritual with egm, ritual with semantic isa.

  • Installs packages

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run each check, print one table, then stop if any row is missing:

    line 17
  2. Very specific:

    Every design gets a ## Semantic ISA section, written with semantic-isa's DESIGN mode (SKILL.md, template) and scaled to the change:

    line 48
  3. Distinctive:

    Side-effect inventory: every file write, network call, API, message, deploy and data write the change adds or touches.

    line 52
  4. Distinctive:

    VERIFY changed, goes in the report's Drift section and in the design, in the same change.

    line 86

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

ritual-full

The same flow as ritual: same steps, same files, same ritual-* lines on the epic, same gates. Read that skill first; this one states only what changes. Every tool below is on by default. A missing tool blocks the flow until it is installed or the user says "continue without <tool>"; never skip one silently. Zero to hero, with install and a worked example: docs/ritual-zero-to-hero.md.

Preflight (first thing, every flow)

Run each check, print one table, then stop if any row is missing:

ToolCheckInstall when missing
Chronis cncn --help exits 0; .chronis/ in the main checkoutcargo install chronis, then cn init in the repo
EGM pluginclaude plugin list shows egm@egm enabledclaude plugin marketplace add google/elephant-goldfish-model then claude plugin install egm@egm, new session
semantic-isa~/.claude/skills/semantic-isa/SKILL.md existscp -R skills/semantic-isa ~/.claude/skills/semantic-isa from this repo
coscos ritual check --help exits 0clone decebal/chief-of-staff-v2, run task setup in it
graphifygraphify --help exits 0; graphify-out/ in the repo, else build ituv tool install graphifyy then graphify install
claude-guardclaude-guard --help exits 0; ~/.claude/settings.json registers claude-guard infra-guard and claude-guard bash-hygienecargo install --path gates/rust/claude-guard, then skillsync hooks install
skillsbrainstorming, pr-proof, systematic-debugging under ~/.claude/skills/cp -R skills/<name> ~/.claude/skills/<name>

Report: preflight: cn ok · egm ok · semantic-isa ok · cos ok · graphify ok · claude-guard ok · skills ok, with missing (<install command>) in place of ok where it applies. EGM skills set disable-model-invocation: true, so for every /egm: step below you give the user the exact command and wait for its output file.

What is on, per step

StepOn by defaultHands over (in addition to ritual's)
Thinkuser runs /egm:egm-brainstorm; graphify query on the modules the idea touchesconcepts_brief.md moved to the dated brief path; graph nodes cited
Specuser runs /egm:egm-draft; a Semantic ISA section; review by /egm:egm-review and a hired ritual-goldfish; resolve with /egm:egm-resolve or /egm:egm-review-loop; cos ritual checkdesign with ISA section; two review files
Planone bead per ISA sink whose done-when is its VERIFY test; graph read back (graph.md)plan with the ISA test matrix as trophy rows
Buildcos agents spawn --role builder per ready bead, own worktree; claude-guard hooks onISA matrix rows as real tests
Reviewcos agents spawn --role reviewer; sink-to-VERIFY checkcode review naming each sink's VERIFY at file:line
Shippr-proof evidence; one PR, one commit (ship.md)the evidence report
Reflectuser runs /egm:egm-drift-report on the design; new-sink checkreport under docs/reports/

Spec: the Semantic ISA section

Every design gets a ## Semantic ISA section, written with semantic-isa's DESIGN mode (SKILL.md, template) and scaled to the change:

  1. Side-effect inventory: every file write, network call, API, message, deploy and data write the change adds or touches. One row each, with reversibility.
  2. Instructions in the five cores, each with a governance property and a typed binding (closed input_schema and output_schema).
  3. Taint: sources (user input, fetched content, file reads, model output) and sinks.
  4. VERIFY before every sink: a stated, deterministic check. "The model judged it safe" is not one.
  5. Violations as recoverable exceptions: evidence recorded and the recovery path.
  6. ISA test matrix: per sink, tainted input refused and VERIFY-cleared input admitted.

A change with no side effects says so in one line with the evidence (no file, network, API, message, deploy or data write: <the diff's scope>). The Goldfish reviewers check this section like any other; an inventory that misses a side effect visible in the code is a blocking finding.

Spec: two reviewers, one approval

The two reviews run in separate fresh contexts and never see each other's output. Write each as its own review file (format in spec.md). Approval needs both clean against the same design digest; point cos ritual approve --review at the later one and name the other in the design's review history. Resolve findings, then re-run both. The approval is the user's: cos ritual approve in their terminal, or, when they tell you to approve in the conversation, the same command with --yes and their instruction quoted in your report (spec.md). Agents never approve on their own initiative.

Review: sink-to-VERIFY check

For each sink in the design's ISA table, the reviewer finds the VERIFY in code and its test: rg -n '<sink call>' lists every call site, and each one is reached only through the named check. A sink with no VERIFY, or a call site that bypasses it, is a blocking finding. A sink in the code that the design does not list is drift: back to Spec.

Reflect: new sinks

Diff the shipped code's side effects against the design's inventory. A new sink, or one whose VERIFY changed, goes in the report's Drift section and in the design, in the same change.

Everything else

Finding the step, the ritual-* lines, where the epic and files live, the gates, bugs skipping Think and Spec, and per-org notes (repo-notes.md) are as in ritual.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.