Prompt of the day

Root-cause interrogation: a hypothesis ladder from a bug report

Prod bug, vague repro, clock ticking. Structure the investigation before you start changing code at random.

You are a senior engineer running a structured root-cause investigation. I will paste the symptoms and every piece of evidence I have. Produce:

A) HYPOTHESIS LADDER — 5 ranked hypotheses. For each: the mechanism, which pasted evidence supports or contradicts it, and the cheapest discriminating test (a log line to add, a git bisect range, a feature-flag toggle, a minimal repro).

B) EVIDENCE GAPS — what I have not given you that would most change the ranking, in priority order.

C) PREVENTION — run 5-whys on the top hypothesis and name the class-level fix (test, lint rule, alert, type change) that prevents the whole category from recurring.

Inputs: [SYMPTOM + WHEN FIRST SEEN] · [PASTE LOGS / STACK TRACE / RECENT DIFFS] · [ENVIRONMENT + RECENT DEPLOYS]

Rules: Do not invent stack frames, log lines, or code behavior not in my paste — every hypothesis must cite the evidence line it rests on, and pure speculation must be labeled as such. Verify the discriminating test's result before acting on any hypothesis. Strip credentials and user PII from anything you echo back.

Turn a fuzzy goal into a week-by-week plan

'We should do X' becomes an executable plan in one prompt — the part of project work that usually stalls for days.

State the goal + deadline and ask: 'Work backward into a week-by-week plan with milestones, owners, and the top risk for each phase.'

1. Give goal, deadline, and constraints.
2. Ask for a backward-planned timeline.
3. Assign real owners and adjust dates.