Collision Zone Thinking
Turn a spec or requirements into bite-sized implementation tasks before any code is written.
Install
npx skills add https://github.com/obra/superpowers-skills --skill collision-zone-thinkingWhat is this skill?
- 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.
Adoption & trust: 71 installs on skills.sh; 692 GitHub stars; 3/3 security scanners passed (skills.sh audits).
Recommended Skills
Grill Memattpocock/skills
Grill With Docsmattpocock/skills
Brainstormingobra/superpowers
Lark Tasklarksuite/cli
Lark Workflow Standup Reportlarksuite/cli
Cavemanjuliusbrussee/blueprint
Journey fit
Primary fit
Writing plans belongs in idea phase—translating intent into an executable task list before build starts. Research subphase fits because the skill decomposes specs into file-level tasks with exact test commands and commit steps.
Common Questions / FAQ
Is Collision Zone Thinking safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Collision Zone Thinking
# Collision-Zone Thinking ## Overview Revolutionary insights come from forcing unrelated concepts to collide. Treat X like Y and see what emerges. **Core principle:** Deliberate metaphor-mixing generates novel solutions. ## Quick Reference | Stuck On | Try Treating As | Might Discover | |----------|-----------------|----------------| | Code organization | DNA/genetics | Mutation testing, evolutionary algorithms | | Service architecture | Lego bricks | Composable microservices, plug-and-play | | Data management | Water flow | Streaming, data lakes, flow-based systems | | Request handling | Postal mail | Message queues, async processing | | Error handling | Circuit breakers | Fault isolation, graceful degradation | ## Process 1. **Pick two unrelated concepts** from different domains 2. **Force combination**: "What if we treated [A] like [B]?" 3. **Explore emergent properties**: What new capabilities appear? 4. **Test boundaries**: Where does the metaphor break? 5. **Extract insight**: What did we learn? ## Example Collision **Problem:** Complex distributed system with cascading failures **Collision:** "What if we treated services like electrical circuits?" **Emergent properties:** - Circuit breakers (disconnect on overload) - Fuses (one-time failure protection) - Ground faults (error isolation) - Load balancing (current distribution) **Where it works:** Preventing cascade failures **Where it breaks:** Circuits don't have retry logic **Insight gained:** Failure isolation patterns from electrical engineering ## Red Flags You Need This - "I've tried everything in this domain" - Solutions feel incremental, not breakthrough - Stuck in conventional thinking - Need innovation, not optimization ## Remember - Wild combinations often yield best insights - Test metaphor boundaries rigorously - Document even failed collisions (they teach) - Best source domains: physics, biology, economics, psychology