ds-unstick

Steps

1. Stop editing. Do not try a third variation of the same fix.
2. Write down each failed attempt in one line: what you changed and what happened. Include the exact error text.
3. Write the assumption that all of those attempts shared. Typical examples: "this file is the one that runs", "the config is loaded", "the function receives a string", "the cache is cleared", "the error comes from my code". Name one, in one sentence.
4. Test that assumption directly with the cheapest probe that gives a yes or no answer: a print statement, a log line, a

   which

   or

   --version

   , a grep for the real call site, a minimal script, or a read of the docs for the exact version installed. Paste the result.
5. If the assumption is false, you have found the real problem. Plan the fix from the new fact.
6. If the assumption holds, list 3 different approaches. "Different" means another mechanism, library, layer or data path, not a tweak of the same edit. Give each approach one line on cost and risk.
7. Pick one approach and say why in one sentence.
8. Restart from a clean state if the failed attempts left debris: revert them with git (

   git stash

   or

   git checkout -- <files>

   ), then apply only the chosen approach.
9. Record the false assumption or the chosen approach in PROGRESS.md (see ds-context-reset) so a later session does not repeat the attempts.
10. Return to ds-verify-loop with the new approach.

Stop when

• The probe in step 4 explains the failure, or the new approach passes its check.
• Two rounds of this skill have failed. Stop and report to the user: the attempts, the assumptions you tested, and the evidence. Ask for direction.

Rules

• Do not repeat a fix that has already failed, even with small changes.
• Evidence beats reasoning. If a probe takes a minute, run it.
• Keep the failed-attempt list, because it is the most useful part of the report.
• Use a clean state before a new approach, so that old edits cannot hide the result.