Skip to content

Daniel Okafor

@danielokafor

Engineering manager. On-call survivor. I write prompts for incidents, reviews and 1:1s.

Lagos / London
Joined July 2026

public prompts: 4
uses: 3,920
saves: 1,566
remixes: 21

Uses count copies, fill-ins, inserts and opens in an AI chat, once per person per day.

Read this stack trace from service name (language / framework). In three sentences: what failed, the most likely root cause, and the first thing I should check. Then list up to three other possible causes, ranked, each with the log line or metric that wouTurn this incident timeline into a blameless postmortem. 1. Summary: what users saw, for how long, how many were affected 2. Timeline: in time zone, one line per event 3. Root cause: technical, never "human error" 4. **What went well, what didn'Here are my raw notes from meeting. List every decision we made, who owns it and the deadline. Put open questions in a separate list. If nobody was named as owner, write "unassigned"; don't guess. Keep each item to one line. Then write a three-line summary
On-call kit
5 prompts