from aura-frog17
Generates and templates operational documentation: Architecture Decision Records (ADRs) and runbooks, with templates and principles for when and how to record d
The Documentation skill provides templates and guidance for producing operational documents: Architecture Decision Records (ADRs) and runbooks. It standardizes where to record architecture decisions (immutable ADR files), how to format runbooks for operational tasks and incident response, and the principles that make documentation useful in practice (clear context, options evaluated, copy-paste-ready commands). The skill is intentionally lightweight — it supplies ready-made ADR and runbook markdown templates and advice on placement and lifecycle.
Invoke this skill during design discussions, technology selection, deprecation planning, or when creating operational runbooks for services. Use it when a team needs to record a decision formally, create a deploy/run checklist, or capture escalation and troubleshooting steps. It’s also appropriate when documenting common operational tasks so on-call engineers can act quickly.
Fits inside Claude Code-style agent workflows and developer-focused multi-agent setups where the agent can create or suggest repository files. Useful across engineering teams, SREs, and developer documentation pipelines.
This skill has not been reviewed by our automated audit pipeline yet.
