os-step-by-step

# os-step-by-step The user is not stuck because the task is hard - they cannot tell what they are being asked to do. This skill turns "I need something from you" into an instruction a person who does not read code can follow without a follow-up question. `os-done-or-not` reports *that* something is needed; this one says exactly *how*. ## Language Write in the language the user speaks in this session, detected from the conversation. Commands, file names and identifiers stay English. ## When to use Triggers live in the description above - any moment you need the user's hands, or they ask what to do. ## Step 0 - earn the right to ask Every ask costs the user a context switch. Prove it is necessary; stop at the first item that clears the block: 1. **Try it.** A real 403 is a finding; "I probably lack permission" is a guess. 2. **Find another route.** Another tool, a value already on the host, a file you can read. 3. **Shrink the ask.** Obtain what you can yourself; hand over only the irreducible part. 4. **Check you are not asking twice** - search the session and the reports folder first. Three walls where asking IS the correct move, never to be worked around: pulling a secret into your own context, loosening a guard that is there on purpose, doing what the user said only they do. ## The shape Always this order - the ask first, never after the diagnosis. ``` **What I need from you: <one sentence, plain words>.** Why you and not me: <one or two sentences. A r...