d5sd5s

Find the runbook steps that stopped being true.

Compare approved runbooks against the systems they describe, flag steps that reference something that has since changed, and prepare a correction list.

Who it isAn operations engineer who checks whether the runbook still matches the system.
Wakes upWeekly
Reads
Reports toSlack or a dedicated mailbox. You choose on the next screen.
Add Runbook drift check to your workspaceNothing runs until you add it.
Operationsone of 24 ready-made agents in the library
Deliverable

A drift report listing steps that no longer match, with what each was compared against.

Human sign-off required

A drift report listing steps that no longer match, with what each was compared against. Prepared for review, never posted.

How this composition works.

Runbooks are trusted precisely when there is no time to check them, which is why drift is expensive. This workflow compares each documented step against the current state of the system it references, reports the steps that no longer resolve, and cites what it compared against. It edits no runbook.

Read the runbooks

Open the approved runbook set and extract the steps that reference systems.

Check current state

Compare each referenced path, job, or service against what exists now.

Report the drift

List the steps that no longer resolve and cite the comparison.

A human signs off

Runbook edits and any remediation of the underlying system require an accountable owner.

Deliverable

A drift report listing steps that no longer match, with what each was compared against.

Human sign-off required

A drift report listing steps that no longer match, with what each was compared against. Prepared for review, never posted.

Composed from the tools operations already uses.

Optional skills add method and verification.

Put your operations workflow under policy. Tell us what your team repeats today.

More for operations.