What problem does it solve? Engineering teams produce inconsistent, scattered, or missing documentation — decisions get lost, runbooks fail at 3am, and onboarding takes weeks. This Skill provides one opinionated standard for every kind of doc that ships in a repo, so any engineer (human or AI) can find why decisions were made, how the system fits together, and what to do when alerts fire. ## Core Features & Use Cases - Complete doc taxonomy: Covers Diataxis quadrants (tutorials, how-tos, reference, explanation), ADRs for decisions made, RFCs for decisions in flight, C4 architecture diagrams (Context, Container, Component), runbooks, blameless postmortems, changelogs, READMEs, and onboarding docs. - Repo bootstrapping: Provides a canonical docs/ directory layout plus ready-to-copy Markdown templates for ADRs, RFCs, plans, C4 diagrams, runbooks, postmortems, changelogs, READMEs, and onboarding. - Review checklist and anti-patterns: Includes a PR review checklist for docs and explicit anti-patterns (e.g., mixed Diataxis quadrants, mutable ADRs, blameful postmortems). - Use Case: A team starting a new service uses the Skill to scaffold docs/ with a C4 context diagram, an ADR index, a changelog, and an onboarding guide — then later writes a blameless postmortem and runbook after their first sev2 incident. ## Quick Start Ask the AI to bootstrap the MIS documentation structure in your repository, including the docs folder layout, an ADR template, and a changelog.
