Skip to content

kellerai/reliability-desk

v1.0.0Apache-2.0

High-reliability practices for launches, changes and incidents: go/no-go polls, blameless reviews, FMEA, readbacks, stop-the-line, change control and session checklists. Skills only; no network calls.

andon-stop-the-line

Use when the user says 'stop the line' or 'halt on defect', or when a defect should stop work rather than be logged. Declares halt triggers and owners before work starts, captures the halt state and drafts the escalation for the user to send.

blameless-incident-review

Use after an outage, a bad agent run or a shipped defect, or when the user asks for a postmortem or incident review. Reconstructs the failure from cited evidence, tests each finding with the substitution test and emits systemic actions that change conditions, never blame.

change-control-board

Use when the user asks for change control or a CAB review, or is about to merge or deploy something whose blast radius is unclear. Classifies the change as standard, normal or emergency and records a CAB decision with a named owner. Never merges or deploys.

closed-loop-readback

Use before acting on a costly or ambiguous instruction, or when the user says 'read it back to me' or 'confirm you understood'. Restates the instruction, scope, done-condition and assumptions, then waits for confirm or correct before any action.

fmea-design-review

Use when the user asks to run an FMEA, asks what could go wrong with a design or plan, or wants failure modes ranked. Scores each failure mode for severity, occurrence and detection, ranks by RPN with a severity override, and proposes owned mitigations.

get-started

Use right after Reliability Desk is enabled, or when the user asks what it does or how to start. Explains the job in one line, asks three setup questions one at a time, then hands off to the practice that fits.

go-no-go-poll

Use when the user asks for a go/no-go, asks 'are we ready to ship or launch', or is about to cut a release. Polls each discipline for an attributable GO or NO-GO with named veto owners; any single NO-GO holds the release. The user and the named owners make the call.

surgical-safety-checklist

Use at the start of risky multi-file or high-stakes work, or when the user says 'run the session checklist' or 'time out before we start'. Brackets the session with sign-in, time-out and sign-out gates; nothing changes until the user confirms the plan.