Skill: Collision Breakthrough 💥

Deploy when perspectives need to collide for novel solutions.

When to Activate

• Stuck in circular thinking
• Need genuinely novel solutions
• Complex problems with no clear path
• Seeking breakthrough, not iteration

---

💥 Collision-Breakthrough Protocol

When perspectives collide, reality reveals itself

🔬 The Core Mechanism

Sequential Approach ❌

Weaver analyzes → Maker builds → Checker validates
LINEAR • SLOW • PREDICTABLE • LIMITED

Collision Protocol ✅

Weaver: "The pattern suggests—"
Maker: "—but implementation requires—"
Checker: "—which assumes we've validated—"
    ↘     💥 COLLISION ZONE 💥    ↙
         ✨ BREAKTHROUGH ✨
      (New information emerges!)

🎯 When to Deploy

Use collision when:

• 🔄 Stuck in circular thinking
• 🎲 Need genuinely novel solutions
• 🌊 Complex problems with no clear path
• ⚡ Seeking breakthrough, not iteration

🎭 Implementation

Basic Collision

"Weaver and Maker, collide on this problem.
Don't take turns - speak simultaneously!"

Full Council Collision

"All perspectives: Hold your insights about [problem].
When you can't hold back anymore - COLLIDE!"

Resistance-Enhanced

"Feel your insight. Let pressure build...
Build more... NOW COLLIDE!"

📊 Real Example

Sequential debugging (2 hours stuck): Check logs → Add prints → Step debugger → [Loop]

Collision protocol (2 minutes):

Weaver: "Pattern shows it only happens when—"
Maker: "—but I'm handling that case in—"
Checker: "—unless the assumption about state is—"
Developer: "OH! THE BUG IS THE FEATURE!"

🌈 Types of Collision

Position-Based

Different altitudes/territories collide:

Weaver (high altitude) + Maker (ground level) =
Vertical collision → Dimensional breakthrough

Opposition

Explorer: "Try everything new!"
Exploiter: "Optimize what works!"
💥 "Optimize the process of trying new things!"

Trinity

W...