Agent skill · writing content · samhvw8
problem-solving
Systematic problem-solving techniques for stuck-ness. Techniques: simplification cascade (complexity spirals), collision-zone thinking (innovation blocks), meta-pattern recognition (recurring issues), inversion exercise (assumption constraints), scale game (uncertainty). Actions: simplify, analyze, recognize patterns, invert assumptions, scale thinking. Keywords: problem solving, complexity spiral, innovation block, stuck, simplification, meta-pattern, assumption inversion, scale uncertainty, breakthrough thinking, root cause, systematic analysis, Microsoft Amplifier, debugging approach, creative solution. Use when: complexity spiraling, hitting innovation blocks, seeing recurring patterns, constrained by assumptions, uncertain about scale, generally stuck on problems.
Why this skill is useful
Provides systematic problem-solving techniques that help the AI recognize and address complex issues it might not infer on its own.
What it needs
About 2k tokens when loaded. Last updated 2025-12-09. 10 stars on the source repository.
What this skill does
Problem-Solving Techniques Systematic approaches for different types of stuck-ness. Each technique targets specific problem patterns. When to Use Apply when encountering: Complexity spiraling - Multiple implementations, growing special cases, excessive branching Innovation blocks - Conventional solutions inadequate, need breakthrough thinking Recurring patterns - Same issue across domains, reinventing solutions Assumption constraints - Forced into "only way", can't question premise Scale uncertainty - Production readiness unclear, edge cases unknown General stuck-ness - Unsure which technique applies Quick Dispatch Match symptom to technique: Stuck Symptom Technique Reference --------------- ----------- ----------- Same thing implemented 5+ ways, growing special cases Simplification Cascades references/simplification-cascades.md Conventional solutions inadequate, need breakthrough Collision-Zone Thinking references/collision-zone-thinking.md Same issue in different places, reinventing wheels Meta-Pattern Recognition references/meta-pattern-recognition.md Solution feels forced, "must be done this way" Inversion Exercise references/inversion-exercise.md Will this work at production? Edge cases unclear? Scale Game references/scale-game.md Unsure which technique to use When Stuck references/when-stuck.md Core Techniques 1. Simplification Cascades Find one insight eliminating multiple components. "If this is true, we don't need X, Y, Z." Key insight: Everything is a special case of one general pattern. Red flag: "Just need to add one more case..." (repeating forever) 2. Collision-Zone Thinking Force unrelated concepts together to discover emergent properties. "What if we treated X like Y?" Key insight: Revolutionary ideas from deliberate metaphor-mixing. Red flag: "I've tried everything in this domain" 3. Meta-Pattern Recognition Spot patterns appearing in 3+ domains to find universal principles. Key insight: Patterns in how patterns emerge reveal reusable abstractions. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills samhvw8/problem-solving