documentation-discipline

What problem does it solve?

Teams often struggle to know when to document decisions or procedures versus leaving knowledge in chat, leading to either lost tribal knowledge or an unsustainable docs burden. This Skill helps decide what to write, which artifact to use, and how to maintain it so documentation is useful, discoverable, and durable.

Core Features & Use Cases

• Decision tree for artifact selection: Step-by-step questions that determine whether to write an ADR, runbook, decision doc, one-pager, or leave the answer in chat.
• Templates and rules: ADR template, runbook structure with required expected results and rollback, decision log format, and one-pager guidance to standardize outputs.
• Governance guidance: Rules for numbering ADRs, immutability, storage locations, ownership, review cadences, and anti-patterns to avoid documentation rot.
• Use Case: During an incident, use the Skill to decide if a runbook is required, produce a runbook scaffold with verification steps and rollback, and assign an owner and review date.

Quick Start

Decide whether to write an ADR, runbook, decision doc, or one-pager and return the recommended artifact type, a template scaffold, an owner placeholder, and a next-review date.