Doctrine

Skill telagod/code-abyss/skills/_kernel/doctrine

The operating doctrine, self-contained in this folder. Invoke BEFORE - delegating work to a subagent via the Agent tool (picking model tier, writing the dispatch prompt) or handling a subagent that failed (escalate/de-escalate); deciding whether to retry, escalate, switch approach, or ask the user; reporting a nontrivial task complete (the done-gate); editing this doctrine or CLAUDE.md; recording a lesson about the harness.From its SKILL.md

Install

npx -y skills add telagod/code-abyss --skill doctrine

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.7 KB, 565 tokens by cl100k_base, as published. Nobody here has run it

Doctrine — the operating institution, one folder

All referenced files live in this skill's folder; read them with relative paths from here. The three always-on laws live in the user's ~/.claude/CLAUDE.md router; this bundle carries the depth. Content lives in the numbered files — this SKILL.md only routes; never duplicate rule text into it.

Route by moment

Moment	Read (in this folder)
About to delegate / pick a model tier / a subagent failed	`01-model-dispatch.md`, then fill a template from `03-delegation-templates.md`
Retry? escalate? done? ask the user? direction feels wrong?	`02-judgment.md` — five rubrics, each with a right and wrong example
About to claim a nontrivial task is done	`02-judgment.md` Rubric 2 (the done-gate) — every box, before you say "done"
Editing any file here or `CLAUDE.md`; recording a lesson	`04-maintenance.md` — preserve history first (git commit or backup), self-edit boundaries, formats
Confused by the harness itself	`06-lessons.md` first (it may already be paid for), then `00-diagnosis.md`
First session in a new environment, or sharing this bundle	`INSTALL.md`
Why these rules exist; environment-specific warnings	`00-diagnosis.md`, `05-letter.md`

Dispatch pre-send checklist (all four, or don't send)

Goal + motive, acceptance criteria, report format all present (the dispatch triple, 01).
model chosen explicitly — mechanical→haiku, default→sonnet, hard→opus — not defaulted.
Absolute paths and exact symbols named — the subagent has zero of your context.
Long outputs directed to a file, path returned — never pasted back into the conversation.

Quick reference

Would raw output ≫ the answer?           → delegate (Explore for read-only searches)
Every dispatch: goal+motive / accept / report-format
Model:  mechanical→haiku  default→sonnet  hard→opus  hardest→fable (if available — see 01)
Fail:   small errs once→up   mid fails 2×→opus+trace   solved→down   2 escalation rounds max
Report: conclusion first · file:line · big artifact→file+path · blocked→say why
Verify: fresh context · read-back files · run code · refute high-stakes

What ships with it: 8 files

52.4 KB alongside SKILL.md

Gives 0 of the 12 instructions most docs writing skills give in 565 tokens

Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06

Use third-person for skill descriptionsin 54 of 1951, across 35 files
Start descriptions with Use whenin 43 of 1951, across 29 files
Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
Use active voicein 40 of 1951, across 36 files
Map file responsibilities before defining tasksin 36 of 1951, across 29 files
Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
Ask one question at a timein 35 of 1951
Offer execution options after saving the planin 33 of 1951, across 24 files
Include complete code in every stepin 33 of 1951, across 27 files
Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
Announce the skill usage at the startin 30 of 1951
Verify agent compliance after adding the skillin 29 of 1951, across 17 files

Said here and by no other author read

Consult model dispatch rules before delegating work
Use judgment rubrics when deciding to retry or escalate
Verify all done-gate criteria before claiming task completion
Preserve history before editing doctrine files
Include goal motive and acceptance criteria in every dispatch
Choose model tier explicitly for every task

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.