Results for “runbooks”

Generate operational runbooks from a service name — deployment, incident response, maintenance, and rollback workflows. Templated structure customizable per environment.

Runbook Generator

Runbook Generator

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

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

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.

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

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

runtime-and-process

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.

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.

Automate QuickBooks Online operations including creating invoices, managing customers, querying accounts, and listing invoices for financial reporting.

Runbook skill for failures: cron error, PA failure, cascade, gateway disconnect, semantic DB stale. Walks: detect → classify → diagnose → notify → log. Replaces ad-hoc failure handling. Triggers: "cron failed", "X is broken", "cascade", "incident", "gateway down", "PA failure".

Execute Databricks Notebooks / Jobs

AI CFO briefings from QuickBooks exports, burn/runway, scenario modeling, and build-cost estimates. Use for CFO briefing, runway analysis, or development cost estimates.

Build lean, opinionated products using the 37signals philosophy from Getting Real, Rework, and Shape Up. Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", or "opinionated software". Also trigger when cutting scope to ship faster, running small teams, avoiding long-term roadmaps, or eliminating meetings. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.

Mounts a fetch-native CopilotRuntime on any JS server, wires middleware, selects an AgentRunner, and integrates built-in or external agent frameworks.

Designs chaos experiments, creates failure injection frameworks, and facilitates game day exercises for distributed systems — producing runbooks, experiment manifests, rollback procedures, and post-mortem templates.