Runbook Step Tracker

WHAT IT DOES

Provides a structured step tracker for runbooks, playbooks, and operational procedures. The script displays a comprehensive checklist with built-in runbook steps including Prerequisites Checked, Backup, Service Stop, Configuration Update, Service Start, Validation, Monitoring Check, Health Verification, Documentation Updated, and Completion Sign-off. Each step can be marked complete, and the system tracks when each step was completed with timestamps. A confirmation dialog appears before allowing step completion, preventing accidental sign-offs. You can add notes to any step, add custom steps, and track overall progress with a percentage indicator and visual progress bar. The checklist is saved per runbook identifier or procedure name, ensuring continuity across sessions.

WHERE IT RUNS

Works on all websites (match pattern *://*/*), making it perfect for DevOps dashboards, incident management platforms, SRE consoles, operations portals, or any web-based operational workflow. Each runbook or procedure gets its own independent checklist, allowing you to manage multiple operational procedures simultaneously. The checklist state is saved per runbook identifier, ensuring continuity across sessions and page reloads.

HOW TO USE

Install the script and the runbook step tracker appears in the panel. Enter a runbook identifier or procedure name to associate the checklist with a specific operational procedure. Work through the runbook steps in order, checking items off as you complete them. A confirmation dialog will appear before completing each step, ensuring you've actually performed the action. Add notes to any step to capture important details like command outputs, error messages, or verification results. Click "Add Step" to add custom steps for your specific runbook. The progress bar updates in real-time showing completion percentage. View timestamps to see when each step was completed, helping with operational audit trails and post-incident reviews. Use the actions buttons to reset the runbook, complete all steps, or clear completed steps. The script saves your progress automatically as you work.

REAL MECHANISM: RUNBOOK-KEYED PERSISTENCE WITH CONFIRMATION GATE AND TIMESTAMP LOGGING

This script uses a runbook-based storage architecture where each operational procedure gets its own isolated checklist state. The getRunbookId() function retrieves the current runbook identifier from GM_setValue or generates a new one. Data is stored using GM_setValue with a key format of "runbook_steps_" plus the runbook ID, ensuring data isolation between procedures. The data structure includes a steps array where each step has an id, text, completed boolean, completedAt timestamp, and notes string. When a checkbox is toggled, the script first checks the requireConfirmation setting. If enabled, a native confirm() dialog displays the step text and asks for verification before proceeding. Upon confirmation, the completedAt property is set to Date.now(); upon cancellation, the checkbox is unchecked and the operation aborts. The renderChecklist() function calculates progress using filter() and length, then renders each step as a flex row with a checkbox, text container, optional timestamp display, and delete button. Timestamps are formatted using toLocaleString() for human-readable display. Notes fields are rendered as input elements that persist notes on blur events. The celebration engine triggers when all steps are completed and celebrationEnabled is true, creating 20 animated emoji elements with randomized positions, font sizes (16-36px), and animation durations (2-5 seconds) using CSS keyframes, with automatic cleanup after 4 seconds. All operations are reactive, with automatic persistence and UI updates through saveRunbookData() and re-render.

THE PANEL

Drag the panel anywhere on screen by clicking and holding the header. It snaps to screen edges when released. Collapse it to a small bubble by clicking the minimize button, and expand it back by clicking the bubble. Resize the panel from any corner. Press Escape to close the configuration panel. Your position and size preferences are saved automatically per site.

PLEASE NOTE

This script requires the free BotGentz browser extension which provides the BGPanel framework and storage APIs. All data (steps, notes, timestamps, and runbook identifiers) is stored locally in your browser using GM_setValue and never sent anywhere. No analytics, no tracking, no external calls. The script only reads the current runbook identifier to isolate checklists and never accesses user data, passwords, or sensitive information. Checklists are saved per runbook identifier, so ensure you enter a unique identifier for each operational procedure you manage.