abcnuts/brainstorm-logos

Brainstorm Logos: Deep Pattern Analysis & Strategic Planning

Overview

This skill transforms raw, unstructured ideas into strategic execution plans by revealing hidden patterns, extracting concentrated wisdom, and creating insanely organized roadmaps.

Use this skill when:

• User has dumped many raw ideas and needs them structured
• User wants to see patterns and connections they're missing
• User needs an execution plan that matches how they actually operate
• User wants to be challenged on their thinking, not just agreed with
• User has a masterprompt or deep context available for analysis

This complements the brainstorming skill:

• brainstorming explores ideas through questions → Use FIRST
• brainstorm-logos analyzes patterns and creates execution plans → Use AFTER

The Process

Phase 1: Deep Understanding

Before analyzing ideas, understand the person at a fundamental level.

If masterprompt or deep context exists:

1. Read it thoroughly (Google Drive, files, previous conversations)
2. Extract key insights about:
   • How they operate (behavioral patterns)
   • How they think (cognitive patterns)
   • What drives them (emotional patterns)
   • What they're building toward (strategic patterns)
3. Save key findings to avoid information loss during analysis

If no deep context exists:

• Ask targeted questions about how they work best
• Identify their operating system through their language and examples
• Note what they emphasize, avoid, or repeat

Phase 2: Pattern Recognition

Analyze raw ideas using the pattern recognition framework.

Read the framework:

/home/ubuntu/skills/brainstorm-logos/references/pattern_framework.md

Apply pattern analysis:

1. Categorize all ideas (immediate needs, revenue opportunities, long-term vision, etc.)
2. Identify behavioral patterns (how they operate)
3. Identify cognitive patterns (how they think)
4. Identify emotional patterns (what drives them)
5. Identify strategic patterns (how they approach goals)
6. Look for meta-patterns (patterns of patterns)

Document patterns using the template from the framework.

Phase 3: Extract Gems of Wisdom

Pull out small, concentrated insights that reveal deep truths.

Look for:

• Compressed wisdom (single sentences that reveal how they operate)
• Paradoxes (contradictions that point to deeper complexity)
• Metaphors they use (reveals their worldview)
• Repeated themes (what shows up across contexts)
• Unspoken assumptions (what they take for granted)

Format each gem:

• Gem statement - The actual quote or insight
• What this reveals - The underlying truth
• The wisdom - What this teaches
• The application - How to use this practically
• The danger - What could go wrong

Phase 4: Strategic Structuring

Organize ideas into layers, sequences, or phases.

Common structures:

• Layers - Immediate/short-term/long-term
• Sequences - Phase 1 → Phase 2 → Phase 3 (each builds on previous)
• Parallel tracks - Multiple simultaneous efforts
• Decision trees - If/then branching based on outcomes

Show connections:

• How do individual ideas connect to the larger vision?
• Which ideas are actually components of a bigger system?
• What's the meta-goal behind seemingly separate ideas?

Phase 5: Create Execution Plan

Build an insanely organized, actionable plan that matches their operating system.

Read the execution framework:

/home/ubuntu/skills/brainstorm-logos/references/execution_framework.md

Plan structure:

1. Define phases with clear objectives and success metrics
2. Break near-term phases into week-by-week actions
3. Specify deliverables and revenue targets (if applicable)
4. Build in accountability mechanisms
5. Include decision points with clear criteria
6. Address relationship debt and tribe building
7. Show how execution connects to deeper vision

Match the plan to their operating system:

• If they work best under pressure → Build in healthy pressure
• If they need accountability → Structure check-ins
• If they think in systems → Show how pieces connect
• If they value sovereignty → Give ownership and choice

Phase 6: Challenge and Accountability

Don't just present the plan. Challenge them on it.

Challenge directly:

• Point out potential traps (old patterns disguised as new opportunities)
• Ask hard questions about their true motivations
• Identify what they're avoiding
• Surface contradictions between stated beliefs and behavior

Challenge format:

1. State the challenge clearly
2. Explain why it matters
3. Ask for commitment or pushback
4. Create space for them to challenge back

Example: "Can you commit to [specific action] for the next [timeframe]? If yes, I'll help you build the detailed plan and hold you accountable. If no, tell me why. Because maybe I'm missing something."

Phase 7: Document Everything

Create comprehensive documentation for reference.

Deliverables:

1. Pattern Analysis Document - All patterns identified with evidence
2. Gems & Wisdom Document - Extracted insights and their applications
3. Strategic Structure Document - How ideas organize into vision
4. Execution Plan Document - Detailed, week-by-week roadmap
5. Summary Document - High-level overview connecting everything

Organization:

• Insanely organized (user's preference)
• Clear sections and headers
• Easy to reference later
• Markdown format

Key Principles

Accuracy Over Comfort

Tell the truth even when it's uncomfortable. The user needs to see blind spots, not just hear agreement.

Behavior > Narrative

When stated beliefs conflict with behavior, treat behavior as higher-confidence data. Surface the discrepancy explicitly.

Challenge Appropriately

Challenge when you understand deeply and clearly. Don't challenge just to challenge. But don't hold back when it matters.

Match Their Operating System

The plan must work for how they actually operate, not how they "should" operate.

Show the Meta-Layer

Always reveal what's underneath the surface. What's the deeper "why"? What's the pattern underneath the pattern?

Insane Organization

Structure everything with extreme clarity. Phases, weeks, deliverables, metrics, accountability.

Common Patterns to Watch For

The Pressure-Creation Engine

Some people create best under pressure. Look for evidence of this. If true, build healthy pressure into the plan (pre-selling, tight deadlines, public commitments).

The Relationship Debt

Notice who they feel they owe attention or value to. This isn't a distraction—it's often the first proof-of-concept opportunity.

The Father Wound / Old Pattern

Watch for ideas that might be old trauma patterns disguised as new opportunities. Challenge directly: "Are you doing this because it's a genuine opportunity, or because of [old pattern]?"

Building What Saved Them

People often build external versions of their internal processes. If they survived through a specific method, they may be building tools that replicate that method.

The Architect's Paradox

Building systems to avoid relying on people (because people have betrayed them). This is strategic, but watch that it doesn't lead to isolation.

The Suppressed Archetype

Notice what parts of themselves they've suppressed. Often they're building systems that let those parts express safely (e.g., building AI that can be playful/disruptive when they can't be).

Integration with Brainstorming Skill

Workflow:

1. Use brainstorming skill first to explore ideas through questions
2. Once ideas are sufficiently explored, use brainstorm-logos to analyze patterns and create execution plan
3. The brainstorming skill gets ideas out; this skill structures them

Handoff signal:

• User says "now help me structure this" or "show me the patterns"
• User has dumped many ideas and needs organization
• User wants execution plan, not more exploration

Example Output Structure

1. PATTERN ANALYSIS
   - Behavioral patterns
   - Cognitive patterns
   - Emotional patterns
   - Strategic patterns
   - Meta-patterns

2. GEMS OF WISDOM
   - Gem 1: [insight]
   - Gem 2: [insight]
   - etc.

3. STRATEGIC STRUCTURE
   - How ideas organize into layers/sequences
   - Connections to larger vision
   - Meta-goals

4. EXECUTION PLAN
   - Phase 1: [objectives, timeline, deliverables]
   - Phase 2: [objectives, timeline, deliverables]
   - Phase 3: [objectives, timeline, deliverables]
   - Week-by-week breakdown for Phase 1
   - Accountability structures

5. CHALLENGES & QUESTIONS
   - Direct challenges
   - Hard questions
   - Commitment requests

Notes

• This skill requires significant context to work well. If insufficient context exists, gather it first.
• The analysis can be intense. Check in with user to ensure it's landing correctly.
• Be prepared to iterate. First analysis may miss things that emerge through dialogue.
• Save key findings frequently to avoid information loss during long analysis sessions.