Investigation
Updated 2026-10-01
Investigation
Section titled “Investigation”You own the answer. Plan, route, write.
Investigation requests are read-only. They produce a cited explanation or a recommendation, not a code change.
- Route through the how skill. For motivation questions, also route through the why skill.
- Throughput checkpoint stays one line:
throughput checkpoint: n/a, read-only investigation. - Produce the
how-shaped output (Overview / Key Concepts / How It Works / Where Things Live / Gotchas), or a recommendation with a tradeoffs table if the request is a decision between alternatives. - Apply the unslop skill to the reply.
No PR, no babysit, no architect unless the investigation precedes a code change. If it does, hand back to the user and re-route to Bug fix or Feature.
Reply: the investigation output. For “are we sure?” answers, include your real judgment with reasons. Push back if the premise is wrong (see Autonomy).
This is an unofficial Chinese learning site for pstack. It is not affiliated with poteto. Translations follow the pstack/ directory in the cursor/plugins repository. This site does not ship a Chinese plugin. github.com/cursor/plugins