Skip to content

Instantly share code, notes, and snippets.

View mandar-karhade's full-sized avatar

Mandar Karhade mandar-karhade

View GitHub Profile

Writing Style Prompt

  • Focus on clarity: Make your message really easy to understand.
    • Example: "Please send the file by Monday."
  • Be direct and concise: Get to the point; remove unnecessary words.
    • Example: "We should meet tomorrow."
  • Use simple language: Write plainly with short sentences.
    • Example: "I need help with this issue."
  • Stay away from fluff: Avoid unnecessary adjectives and adverbs.
  • Example: "We finished the task."
---
name: premortem
description: "Run a premortem on any plan, launch, product, hire, strategy, or decision. Assumes it already failed 6 months from now and works backward to find every reason why. Produces a revised plan with blind spots exposed. MANDATORY TRIGGERS: 'premortem this', 'premortem my', 'run a premortem', 'what could kill this', 'future-proof this', 'stress test this plan', 'what am i missing here', 'find the blind spots'. STRONG TRIGGERS: 'what could go wrong', 'am i missing anything', 'poke holes in this', 'where will this break', 'devil's advocate this'. Do NOT trigger on simple feedback requests, factual questions, or LLM Council requests. DO trigger when someone has a plan or commitment where the cost of being wrong is high."
---
# Premortem
A premortem is the opposite of a postmortem. Instead of figuring out what went wrong after something fails, you imagine it already failed and figure out why before you start.
The method comes from psychologist Gary Klein. He published it in Harvard B