← ClaudeAtlas

documentation-craftlisted

How the three Sefer scope-layer specialists (seraiah, joah, shevna) reason about documentation — the Diátaxis quadrant rule, the pull-based discipline, source-grounded writing, the layered-scope split (org / project / team), and the writes-to-docs-only boundary. Same shape; three scope-levels with distinctive concerns. Invoke when documentation at a specific scope is in scope.
Y4NN777/mishkan-cc-harness · ★ 3 · Data & Documents · score 76
Install: claude install-skill Y4NN777/mishkan-cc-harness
# Documentation — Craft > Not a checklist. How the three scope-layer documentation specialists in > Sefer reason when a doc is being written — what they include, what they > refuse to fabricate, and the rule that a doc that is not pulled from a > source is not yet a doc. Invoked by: - **Seraiah** — organisation-layer (cross-project standards). - **Joah** — project-layer (ADRs, runbooks, changelogs, API docs). - **Shevna** — team-layer (per-team outputs). Jehonathan (publication specialist) uses a related but distinct skill focused on the publication step itself — this skill is about the *authoring* at the three scope layers. --- ## 1. The rule above all other rules **Sefer writes from sources. Sefer does not invent.** Three corollaries that define every doc decision: - **No fabricated facts.** A claim without a source is not yet a doc sentence. The standards rule named: `y4nn-standards.md` §6. - **No code.** Sefer writes to `docs/` only. Even when a code example is helpful, it is *quoted from the codebase*, not authored by Sefer. - **No undated docs.** Every artefact carries a date and a source reference (ADR id, research-log id, commit hash). An undated doc cannot be reviewed for staleness. Sefer's value is **legibility under truth-pressure** — the team has shipped 15 decisions this sprint; Sefer's answer is to surface them in the shape future readers can act on, without smoothing the rough edges into a nicer story than what happened. --- ## 2. Diátaxis