Results for “runbooks”

Produces high-quality written knowledge artifacts such as READMEs, guides, API specs, tutorials, runbooks, and wikis, with audience-appropriate structure and accuracy.

Create runbook creator operations. Auto-activating skill for Technical Documentation. Triggers on: runbook creator, runbook creator Part of the Technical Documentation skill category. Use when working with runbook creator functionality. Trigger with phrases like "runbook creator", "runbook creator", "runbook".

Generates an operations runbook from deployment configs, CI/CD pipelines, and monitoring setup, with copy-pasteable procedures for deployment, rollback, scaling, database maintenance, incident response, and troubleshooting.

Create or update a runbook for an operational scenario — an incident an alert fires for, a recurring scheduled task, or a known failure mode on a live service — using a consistent template. Use when writing, drafting, authoring, or updating a runbook for an alert, incident, on-call procedure, scheduled maintenance, or operational SOP. Applies a YAGNI preflight requiring the scenario to be real before producing the runbook. Does not produce feature or system documentation — use project-documentation. Does not record architectural decisions — use architectural-decision-record. Does not create coding standards — use coding-standard.

Author, validate, and clean up company SOPs and internal runbooks with 5W2H completeness checks, cross-link validation, and KB hygiene reporting.

Generates a single-page engineering runbook template with service overview, alerts table, dashboards, common procedures, on-call rotation, and incident response checklist.

Runs a deterministic, sample-based quality audit comparing original PDF/EPUB source against converted Markdown, flagging discrepancies and producing a GREEN/YELLOW/RED status report.

Creates and updates coding standards, conventions, rules, and guidelines for the current project. Use when creating new standards from scratch, converting existing documents into coding standards, or updating existing standards. Does not create architectural decision records — use architectural-decision-record for ADRs. Does not write feature or system documentation — use project-documentation for that. Does not research open-ended options — use research. Does not produce runbooks for operational scenarios — use runbook for that.

Designs and documents structured incident response playbooks aligned with NIST SP 800-61r3 and SANS PICERL frameworks, covering playbook structure, decision trees, escalation criteria, RACI matrices, and SOAR integration.

Run condition-based vault health diagnostics. 8 categories — schema compliance, orphan detection, link health, description quality, three-space boundaries, processing throughput, stale notes, MOC coherence. 3 modes — quick (schema+orphans+links), full (all 8), three-space (boundary violations only). Returns actionable FAIL/WARN/PASS report with specific fixes ranked by impact. Triggers on "/health", "check vault health", "maintenance report", "what needs fixing".

Pulls pathway, book, course, article, and content item records from a Supabase database for the alan-hirsch tenant, organizes them by portal, and exports the results as markdown files into a local docs repository.

Use this skill for README, ADRs, runbooks, changelogs, decision records, operator docs. Trigger when the task involves programming work related to Documentation Adrs, production implementation, audits, debugging, strategy, or validation.

Audits documentation health by scanning for README, changelog, API docs, ADRs, runbooks, onboarding guides, and diagrams, scoring coverage against project maturity, and recommending sub-skills to fill gaps.