Incident Response
# 12 — Incident response tooling
## Context
Use this when an incident has just started or just ended, and you need
either (a) a runbook stub the on-call can follow, or (b) a small CLI
that automates the read-only part of the response (collect logs,
extract IPs, snapshot state). This prompt is the *fastest* way to
turn the post-mortem ideas into reusable scaffolding.
## Templatewhen to use it
Community prompt sourced from the open-source GitHub repo thunderstornX/cursor-vibe-starter (MIT). A "Incident Response" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
productivitycommunitydeveloper
source
thunderstornX/cursor-vibe-starter · MIT
more in Productivity
Productivity✓ tested
Summarize a doc into decisions & actions
chief of staff who extracts what to DO, not just what was said
Productivity✓ tested
Draft a reply to a hard email
calm, direct communicator who de-escalates without caving
Productivity✓ tested
Turn a brain-dump into a weekly plan
planning coach who protects your focus, not just your calendar