Results for “runbooks”

Mantém a documentação técnica viva no Notion e no repositório, gerando runbooks, inventários, ADRs e procedimentos a partir da infraestrutura real.

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

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

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.

Classify AEM 6.5 LTS and AMS workflow issues by symptom, gather relevant logs and metrics, and map to runbooks or Splunk searches.

Runbook Generator

Runbook Generator

Write an operational runbook any qualified operator can execute under pressure, with verification, failure paths, and escalation.

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.

Turn a workflow that lives in your head into a runbook anyone can execute. Capture the 5W2H of a repeated process, who, what, when, where, why, how, and how much, name the failure points, and add the checks that prove each step worked, so the task no longer depends on you being available. Trigger on "write a runbook for this", "document this process", "make this an SOP", "turn this into steps", "how do we run X", or any workflow you have now done enough times to hand off.

A runbook written in a wiki decays silently: the dashboard is renamed, the

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.

Translate an approved experiment spec into a launch runbook — platform binding (PostHog primary), feature flag setup, assignment unit, exposure event definition, instrumentation QA, dashboard wiring, ramp plan, monitoring, and rollback procedure. Platform-agnostic core with one strong PostHog adapter shipped; GrowthBook, Statsig, LaunchDarkly, Optimizely, and Eppo documented as a single mapping table the user adapts. Load when a spec is approved and ready to launch, or when the user says "set up the experiment", "wire this up in PostHog", "implement the test", "create the runbook", "launch checklist for this test", or when the experimentation orchestrator routes here.

Provides structured guidance for running operations across engineering, business, and organizational contexts, including incident management, deployment checklists, rollback procedures, change management, meeting design, and operational rituals.

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

Manage businesses, projects, time tracking, and budgets in FreshBooks cloud accounting via automated API calls.

Plan structured workshops with goals, agenda, activities, prompts, decision rules, and follow-ups.

runtime-and-process

Deployment runbook for IntelliVerse Kubernetes services. Use when deploying a new service, updating an existing deployment, rolling back, applying manifests, updating images, scaling, or managing namespaces in the aicart cluster.

Runs a complete quality engineering audit on any codebase, deriving behavioral requirements, generating spec-traced tests, performing multi-pass code review, and producing a consolidated bug report with verified patches.

Plans, executes, and validates Google Kubernetes Engine (GKE) cluster upgrades and maintenance operations for both Standard and Autopilot clusters, producing upgrade plans, checklists, and runbooks with gcloud commands.

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.

Financial runway & unit economics tracker — burn rate, revenue trajectory, runway in months, scenario modeling

Upserts a validated MDX book corpus into Supabase via Drizzle, hydrating books, chapters, sections, and chunks tables while preserving stable bookmark anchors and only re-embedding changed content.

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.

Coaches runners with training plans, pace calculations, race strategies, and form analysis

Programmatically author RoadRunner scenarios from MATLAB using roadrunnerAPI. Use when adding actors, creating routes, building scenario logic (phases, conditions, actions), placing vehicles/pedestrians, defining cut-in/crossing/ follow scenarios, or any programmatic scenario creation in RoadRunner. Triggers on: roadrunnerAPI, scenario authoring, add actor, create route, phase logic, cut-in scenario, pedestrian crossing, scenario from MATLAB.

Manage R&D program budgets with F&A splits, track burn rate and runway against milestones, and route capitalize-vs-expense decisions to a named finance owner.