Skip to main content
Prompts Incident Postmortem Markdown Report Generator

model analysis user risk: low

Incident Postmortem Markdown Report Generator

Create a new Markdown file for a postmortem analysis that includes the original message, what happened, how it happened, chronological steps taken to fix the problem, commands used…

PROMPT 

create a new markdown file that as a postmortem/analysis original message, what happened, how it happened, the chronological steps that you took to fix the problem. The commands that you used, what you did in the end. Have a section for technical terms used, future thoughts, recommended next steps etc.

REQUIRED CONTEXT

  • original message
  • incident details
  • fix steps and commands

EXPECTED OUTPUT

Format
markdown
Schema
markdown_sections · Postmortem/Analysis Original Message, What Happened, How It Happened, Chronological Steps to Fix the Problem, Commands Used, What You Did in the End, Technical Terms Used, Future Thoughts, Recommended Next Steps
Constraints
  • include sections for original message
  • what happened
  • how it happened
  • chronological steps to fix
  • commands used
  • final actions
  • technical terms used
  • future thoughts
  • recommended next steps

SUCCESS CRITERIA

  • Create a new markdown file
  • Include postmortem/analysis of original message
  • Describe what happened
  • Describe how it happened
  • Include chronological steps to fix the problem
  • List commands used
  • Describe what was done in the end
  • Include section for technical terms used
  • Include future thoughts
  • Include recommended next steps

FAILURE MODES

  • Misinterpreting garbled phrasing like 'that as a postmortem/analysis original message'
  • Omitting sections due to vague 'etc.'
  • Failing to use markdown format
  • Lacking context leading to invented details

CAVEATS

Dependencies
  • Context of prior problem incident
  • Details of original message
  • Knowledge of fix steps and commands used
Missing context
  • Details of the specific incident, original message, steps taken, and commands used.
  • Domain or technical context for terms.
  • Desired filename for the markdown file or exact output method.
Ambiguities
  • 'that as a postmortem/analysis original message' phrasing is unclear and grammatically awkward.
  • Unclear what 'original message' refers to without prior context.
  • 'etc.' leaves sections open-ended.

QUALITY

OVERALL
0.50
CLARITY
0.60
SPECIFICITY
0.50
REUSABILITY
0.40
COMPLETENESS
0.50

IMPROVEMENT SUGGESTIONS

  • Rewrite for clarity: 'Create a Markdown file as a postmortem analysis with sections: Original Message, What Happened, How It Happened, Chronological Fix Steps (include commands), Final Actions, Technical Terms, Future Thoughts, Recommended Next Steps.'
  • Add placeholders like {original_message} and {fix_steps} to make it template-reusable.
  • Specify output format explicitly, e.g., 'Output the full Markdown content here.'

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR MODEL