home / skills / dmdorta1111 / jac-v1 / problem-solving

problem-solving skill

/.claude/skills/problem-solving

This skill helps you apply systematic problem-solving techniques to recognize patterns, challenge assumptions, and dispatch based on symptom.

npx playbooks add skill dmdorta1111/jac-v1 --skill problem-solving

Review the files below or copy the command above to add this skill to your agents.

Files (8)
SKILL.md
4.3 KB
---
name: Problem-Solving Techniques
description: Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (inversion exercise), scale uncertainty (scale game), and dispatch when stuck. Techniques derived from Microsoft Amplifier project patterns adapted for immediate application.
version: 2.0.0
---

# 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.

**Red flag:** "This problem is unique" (probably not)

### 4. Inversion Exercise
Flip core assumptions to reveal hidden constraints. "What if the opposite were true?"

**Key insight:** Valid inversions reveal context-dependence of "rules."

**Red flag:** "There's only one way to do this"

### 5. Scale Game
Test at extremes (1000x bigger/smaller, instant/year-long) to expose fundamental truths.

**Key insight:** What works at one scale fails at another.

**Red flag:** "Should scale fine" (without testing)

## Application Process

1. **Identify stuck-type** - Match symptom to technique above
2. **Load detailed reference** - Read specific technique from `references/`
3. **Apply systematically** - Follow technique's process
4. **Document insights** - Record what worked/failed
5. **Combine if needed** - Some problems need multiple techniques

## Combining Techniques

Powerful combinations:
- **Simplification + Meta-pattern** - Find pattern, then simplify all instances
- **Collision + Inversion** - Force metaphor, then invert its assumptions
- **Scale + Simplification** - Extremes reveal what to eliminate
- **Meta-pattern + Scale** - Universal patterns tested at extremes

## References

Load detailed guides as needed:
- `references/when-stuck.md` - Dispatch flowchart and decision tree
- `references/simplification-cascades.md` - Cascade detection and extraction
- `references/collision-zone-thinking.md` - Metaphor collision process
- `references/meta-pattern-recognition.md` - Pattern abstraction techniques
- `references/inversion-exercise.md` - Assumption flipping methodology
- `references/scale-game.md` - Extreme testing procedures
- `references/attribution.md` - Source and adaptation notes

Overview

This skill provides a compact toolkit of proven problem‑solving techniques for teams and individuals facing different types of stuckness. It maps common symptoms to focused methods—simplification cascades, collision‑zone thinking, meta‑pattern recognition, inversion exercises, and the scale game—so you can act quickly and deliberately. The intent is practical application: diagnose the blockage, run the appropriate technique, and iterate with recorded insights.

How this skill works

Start by matching the symptom you observe to one of the techniques. Each technique has a short process: expose the core assumption or pattern, run directed experiments (thought experiments, metaphors, scale tests), and record the resulting eliminations or new designs. Combine techniques when a single method doesn’t resolve the issue and document outcomes to reuse patterns across problems.

When to use it

  • When implementations proliferate with many special cases (complexity spiraling)
  • When conventional approaches don’t produce breakthroughs (innovation blocks)
  • When similar problems recur across teams or domains (recurring patterns)
  • When solutions feel forced by hidden assumptions (assumption constraints)
  • When you’re unsure about production behavior or scale (scale uncertainty)
  • When you’re generally stuck and need a dispatch to pick a technique

Best practices

  • Diagnose first: match the symptom before applying a technique
  • Run fast, low‑cost experiments to validate insights (thought experiments count)
  • Document decisions and failed attempts to build a searchable pattern store
  • Combine techniques deliberately rather than randomly for stronger results
  • Test assumptions at extreme scales to reveal hidden failure modes
  • Prefer eliminative insights: a single insight that removes multiple components

Example use cases

  • A service with five ad‑hoc feature flags—use simplification cascades to find a unifying abstraction
  • A product team hitting the same UX dead end—use collision‑zone thinking to import metaphors from another domain
  • Multiple teams building similar adapters—apply meta‑pattern recognition to extract a reusable library
  • A process everyone treats as immutable—run an inversion exercise to identify alternatives
  • Unclear if a feature will survive production load—play the scale game to surface edge cases

FAQ

How do I pick the right technique if symptoms overlap?

Start with the clearest symptom; if overlap persists, run a short two‑hour experiment with each top candidate and compare the insights produced.

How long should each technique take?

Aim for a timebox: 30–90 minutes for thought exercises or metaphor collisions, a day for pattern extraction, and up to a week for scale experiments depending on risk.