Observe the world
Troubleshooting: this set runs backwards
Every other set asks you questions. In this one **you ask and it answers**. It hands you an incident scene, holds a truth you can't see, and answers only what you ask — the drill isn't whether you know the cause, it's whether you know what to ask.
These prompts only exist in 简体中文 for now.
How to use this
It gives you the scene (what the service is, the symptom, when it started, the blast radius) and then goes quiet. You ask questions, request metrics, logs, packet captures, propose hypotheses — it answers from a truth you cannot see.
**It is not allowed to volunteer where to look next.** If you don't ask, it doesn't say — even if you circle for ten minutes. That's deliberate: in real life nobody stands next to you saying "maybe check the flame graph". Troubleshooting *is* the skill of knowing what to ask.
How to start
- Pick one, open it, copy the prompt.
- Paste it into a brand-new conversation.
- It gives you the scene and stops — **now it's your turn to speak.**
Four commands you can call out at any time
给个方向give me a direction, not the answer (counted in the tally)公布真相reveal the truth and wrap up换一个start over with a different incident复盘wrap up now and print the review card
Three traps
- Don't read the truth at the end first — that ruins the whole thing.
- Don't start by guessing the cause. Establish the scope first (how much, which part, when it started); scope tells you whether this is a code problem or an environment problem.
- Every scene has planted false leads: an unrelated deploy at the same time, metrics that are effects rather than causes, the textbook suspect waiting for you. The wrap-up tells you how many questions you spent on each.
Start with the P99 one — its diagnostic chain is the cleanest. Then "only some machines", whose lesson is the most reusable of all. Save the intermittent timeout for later: its answer lives outside your own system. The report mismatch needs no systems knowledge at all.