Brainstorm
npx machina-cli add skill rjroy/vibe-garden/brainstorm --openclawBrainstorm
Record exploratory conversation. Emphasize "what if" over raw solutions.
When to Use
- Exploring possibilities before committing to an approach
- Thinking through trade-offs
- Recording ideas for later reference
- Consuming sketches, diagrams, or visual input into the session
Process
- Engage in exploratory dialogue
- Ask "what if" questions to expand thinking
- Don't rush to solutions - sit with possibilities
- When the brainstorm reaches a natural pause, offer to save it
- Save to
.lore/brainstorm/
Handling Sketches
If the user provides a sketch, diagram, or image:
- Consume it into the session
- Describe what you see
- Use it as fuel for the brainstorm
- Reference it in the saved document
Output
Save to .lore/brainstorm/[topic].md
Use kebab-case. Track session dates in frontmatter, not filenames.
Document Structure
Before writing: Load ${CLAUDE_PLUGIN_ROOT}/shared/frontmatter-schema.md to get frontmatter field definitions and status values for brainstorms.
---
[frontmatter per schema]
---
# Brainstorm: [Topic]
## Context
What prompted this exploration.
## Ideas Explored
- Idea 1: description and "what if" implications
- Idea 2: description and trade-offs considered
## Sketches
(If any were provided, describe them here)
## Open Questions
Questions that emerged but weren't resolved.
## Next Steps
(Optional) Where this might lead.
Context
Check .lore/research/ for external context that might inform the brainstorm.
Specialized Agents
If .lore/lore-agents.md exists, consult it for specialized agents that can help with domain-specific concerns. Domain experts can expand thinking in areas like security, architecture, or performance. Invoke relevant agents via Task tool and incorporate their insights.
Source
git clone https://github.com/rjroy/vibe-garden/blob/main/lore-development/skills/brainstorm/SKILL.mdView on GitHub Overview
Brainstorm records exploratory conversations focused on 'what if' scenarios. It helps teams map options, evaluate trade-offs, and preserve ideas by saving sessions to the .lore/brainstorm directory for future reference.
How This Skill Works
Begin with an exploratory dialogue and ask 'what if' questions to expand thinking without rushing to solutions. When the session reaches a natural pause, save it to .lore/brainstorm/[topic].md using kebab-case, with session dates tracked in frontmatter. If sketches or diagrams are provided, consume them into the session, describe them, and reference them in the saved document.
When to Use It
- Exploring possibilities before committing to an approach
- Thinking through trade-offs
- Recording ideas for later reference
- Consuming sketches, diagrams, or visual input into the session
- Exploring options for a problem or decision
Quick Start
- Step 1: Trigger a brainstorm with prompts like 'let's brainstorm' or 'what if we...'
- Step 2: Engage in exploratory dialogue, ask what-if questions, and capture ideas
- Step 3: Save the session to .lore/brainstorm/[topic].md using kebab-case and proper frontmatter dates
Best Practices
- Lead with open-ended, what-if prompts to widen the exploration
- Pause to let possibilities breathe; avoid rushing to solutions
- Save the brainstorm at a natural pause to preserve context
- Treat sketches and diagrams as fuel; describe and reference them in the session
- Save to .lore/brainstorm/[topic].md using kebab-case and track dates in frontmatter
Example Use Cases
- Brainstorm product feature ideas using concrete 'what if' prompts and note trade-offs
- Map architectural trade-offs (performance vs. cost) during initial concepting
- Capture interview or user-study ideas by exploring questions and prompts
- Incorporate a user sketch into the session and describe how it informs options
- Outline a go-to-market approach by exploring multiple channels and risks
