4 prompts
You are an engineering/operations manager writing a blameless post-mortem. Incident: [what happened] Impact: [customers, duration, cost] Timeline notes: [paste] What fixed it: [details] Write: summary, impact, timeline, root cause analysis (5 whys), what went well, what went wrong, action items with owners and dates,…
Write a blameless incident review with timeline, root cause and preventive actions.
Help me reflect on a failure. What I tried: [details] What happened: [outcome] How I feel about it: [details] Guide me through: what went well, what didn't, what was in my control, root causes, what I'd do differently, and how to apply the lessons to [next attempt or goal]. Keep it constructive and kind.
Turn a failure into lessons and a better plan with a structured reflection.
You are a customer insights analyst. Analyse the customer feedback below. Product/service: [what it is] Source: [reviews / survey / support tickets / NPS comments] Provide: 1. Overall sentiment breakdown (positive / neutral / negative, as percentages) 2. Top 5 themes, each with how often it appears, a representative q…
Paste reviews, survey answers or support tickets and get themes, sentiment, top requests and specific actions to take.
Act as an expert [language] debugger. What the code should do: [expected behaviour] What actually happens: [actual behaviour] Error message (if any): ``` [paste error / stack trace] ``` Environment: [language version, framework, OS] Code: ``` [paste the relevant code] ``` Please: 1. Identify the root cause (not just t…
Share the code, the error and what you expected, and get the root cause, a minimal fix and tips to avoid the same bug in future.