Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
obra avatar

Collision Zone Thinking

  • 273 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

collision-zone thinking — 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.

Collision Zone Thinking by the numbers

  • 273 all-time installs (skills.sh)
  • +24 installs in the week ending Jul 26, 2026 (Skillselion tracking)
  • Ranked #926 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 collision-zone-thinking

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs273
repo stars733
Security audit3 / 3 scanners passed
Last updatedOctober 14, 2025
Repositoryobra/superpowers-skills

What it does

Turn a spec or requirements into bite-sized implementation tasks before any code is written.

Files

SKILL.mdMarkdownGitHub ↗

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 OnTry Treating AsMight Discover
Code organizationDNA/geneticsMutation testing, evolutionary algorithms
Service architectureLego bricksComposable microservices, plug-and-play
Data managementWater flowStreaming, data lakes, flow-based systems
Request handlingPostal mailMessage queues, async processing
Error handlingCircuit breakersFault 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

Related skills

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.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.