メニュー
Problem-Solving Dispatch; Dispatch to the right problem-solving technique based on how you're stuck; Stuck on a problem. Conventional approaches not working. Need to pick the right problem-solving technique. Not sure which skill applies.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Interactive idea refinement using Socratic method to develop fully-formed designs. When your human partner says "I've got an idea", "Let's make/build/create", "I want to implement/add", "What if we". When starting design for complex feature. Before writing implementation plans. When idea needs refinement and exploration. ACTIVATE THIS AUTOMATICALLY when your human partner describes a feature or project idea - don't wait for /brainstorm command.
Use when debugging a web UI bug or validating a multi-step browser flow. Start or reuse background servers through run-long-running-processes-in-tmux using the deterministic current-directory-plus-purpose session name, not generic tmux names or kill-before-create setup. Prevent repo-root Playwright artifact leaks by resolving the retrospective screenshots directory once and prefixing every saved filename with it.
Use when Go code starts external processes, detaches process groups, or needs cancellation and interrupt handling with os/exec.
Go code review checklist based on official Go style guides. When reviewing Go code for style, idioms, and best practices
Use when writing or changing tests, adding mocks, tempted to add test-only methods to production code, or considering absence tests for deleted helpers, deleted client members, exported API shape, or removed routes. Prevents testing mock behavior, production pollution with test-only methods, mocking without understanding dependencies, and memorial tests whose sole purpose is to prove deleted internal/client surface stays gone while preserving tests for current observable behavior and current public/server contracts such as 404 removed-route checks.
Automatically scans GOAL.md for unchecked items, provides completion status summary, and enables coordinator to mark items as complete. When coordinator needs to verify project completion status or before marking work as complete. When coordinator needs to mark completed items in GOAL.md. Symptoms - manually going through GOAL.md line by line to check task completion, needing quick summary of pending vs completed tasks by category, and verifying all requirements are met before finalizing work.
| name | when-stuck |
| description | Problem-Solving Dispatch; Dispatch to the right problem-solving technique based on how you're stuck; Stuck on a problem. Conventional approaches not working. Need to pick the right problem-solving technique. Not sure which skill applies. |
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.
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?"];
patterns [label="Same issue in different places?\nFeels familiar across domains?\nReinventing wheels?"];
assumptions [label="Solution feels forced?\n'This must be done this way'?\nStuck on assumptions?"];
scale [label="Will this work at production?\nEdge cases unclear?\nUnsure of limits?"];
bugs [label="Code behaving wrong?\nTest failing?\nUnexpected output?"];
stuck -> complexity;
stuck -> innovation;
stuck -> patterns;
stuck -> assumptions;
stuck -> scale;
stuck -> bugs;
complexity -> simp [label="yes"];
innovation -> collision [label="yes"];
patterns -> meta [label="yes"];
assumptions -> invert [label="yes"];
scale -> scale_skill [label="yes"];
bugs -> debug [label="yes"];
simp [label="skills/problem-solving/\nsimplification-cascades", shape=box, style="rounded,filled", fillcolor=lightgreen];
collision [label="skills/problem-solving/\ncollision-zone-thinking", shape=box, style="rounded,filled", fillcolor=lightgreen];
meta [label="skills/problem-solving/\nmeta-pattern-recognition", shape=box, style="rounded,filled", fillcolor=lightgreen];
invert [label="skills/problem-solving/\ninversion-exercise", shape=box, style="rounded,filled", fillcolor=lightgreen];
scale_skill [label="skills/problem-solving/\nscale-game", shape=box, style="rounded,filled", fillcolor=lightgreen];
debug [label="skills/debugging/\nsystematic-debugging", shape=box, style="rounded,filled", fillcolor=lightyellow];
}
| How You're Stuck | Use This Skill |
|---|---|
| Complexity spiraling - Same thing 5+ ways, growing special cases | skills/problem-solving/simplification-cascades |
| Need innovation - Conventional solutions inadequate, can't find fitting approach | skills/problem-solving/collision-zone-thinking |
| Recurring patterns - Same issue different places, reinventing wheels | skills/problem-solving/meta-pattern-recognition |
| Forced by assumptions - "Must be done this way", can't question premise | skills/problem-solving/inversion-exercise |
| Scale uncertainty - Will it work in production? Edge cases unclear? | skills/problem-solving/scale-game |
| Code broken - Wrong behavior, test failing, unexpected output | skills/debugging/systematic-debugging |
| Multiple independent problems - Can parallelize investigation | skills/collaboration/dispatching-parallel-agents |
| Root cause unknown - Symptom clear, cause hidden | skills/debugging/root-cause-tracing |
Some problems need multiple techniques: