get-unstuck

# Stuck — recovery checklist Stop. Don't make another tool call. Read this whole skill before deciding what to do next. ## What "stuck" actually looks like You probably got here because one of these is true: - The same file keeps being edited and reverted, or the same tool keeps being called with slightly different inputs and the same result. - You've explained a plan three different ways and the user is still unhappy. - A test / build keeps failing and your fixes aren't moving the failure mode, just relocating it. - You're about to open a PR / send a commit but you can't summarise what changed. If none of those describe the moment, this skill probably isn't what you needed. ## Recovery — five-step recipe ### 1. State the original goal in one sentence What was the *user's* original ask? Not your interpretation, not the third-derivative subgoal you ended up chasing. The literal prompt or its plain-English rephrasing. ### 2. List what's actually been done Not what you tried, not what you intended. What's *committed to disk* or *visible in the conversation* right now. Bullet list of ≤ 5 items. ### 3. List the open question(s) What single piece of information would unblock you? It's almost always one of: - A clarification from the user (which of two interpretations, what counts as "done", which file is canonical). - A reading you skipped (a config you haven't opened, a log line you haven't grepped, a manifest you assumed about). - A test / repro you don...