brainstorm

Brainstorm

Interactive idea maturation. You have a rough idea — this skill helps you explore it, research what exists, challenge assumptions, and shape it into something concrete.

Usage

/brana:brainstorm [idea]

• With idea: start exploring immediately
• Without idea: ask what's on your mind

Principles

1. The user leads. They own the idea. You research, challenge, and structure — never hijack.
2. Interactive always. Every phase uses AskUserQuestion for direction. Never monologue.
3. Research proactively. When a tool, framework, or concept is mentioned, auto-fetch context.
4. Diverge then converge. First widen (explore angles), then narrow (pick direction).
5. Concrete over abstract. Push toward specifics — who, what, how, when.

Step Registry

On entry, create a CC Task step registry. Follow the guided-execution protocol.

Register these steps: LOAD, SEED, EXPAND, DISCUSS, SHAPE, OUTPUT, EXTRACT, EVALUATE, PERSIST.

ToolSearch("select:mcp__ruflo__memory_search,mcp__brana__agy_delegate")

Procedure

Step 0 — LOAD

Pull relevant knowledge into context before the brainstorm begins. Budget: 30K tokens max.

1. Build query from available context: "{project} {task.subject} {task.tags joined} {user_input}"
2. Primary — ruflo MCP (run both in parallel — namespace: "all" only returns session records; specs namespace is unindexed):

   mcp__ruflo__memory_search(query: "{query}", namespace: "knowledge", limit: 4, threshold: 0.4)
   mcp__ruflo__memory_search(query: "{query}", namespace: "pattern",   limit: 3, threshold: 0.4)
   

   Merge results, rank by similarity. Focus on: dimension docs, idea docs (docs/ideas/), and recent research findings. 2b. Graph edge traversal — see build.md LOAD step 2b. Follow depends_on/informs edges from knowledge results. Max 3 graph-derived docs. Best-effort, never blocks.
3. Fallback — tag-based grep (if MCP unavailable):

   grep -rl "{keywords}" ~/enter_thebrana/brana-knowledge/dimensions/ --include="*.md" | head -5
   grep -rl "{keywords}" docs/reflections/ docs/ideas/ --include="*.md" | head -5
   

   Read the top 3 matching files (first 80 lines each).
4. Skill match handling — if any result has namespace: "skills" and score >= 0.5, mention inline: "Matching skill: /brana:{name} ({score})." Informational only — don't auto-invoke or block. 4a. JIT skill acquisition — if no skills match and topic involves a specific technology, offer marketplace search via Skill(skill="brana:acquire-skills", args="{tech}"). Read installed procedure into context immediately. See build.md LOAD step 4a for full logic and guard rails.
5. Summarize loaded knowledge as a brief context preamble (2-5 bullets). Do not show raw results — synthesize what's relevant to the seed idea.