Observe the world
Your own work: made specific
You bring the material; we wrote the answer key. Only you know why your release slipped — but slipped releases have about five root causes, each with its own early warning sign. Bring one concrete thing: a delay, a feature nobody used, a proposal you're about to pitch.
These prompts only exist in 简体中文 for now.
How to use this
The more specific the prompt, the sharper the grading: each specific one carries the root-cause checklist for that kind of situation, and the generic group is the fallback when none of them fits. The system design set grades you on "a benefit with no cost attached means you memorised it"; here the line is different: if you can't give a specific, it's empty.
How to start
- Pick one, open it, copy the prompt.
- Paste it into a brand-new conversation.
- Say in a sentence or two which thing you're going to talk about, then wait for its questions — unlike the system design set, where you say nothing after pasting.
Three commands you can call out at any time
跳过move to the next scene now换一个start over with a different project, outage or experience复盘jump to the wrap-up and print the review card
Three traps
- When it starts consoling you, point it back to the "don't praise me" rule — the two retrospectives are the likeliest to summon a model's soothing persona, which turns the whole thing into emotional support rather than a retrospective.
- Cut it off when it tries to complete your answer for you. You say "I don't remember", it offers "probably because the schedule was tight" — and that sentence is no longer your memory.
- Before pasting a CV or a design doc, strip out phone numbers, email addresses and anything your company wouldn't want leaving the building.
Got a proposal to pitch? Start with defending it. Just finished a project or lived through an outage? Do those retrospectives while you still remember. Job hunting? Audit the CV first, then take the lines that survived into the behavioural drill.