Simplification Cascades
- 272 installs
- 733 repo stars
- Updated October 14, 2025
- obra/superpowers-skills
Turn a spec or requirements into bite-sized implementation tasks before any code is written.
About
simplification cascades — Writing Plans converts specs into engineer-ready implementation plans—file structure, checkbox tasks, failing-test-first steps, and commit boundaries—assuming zero codebase context. It pairs with executing-plans and subagent-driven-development for delivery. Solo builders use it after brainstorming when a feature needs disciplined execution.
- Bite-sized TDD-friendly tasks with explicit file paths and verification commands.
- Requires plan header with goal, architecture, and required sub-skills.
- Scope check to split multi-subsystem specs into separate plans.
Simplification Cascades by the numbers
- 272 all-time installs (skills.sh)
- +25 installs in the week ending Jul 26, 2026 (Skillselion tracking)
- Ranked #930 of 3,301 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/obra/superpowers-skills --skill simplification-cascadesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 272 |
|---|---|
| repo stars | ★ 733 |
| Security audit | 3 / 3 scanners passed |
| Last updated | October 14, 2025 |
| Repository | obra/superpowers-skills ↗ |
What it does
Turn a spec or requirements into bite-sized implementation tasks before any code is written.
Files
Simplification Cascades
Overview
Sometimes one insight eliminates 10 things. Look for the unifying principle that makes multiple components unnecessary.
Core principle: "Everything is a special case of..." collapses complexity dramatically.
Quick Reference
| Symptom | Likely Cascade |
|---|---|
| Same thing implemented 5+ ways | Abstract the common pattern |
| Growing special case list | Find the general case |
| Complex rules with exceptions | Find the rule that has no exceptions |
| Excessive config options | Find defaults that work for 95% |
The Pattern
Look for:
- Multiple implementations of similar concepts
- Special case handling everywhere
- "We need to handle A, B, C, D differently..."
- Complex rules with many exceptions
Ask: "What if they're all the same thing underneath?"
Examples
Cascade 1: Stream Abstraction
Before: Separate handlers for batch/real-time/file/network data Insight: "All inputs are streams - just different sources" After: One stream processor, multiple stream sources Eliminated: 4 separate implementations
Cascade 2: Resource Governance
Before: Session tracking, rate limiting, file validation, connection pooling (all separate) Insight: "All are per-entity resource limits" After: One ResourceGovernor with 4 resource types Eliminated: 4 custom enforcement systems
Cascade 3: Immutability
Before: Defensive copying, locking, cache invalidation, temporal coupling Insight: "Treat everything as immutable data + transformations" After: Functional programming patterns Eliminated: Entire classes of synchronization problems
Process
1. List the variations - What's implemented multiple ways? 2. Find the essence - What's the same underneath? 3. Extract abstraction - What's the domain-independent pattern? 4. Test it - Do all cases fit cleanly? 5. Measure cascade - How many things become unnecessary?
Red Flags You're Missing a Cascade
- "We just need to add one more case..." (repeating forever)
- "These are all similar but different" (maybe they're the same?)
- Refactoring feels like whack-a-mole (fix one, break another)
- Growing configuration file
- "Don't touch that, it's complicated" (complexity hiding pattern)
Remember
- Simplification cascades = 10x wins, not 10% improvements
- One powerful abstraction > ten clever hacks
- The pattern is usually already there, just needs recognition
- Measure in "how many things can we delete?"
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.645k185kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.547k185k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.466kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).466kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.466kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.465kFAQ
Is Simplification Cascades safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.