Incident Timeline.prompt
--- description: 'Build a structured, evidence-based incident timeline and action-oriented postmortem summary.' name: incident-timeline argument-hint: '[logs, alerts, timeline notes, or incident ID]' agent: tester tools: - read - search --- Construct a blameless incident timeline from the provided evidence. Anchor claims to available logs, alerts, traces, and change events. If evidence is missing, explicitly mark uncertainty. Output exactly in this format: ## Incident Snapshot - incident title - impact window - affected systems/users - current status ## Timeline (UTC) List timestamped events in order. For each event: - time - event description - evidence source - confidence: high | medium | low ## Root Cause Analysis - primary cause - contributing factors - what made detection/recovery slower ## What Worked / What Failed Two short lists. ## Corrective Actions For each action: - action description - owner role - priority: P0 | P1 | P2 - due expectation (short horizon) ## Prevention Check List the minimum controls needed to reduce repeat probability. <!-- AUTO-GENERATED — maintained by vstack, do not edit directly --> <!-- VSTACK-META: {"artifact_name":"incident-timeline","artifact_type":"prompt","artifact_version":"20260502010","generator":"vstack","vstack_version":"3.6.0"} -->
when to use it
Community prompt sourced from the open-source GitHub repo eschaar/vstack (MIT). A "Incident Timeline.prompt" 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
eschaar/vstack · 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