abstraction-laddering
Skill3 starsChanged 6 months agoMITView on GitHub
Use abstraction laddering to reframe problems by moving between higher-level why questions and lower-level how questions. Use when a problem statement feels too narrow, too vague, or needs more innovative solution framing.
In this repository23 other files it gives its agents.
- balancing-feedback-loopSkill
- concept-mapSkill
- confidence-determines-speed-vs-qualitySkill
- conflict-resolution-diagramSkill
- connection-circlesSkill
- cynefin-frameworkSkill
- decision-matrixSkill
- eisenhower-matrixSkill
- first-principlesSkill
- hard-choice-modelSkill
- iceberg-modelSkill
- impact-effort-matrixSkill
- inversionSkill
- ishikawa-diagramSkill
- issue-treesSkill
- ladder-of-inferenceSkill
- minto-pyramidSkill
- ooda-loopSkill
- productive-thinking-modelSkill
- reinforcing-feedback-loopSkill
- second-order-thinkingSkill
- situation-behavior-impactSkill
- six-thinking-hatsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Start with an initial problem statement
- Distinctive: line 19
Ask "why" questions to expand scope (move up the ladder)
- Distinctive: line 20
Ask "how" questions to develop concrete solutions (move down the ladder)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Abstraction Laddering
Overview
- Category: Problem Solving Tool
- Purpose: Frame problems more skillfully by exploring different levels of abstraction
How to Use
Core Technique
- Start with an initial problem statement
- Ask "why" questions to expand scope (move up the ladder)
- Ask "how" questions to develop concrete solutions (move down the ladder)
Key Benefits
- Helps "see the forest for the trees"
- Enables finding innovative solutions
- Can be used quickly, alone or in team settings
Example
Practical Illustration (Wes O'Haire, Dropbox)
Initial Problem: "Design a better can opener"
Moving Down (How?):
- "Make it more appealing"
Moving Up (Why?):
- "Get soup out of the can"
- "Make it more convenient"
Visual Aid
The tool is represented as a ladder where you can:
- Move up to expand problem scope
- Move down to develop specific solutions
Resources
- Worksheet available in a bundle with 9 other tools
- Sources: Wes O'Haire's "Mental Models for Designers", Autodesk's abstraction laddering guide
Related Tools
- First Principles
- Issue Trees
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

