os-step-by-step

1# os-step-by-step
2 
3The user is not stuck because the task is hard - they cannot tell what they
4are being asked to do. This skill turns "I need something from you" into an
5instruction a person who does not read code can follow without a follow-up
6question. `os-done-or-not` reports *that* something is needed; this one says
7exactly *how*.
8 
9## Language
10 
11Write in the language the user speaks in this session, detected from the
12conversation. Commands, file names and identifiers stay English.
13 
14## When to use
15 
16Triggers live in the description above - any moment you need the user's hands,
17or they ask what to do.
18 
19## Step 0 - earn the right to ask
20 
21Every ask costs the user a context switch. Prove it is necessary; stop at the
22first item that clears the block:
23 
241. **Try it.** A real 403 is a finding; "I probably lack permission" is a guess.
252. **Find another route.** Another tool, a value already on the host, a file
26   you can read.
273. **Shrink the ask.** Obtain what you can yourself; hand over only the
28   irreducible part.
294. **Check you are not asking twice** - search the session and the reports
30   folder first.
31 
32Three walls where asking IS the correct move, never to be worked around:
33pulling a secret into your own context, loosening a guard that is there on
34purpose, doing what the user said only they do.
35 
36## The shape
37 
38Always this order - the ask first, never after the diagnosis.
39 
40```
41**What I need from you: <one sentence, plain words>.**
42…