Collision-Zone Thinking

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 6d51b9a892b5 · 22 Oct 2026Report an issue or request a re-scan

• Publisherobra GitHub userOwner of the repository this skill is read from
• Source folderobra/superpowers-skills/skills/problem-solving/collision-zone-thinkingThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict6d51b9a892b5A new audit runs when the source changes
• Repository statusArchivedLast push 372 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Force unrelated concepts together to discover emergent properties - "What if we treated X like Y?

---
name: Collision-Zone Thinking
description: Force unrelated concepts together to discover emergent properties - "What if we treated X like Y?"
when_to_use: when conventional approaches feel inadequate and you need breakthrough innovation by forcing unrelated concepts together
version: 1.1.0
---

# 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

Excerpt, first 2,235 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/obra/superpowers-skills
git -C superpowers-skills checkout 6d51b9a892b5

Works in

1. 2026-10-22
   ✓SAFE B 89 / 100

   first audit · source 6d51b9a892b5

Questions about Collision-Zone Thinking

• github.com/obra/superpowers-skills/tree/main/skills/problem-solv — the audited source at commit 6d51b9a892b5 and every finding aboveObserved · 22 Oct 2026

Spotted something wrong? Report a correction · Methodology