| name | veda-brainstorm |
| model | claude-sonnet-4-6 |
| description | VEDA gap-finding interview. Guided questions to surface what VEDA could do for the user that it isn't already. Ends with one concrete suggestion, not a feature list. Use when the user says /brainstorm, "what else can you help with", "I feel like I'm missing something", "what should I set up next". |
Brainstorm Gaps
Help the user find what VEDA should do for them that it isn't doing yet. This is not an open-ended "what do you want?" — it's guided questions that pull at real friction.
Step 1: Read Current State
Read CLAUDE.md, MEMORY.md, and check what is already configured:
test -f style/style-guide.md && echo "style:done"
test -f rhythms/RECURRING.md && echo "rhythms:done"
ls projects/*.md projects/*/ 2>/dev/null | wc -l
grep -c "^| " slack/channel-summaries/_registry.md
ls people/*.md 2>/dev/null | wc -l
Use this state so you don't suggest things that are already set up.
Step 2: Ask Guided Questions
One at a time. Acknowledge each answer before the next. Stop at 2–3 questions — enough to suggest one concrete thing.
Question 1: Repetition
"What's the thing you spend the most time on that feels repetitive — same shape every week, same kind of task, same kind of message?"
Question 2: Re-explanation
"Is there context you find yourself re-explaining every time you start something new — to yourself, to me, to a friend, to a doctor, to anyone?"
Question 3: Procrastinated organization
"Is there something you keep meaning to organize, write down, or get out of your head, but you haven't?"
Question 4 (only if 1–3 didn't surface a clear target): Tool-to-tool friction
"What's the last thing you copy-pasted between two tools and thought 'this should be easier'?"
Step 3: Suggest ONE Concrete Action
Map their answers to a specific VEDA action. Pick one. Don't list options unless they're truly equivalent.
| User's answer pattern | Concrete suggestion |
|---|
| Repetitive task | Recurring rhythm in rhythms/RECURRING.md OR a workflow in CLAUDE.md |
| Re-explaining personal context (health, family, etc.) | Add a section to MEMORY.md so it's loaded every session |
| Re-explaining a person's context | Build out their profile in people/{name}.md |
| Procrastinated organization | Project file (light or heavy) in projects/ |
| Tool-to-tool friction | Connect or use the relevant API integration; add a workflow that pulls from both |
| Drafting feels off | Style guide (/style) |
| Decisions you keep relitigating | Decision record in decisions/ |
| Forgetting birthdays, anniversaries, dates | Important Dates section in person profiles + add to rhythms/RECURRING.md |
Format the suggestion concretely:
"Sounds like the friction is {specific thing they said}. The fix is {specific action — one sentence}. Want me to set that up now?"
If they say yes, execute it inline or hand off to the matching skill.
Step 4: Close
"Want to keep digging, or call it good?"
If done:
"Run /brainstorm anytime you feel something's off but you can't name it."
