agentleFS
Sign inStart free
modeled-information-formatmodeled-information-format/mif-docs-plugin/skills/playbook/SKILL.md

playbook

Skill1 starsChanged 34 days agoMITView on GitHub

Write a strategic operational playbook that coordinates a CLASS of situations (e.g. a Sev1 outage) across roles, decision points, and phases. Use for higher-altitude incident/operations coordination. Anti-trigger; for fixing one specific alert step-by-step use sre-runbook (tactical), not a playbook.

15 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Create a free account to mount
Files
SKILL.md

playbook

Produces a playbook: strategic coordination for a class of situations. Where a runbook is tactical (fix one specific alert), a playbook answers who does what, when, and how we decide across a whole scenario class.

Pattern

  1. Scenario & Scope — the trigger class this playbook governs and what's out of scope.
  2. Roles & Responsibilities — Incident Commander, Communications Lead, Operations/Subject experts; who holds each and their authority.
  3. Decision Framework — severity levels, declare/escalate criteria, when to page leadership, when to involve external comms.
  4. Phases — Detect -> Triage -> Respond -> Recover -> Review, with the goal and exit criteria of each.
  5. Communications Plan — internal channels + external/status-page cadence.
  6. Post-Incident Review — how the retro is run and what it produces.

Playbook vs runbook

A playbook is strategic and role/decision-centric; it references the tactical runbooks that handle specific alerts. If your document is a single ordered list of commands to fix one symptom, it's a runbook, not a playbook.

MIF frontmatter

type: procedural. Climb to L2 with namespace, tags, title. Gate with mif-validate --level 1. See templates/good.md and templates/bad.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free