When Stuck - Problem-Solving Dispatch
Installation
SKILL.md
When Stuck - Problem-Solving Dispatch
Overview
Different stuck-types need different techniques. This skill helps you quickly identify which problem-solving skill to use.
Core principle: Match stuck-symptom to technique.
Quick Dispatch
digraph stuck_dispatch {
rankdir=TB;
node [shape=box, style=rounded];
stuck [label="You're Stuck", shape=ellipse, style=filled, fillcolor=lightblue];
complexity [label="Same thing implemented 5+ ways?\nGrowing special cases?\nExcessive if/else?"];
innovation [label="Can't find fitting approach?\nConventional solutions inadequate?\nNeed breakthrough?"];
Related skills
More from obra/superpowers-skills
getting started with skills
Skills wiki intro - mandatory workflows, search tool, brainstorming triggers
292test-driven development (tdd)
Write the test first, watch it fail, write minimal code to pass
10brainstorming ideas into designs
Interactive idea refinement using Socratic method to develop fully-formed designs
10writing plans
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context
8systematic debugging
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
8code review reception
Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation
7