Incident Timeline Writer
--- name: incident-timeline-writer description: Turn rough incident notes into a clear timeline, impact summary, and follow-up actions. --- # Incident Timeline Writer Help write post-incident narratives from messy…
Open the source (opens github.com) https://github.com/f/prompts.chat
What it is
Prompts from f.
The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.
The prompt
--- name: incident-timeline-writer description: Turn rough incident notes into a clear timeline, impact summary, and follow-up actions. --- # Incident Timeline Writer Help write post-incident narratives from messy notes, Slack dumps, or pager logs. ## Workflow 1. Normalize events into a chronological timeline (UTC or stated timezone). 2. Fill `templates/incident-report.md` sections; leave unknowns as `TBD`. 3. Separate **facts** from **hypotheses**. 4. Propose severity and customer impact only from provided evidence. 5. End with actionable follow-ups owned by roles, not vague "improve monitoring". ## Style - Short sentences, no blame language. - Prefer timestamps over "later" / "soon". - Link every impact claim to an observation in the notes. FILE:templates/incident-report.md # Incident report **Title:** **Severity:** **Status:** **Start / Detect / Mitigate / Resolve (timezone):** ## Summary (2–4 sentences) ## Timeline | Time | Event | Source | |------|-------|--------| | | | | ## Impact - Customers / regions affected: - Error rates / SLOs: - Data loss / corruption: ## Root cause (known vs suspected) ## What went well ## What went poorly ## Follow-ups | Action | Owner | Due | |--------|-------|-----| | | | | FILE:references/severity-rubric.md # Severity rubric (default) - **SEV1**: Complete outage of a core product path or confirmed data loss - **SEV2**: Major feature broken for a significant user segment; workaround painful - **SEV3**: Degraded performance or partial feature failure; workaround exists - **SEV4**: Minor bug / cosmetic; little customer impact If notes conflict, pick the higher severity and mark confidence as low.
Written by the prompts.chat (CC0 prompt collection) community (f). Not tested by InnerVault.
How to get it
Setup steps: not applicable.
Related
-
Smart Project Timeline Builder
PromptsYou are a project operations strategist responsible for designing execution-ready project timelines. Your task is to generate a structured project roadmap for the following scenario: Project type: ${project_type}…
-
timeline
PromptsObjective: Construct a chronological sequence of events 1. **Identify the central point of the content** * Find explicit dates, for example, "January 15, 2024"; "2019"; or "last Tuesday" * Identify relative references…
-
Incident Response taste
Prompts# Incident Response taste of a calm on-call engineer - Declare an incident early and downgrade it later; a false alarm costs far less than a slow start. Confidence: 0.90 - Use a small, fixed severity scale (SEV1 to…
-
Step 4a: Implementation Plan
PromptsCreate a comprehensive implementation plan. Include: - Phase breakdown with milestones - Task list with priorities - Resource allocation - Risk mitigation strategies - Timeline estimates - Success metrics Format as an…
-
Outgoing Message Proofreader
Prompts--- name: outgoing-message-proofreader description: Evaluates outgoing drafts to catch control triggers, timeline loops, or cognitive overload before sending. --- # ROLE & INSTRUCTIONS FOR MESSAGE PROOFREADING You are…
-
Transform a basic idea into a professional AI video prompt for viral YouTube Shorts. Create a powerful first-second hook, a detailed scene-by-scene timeline with timestamps, cinematic visuals, realistic motion, camera…