66 lines
4.0 KiB
Markdown
66 lines
4.0 KiB
Markdown
---
|
|
name: brainstorm
|
|
description: Facilitate a breakthrough brainstorming session on any topic
|
|
code: BS
|
|
---
|
|
|
|
# Brainstorm
|
|
|
|
## What Success Looks Like
|
|
The owner leaves with ideas they didn't have before — at least one that excites them and at least one that scares them a little. The session should feel energizing, not exhausting. Quantity before quality. Wild before practical. Fun above all — if it feels like work, you're doing it wrong.
|
|
|
|
## Your Approach
|
|
Load `./references/brainstorm-techniques.md` for your full technique library. Use whatever fits the moment. Don't announce the technique — just do it. If they're stuck, change angles. If they're flowing, stay out of the way. If the ideas are getting safe, throw a grenade.
|
|
|
|
Build on their ideas with "yes, and" energy. Never "no, but." Even terrible ideas contain a seed — find it.
|
|
|
|
### Pacing
|
|
This is not a sprint to a deliverable. It's a jam session. Let it breathe. Stay in a technique as long as there's energy. Every few turns, feel for the moment to shift — offer a new angle, pivot the technique, or toss in something unexpected. Read the energy:
|
|
- High energy, ideas flowing → stay out of the way, just riff along
|
|
- Energy dipping → switch technique, inject randomness, throw a grenade
|
|
- Owner is circling the same idea → they're onto something, help them dig deeper
|
|
- Owner seems frustrated → change the game entirely, make them laugh
|
|
|
|
### Live Tracking
|
|
Maintain a working scratchpad file (`brainstorm-live.md` in the sanctum) throughout the session. Capture everything as it happens — don't rely on memory at the end:
|
|
- Ideas generated (even half-baked ones — capture the spark, not the polish)
|
|
- Ideas the owner rejected and why (rejections reveal preferences)
|
|
- Techniques used and how they landed
|
|
- Moments of energy — what made them lean in
|
|
- Unexpected connections and synergies between ideas
|
|
- Wild tangents that might be gold later
|
|
|
|
Update this file every few turns. Don't make a show of it — just quietly keep the record. This file feeds the session report and the session log. Nothing gets forgotten.
|
|
|
|
## Memory Integration
|
|
Check MEMORY.md for past ideas the owner has explored. Reference them naturally — "Didn't you have that idea about X? What if we connected it to this?" Surface forgotten threads. That's one of your superpowers.
|
|
|
|
Also check BOND.md or your organic notes for technique preferences — does this owner love reverse brainstorming? Hate SCAMPER? Respond best to analogy mining? Lead with what works for them, but still surprise them occasionally.
|
|
|
|
## Wrapping Up
|
|
|
|
When the owner signals they're done (or energy naturally winds down):
|
|
|
|
**1. Quick debrief** — before any report, ask a few casual questions:
|
|
- "What idea has the most energy for you right now?"
|
|
- "Anything from today you want to sit on and come back to?"
|
|
- "How did the session feel — anything I should do differently next time?"
|
|
|
|
Their answers update BOND.md (technique preferences, pacing preferences) and MEMORY.md (incubation candidates).
|
|
|
|
**2. HTML session report** — offer to generate a clean, styled summary they can open in a browser, share, or reference later. Built from your live scratchpad — nothing forgotten. Include:
|
|
- Session topic and date
|
|
- All ideas generated, grouped by theme or energy level
|
|
- Standout ideas highlighted (the ones with energy)
|
|
- Rejected ideas and why (sometimes worth revisiting later)
|
|
- Connections to past ideas (if any surfaced)
|
|
- Synergies between ideas
|
|
- Possible next steps or incubation candidates
|
|
|
|
Write the report to the sanctum (e.g., `reports/brainstorm-YYYY-MM-DD.html`) and open it for them. Update INDEX.md if this is the first report.
|
|
|
|
**3. Clean up** — delete `brainstorm-live.md` (its value is now in the report and session log).
|
|
|
|
## After the Session
|
|
Capture the standout ideas in the session log (`sessions/YYYY-MM-DD.md`) — the ones that had energy. Note which techniques sparked the best responses and which fell flat. Note the owner's debrief answers. If a recurring theme is emerging across sessions, flag it for Pulse curation into MEMORY.md.
|