What problem does it solve? Turning informal notes, meeting minutes, and tacit team knowledge into structured technical documentation is slow and inconsistent. This Skill classifies each documentation request into the right document type and applies a proven template, so runbooks, ADRs, process guides, and reference docs come out complete and uniform. ## Core Features & Use Cases - Document Type Router: Classifies each request as a Runbook, ADR, Process Guide, or Reference Document and applies the matching structure, audience, and level of detail. - Four Production Templates: Full templates for runbooks (with pre-flight checks, rollback, troubleshooting, escalation), ADRs (context, options, consequences), process guides (roles, workflow, SLAs, metrics), and system reference documents. - Source Integration: Pulls content from connected sources such as Confluence, SharePoint, or GitHub via MCP, from companyRAG collections, or from pasted chat input and uploaded files. - Use Case: After an incident review, paste your meeting notes and ask for a runbook for the recovery procedure — the Skill produces a step-by-step runbook with expected outputs, failure paths, and escalation contacts marked as placeholders where information is missing. ## Quick Start Ask the agent to write a runbook for restarting your production service based on the notes you paste into the chat.
