When to Use

Layers on top of document-standards specifically for: runbooks, incident postmortems, ADRs, README files (technical or project-specific), on-call handoff notes, change-management docs, SOPs, and similar standalone technical documents aimed at readers who are senior network admins, DevOps engineers, or DevSecOps engineers, often people delegating work to juniors or evaluating documentation quality.

This skill assumes document-standards is already active. It adds document-type presets and audience framing on top of that base. It does not restate the FORMALITY/DENSITY/AUDIENCE_LEVEL dial mechanism, the Content Read step, the pre-flight checklist, the scoring rubric, or the anti-slop references, all of which live in document-standards and apply here unchanged.

Preset priority: when a document could plausibly match a preset in both this file and document-standards, this file's preset wins whenever its trigger conditions (audience, document type) are met, since it represents the more specific match. document-standards' own presets are the fallback for everything else.

Making a new skill is covered by skill-creation, and deciding whether a need justifies one, or locating an existing skill, by skill-discovery.

Document-Type Presets

Vibe-Word to Dial Mapping (Technical)

Templates

references/templates/: technical document-type templates (runbook, ADR, postmortem, and so on), populated iteratively as real documents get produced. Empty at initial build. Apply document-standards' Three-Tier Threshold Framework independently once this folder grows toward the same limits.