Skip to content
Skills Library
Management & product · Analysis

problem-solving

/problem-solving

Use when the user asks to solve a hard problem, break through stuck points, eliminate spiraling complexity, or find elegant solutions beyond conventional approaches.

Repository
Anvien ↗
Licence
MIT
Last repository change
25.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
8
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when the user asks to solve a hard problem, break through stuck points, eliminate spiraling complexity, or find elegant solutions beyond conventional approaches.

Original author description

Use when the user asks to solve a hard problem, break through stuck points, eliminate spiraling complexity, or find elegant solutions beyond conventional approaches.

How it works

  1. Core Philosophy
  2. Symptom Matcher & Dispatch Table
  3. Problem-Solving Workflow
  4. Quick Decision Tree
  5. Reference Index
Original SKILL.md headings · 80 lines, 436 words
SKILL.md preview
---
name: problem-solving
description: Use when the user asks to solve a hard problem, break through stuck points, eliminate spiraling complexity, or find elegant solutions beyond conventional approaches.
---

# Problem-Solving Techniques

A structured toolkit of high-leverage cognitive and architectural techniques to break through stuck points, eliminate spiraling complexity, and discover elegant solutions.

## Core Philosophy

> **"One powerful abstraction > ten clever hacks"**  
> Rather than managing complexity through brute force, these techniques help you uncover the fundamental principles that make complexity unnecessary.

---

## Symptom Matcher & Dispatch Table

When encountering a difficult technical problem or blocker, match your symptom to the appropriate technique:

| Symptom / How You're Stuck | Recommended Technique | Target Reference |
|---|---|---|
| **Unsure which method to apply** | Stuck-Type Diagnostic Dispatch | `references/when-stuck-dispatch.md` |
| **Complexity spiraling / Same logic 5+ ways** | Simplification Cascades | `references/simplification-cascades.md` |
| **Conventional solutions inadequate / Need innovation** | Collision-Zone Thinking | `references/collision-zone-thinking.md` |
| **Rigid assumptions / "Only one way" mindset** | Inversion Exercise | `references/inversion-exercise.md` |
| **Recurring pattern across 3+ domains** | Meta-Pattern Recognition | `references/meta-pattern-recognition.md` |
| **Uncertain about production limits & extreme load** | Scale Game | `references/scale-game.md` |

---

## Problem-Solving Workflow

```text
                  [Technical Blocker / Stuck Point]
                                 │
                                 ▼
                     [Identify Stuck Symptom]
                                 │
         ┌───────────────────────┼───────────────────────┐
         │                       │                       │
         ▼                       ▼                       ▼
[Complexity Spiraling]  [Need Breakthrough]      [Rigid Assumptions]
references/simplification-  references/collision-  references/inversion-
cascades.md             zone-thinking.md         exercise.md
         │                       │                       │
         ├───────────────────────┼───────────────────────┤
         │                       │                       │
         ▼                       ▼                       ▼
[Recurring Pattern]     [Extreme Scale Limits]   [Unsure Where to Start]
references/meta-pattern- references/scale-        references/when-stuck-
recognition.md          game.md                  dispatch.md
                                 │
                                 ▼
                 [Apply Technique & Extract Invariant]
                                 │
                                 ▼
             [Synthesize Clean Architectural Solution]
```

---

## Quick Decision Tree

- Not sure which technique fits your blocker? → `references/when-stuck-dispatch.md`
- Implementing the same feature multiple ways or accumulating special cases? → `references/simplification-cascades.md`
- Out of ideas within the local domain and need cross-domain metaphor breakthroughs? → `references/collision-zone-thinking.md`
- Forcing a solution that feels wrong because of unquestioned assumptions? → `references/inversion-exercise.md`
- Solving a problem that feels structurally familiar to something in networking, OS, or biology? → `references/meta-pattern-recognition.md`
- Need to stress-test an architecture before writing production code? → `references/scale-game.md`

---

## Reference Index

| Technique | Core Mission | Reference File |
|---|---|---|
| **When Stuck Dispatch** | Symptom-to-technique routing matrix and combined methods | `references/when-stuck-dispatch.md` |
| **Simplification Cascades** | Finding unifying abstractions that eliminate 10 redundant components | `references/simplification-cascades.md` |
| **Collision-Zone Thinking** | Forcing unrelated concepts together to generate novel properties | `references/collision-zone-thinking.md` |
| **Inversion Exercise** | Flipping foundational assumptions to expose hidden constraints | `references/inversion-exercise.md` |
| **Meta-Pattern Recognition** | Extracting universal primitives from patterns found in 3+ domains | `references/meta-pattern-recognition.md` |
| **Scale Game** | Testing at 1000x extremes to discover breaking points and resilient cores | `references/scale-game.md` |
Files in this package (8)
  • ABOUT.md 2 KB
  • SKILL.md 5 KB
  • references/collision-zone-thinking.md 3 KB
  • references/inversion-exercise.md 2 KB
  • references/meta-pattern-recognition.md 2 KB
  • references/scale-game.md 3 KB
  • references/simplification-cascades.md 3 KB
  • references/when-stuck-dispatch.md 3 KB

Versions

RepositoryScoreLicence
This page · tamnguyendinh/Anvien100MIT
geekatron/jerry100Apache-2.0
nguyenthienthanh/aura-frog100MIT

Database snapshot: 13.11.2026 · package version 3582568b34e9 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90bmad-cis-problem-solving
    Apply systematic problem-solving methodologies to complex challenges. Use when the user says "guide me through structured problem solving" or "I want to crack this challenge with guided problem solving techniques
  • 90bmad-cis-problem-solving
    Apply systematic problem-solving methodologies to complex challenges. Use when the user says "guide me through structured problem solving" or "I want to crack this challenge with guided problem solving techniques
  • 100goals-problem-solving
    Solve a problem or define/break down a goal using PACERS (Pause, Assess, Choose, Execute, Review, Systemize) and record the reasoning as a traceable building journey in the active Goals goal. Use inside a Goals project when defining a goal, breaking a phase into sub-problems,…
  • 100problem-framing-canvas
    Guide teams through MITRE's Problem Framing Canvas. Use when you need a clearer problem statement before jumping to solutions.
  • 95triz
    Inventive problem solving for IT and app development, built from Altshuller's "Найти идею" (TRIZ). Use it whenever someone is stuck on a hard product, architecture, UX, performance, data, team or business problem; wants "a better idea", "a non-obvious solution", "a way to have…
  • 95problem-interview
    Validate that the problem you want to solve is real, painful, and worth solving before building anything. Master Cindy Alvarez's structured approach to problem discovery interviews. Use when: **Before solution interviews** to confirm the problem exists; **Early customer…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.