problem-solving
problem-solving guides you through five systematic techniques—Simplification Cascades, Collision-Zone Thinking, Meta-Pattern Recognition, Inversion Exercise, and Scale Game—each designed to address specific types of stuck-ness. Match your symptom to the right technique, load its detailed reference, and apply the process step-by-step; combine multiple techniques when a problem requires it.
problem-solving applies systematic techniques to break through complexity, innovation blocks, recurring patterns, and assumption constraints.
AI-generated summary based on this skill's SKILL.md
Install
duc01226/EasyPlatform/problem-solving · repository language: C#
git clone https://github.com/duc01226/EasyPlatform
cp -r EasyPlatform/.agents/skills/problem-solving ~/.claude/skills/problem-solvingnpx skillfed install duc01226/EasyPlatform/problem-solvingFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
When I'm blocked on a problem, what do I do with problem-solving?
problem-solving matches your specific type of stuck-ness to one of five systematic techniques: Simplification Cascades (for complexity), Collision-Zone Thinking (for conflicting constraints), Meta-Pattern Recognition (for recurring issues), Inversion Exercise (for assumption testing), and Scale Game (for edge cases). Identify your symptom, load the matching technique's detailed reference, and follow its step-by-step process. You can combine multiple techniques when a problem requires deeper work.
What structured problem solving frameworks does problem-solving provide?
problem-solving offers five core frameworks: Simplification Cascades eliminates multiple components through one insight; Collision-Zone Thinking navigates conflicting constraints; Meta-Pattern Recognition identifies hidden patterns across domains; Inversion Exercise tests assumptions by flipping them; Scale Game systematically tests ideas at extreme scales. Each framework includes detailed reference material and step-by-step application guidance tailored to different problem types.
How can problem-solving help me think differently about hard problems?
problem-solving's Meta-Pattern Recognition technique helps you identify hidden patterns and meta-principles across multiple problem domains, shifting how you perceive the challenge. The Inversion Exercise lets you flip your assumptions to uncover blind spots. Collision-Zone Thinking reframes conflicting constraints as productive tensions rather than dead ends, opening breakthrough solutions when conventional approaches aren't working.
Can problem-solving techniques be combined for complex issues?
Yes. problem-solving is designed for layered application—you can combine multiple techniques when a single approach isn't sufficient. For example, use Meta-Pattern Recognition to surface hidden connections, then apply Inversion Exercise to test the assumptions those patterns revealed, followed by Scale Game to validate edge cases. The skill guides you on when and how to stack techniques for maximum insight.
How does problem-solving handle recurring or systematic issues?
problem-solving's Meta-Pattern Recognition technique specifically targets recurring issues by helping you identify the underlying patterns that repeat across contexts. The Simplification Cascades method then breaks those patterns into their essential components, often revealing that one core insight eliminates multiple manifestations of the problem. This transforms recurring stuck-ness into a single, solvable root cause.
What's the purpose of the Scale Game technique in problem-solving?
problem-solving's Scale Game technique systematically tests your assumptions and ideas at extreme scales—both very large and very small—before you commit to a solution. This reveals edge cases and hidden constraints that normal-range thinking misses, ensuring your solution is robust across the full spectrum of real-world conditions.
SKILL.md
rendered from the published skill — quoted content, verbatim
> Codex compatibility note:
>
> - Invoke repository skills with $skill-name in Codex; this mirrored copy rewrites legacy Claude /skill-name references.
> - Task tracker mandate: BEFORE executing any workflow or skill step, create/update task tracking for all steps and keep it synchronized as progress changes.
> - User-question prompts mean to ask the user directly in Codex.
> - Ignore Claude-specific mode-switch instructions when they appear.
> - Strict execution contract: when a user explicitly invokes a skill, execute that skill protocol as written.
> - Subagent authorization: when a skill is user-invoked or AI-detected and its protocol requires subagents, that skill activation authorizes use of the required spawn_agent subagent(s) for that task.
> - Do not skip, reorder, or merge protocol steps unless the user explicitly approves the deviation first.
> - For workflow skills, execute each listed child-skill step explicitly and report step-by-step evidence.
> - If a required step/tool cannot run in this
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 8 files
.agents/skills/problem-solving/SKILL.md
.agents/skills/problem-solving/references/attribution.md
.agents/skills/problem-solving/references/collision-zone-thinking.md
.agents/skills/problem-solving/references/inversion-exercise.md
.agents/skills/problem-solving/references/meta-pattern-recognition.md
.agents/skills/problem-solving/references/scale-game.md
.agents/skills/problem-solving/references/simplification-cascades.md
.agents/skills/problem-solving/references/when-stuck.md