breakthrough_skill

Overview

This skill provides a structured creativity toolkit for when conventional approaches fail and you feel stuck. It maps symptoms to six targeted techniques, guides a short protocol to name the stuck, apply a technique, evaluate results, and document the learning. Use it to convert stalled work into actionable next steps or to generate novel solution paths quickly.

How this skill works

The skill inspects your symptom statement (what is stuck, what you've tried, and perceived constraints) and dispatches one of six techniques: Simplification Cascade, Scale Game, Meta-Pattern Recognition, Assumption Inversion, Constraint Removal, or Fresh Perspective. It provides a decision tree for chaining techniques when a single pass is insufficient, and a compact output template (Breakthrough Analysis) to capture insights and the next concrete action. It also flags when the skill is inappropriate (e.g., problem already well-defined or insufficient research).

When to use it

• Progress has stalled and solutions feel forced or overcomplicated
• You keep cycling through options and none look acceptable
• You feel overwhelmed by problem scope or lost in details
• A single constraint appears to block all viable paths
• You need a fresh viewpoint to break repetitive thinking

Best practices

• Start by naming the stuck: symptom, what you tried, and the immovable constraint
• Pick a technique based on the symptom dispatch table or the decision tree
• Apply focused, time-boxed iterations and evaluate outcomes immediately
• Chain techniques if needed—switch directions rather than repeating the same step
• Document the breakthrough analysis so the insight is reusable for future problems

Example use cases

• A product design team stuck on a feature that feels too complex: run Simplification Cascade then Scale Game
• An engineer hitting a wall due to a deployment constraint: try Constraint Removal to invent alternative flows
• A researcher who 'can't figure out' the framing: use Meta-Pattern Recognition to reclassify the problem
• A small team where every option seems bad: apply Assumption Inversion to expose hidden trade-offs
• A solo developer overwhelmed by feature scope: use Fresh Perspective (explain to a rubber duck or channel an expert) and then simplify