Brainstorm
/hub:brainstormgenerates 3+ labelled options with trade-offs for any direction you're unsure about — before you commit to writing code.
When to use it
- You have a vague idea and don't know the right shape yet.
- You're picking a library, pattern, or architecture and want the trade-offs surfaced.
- You want a second opinion that won't defer to whatever you suggest first.
When NOT to use it
- You already know what to build. Skip brainstorm, go straight to plan.
- You're fixing a bug. Use debug — brainstorm will generate 3 theories when you need a root cause.
Invocation
/hub:brainstorm llm observability for a chatbot with 1000 concurrent users@hub brainstorm llm observability for a chatbot with 1000 concurrent usersWhat the approval gate looks like
Brainstorm is MEDIUM, so you get a one-line preview before dispatch:
MEDIUM: dispatch hub:product-manager with socratic-gate + plan-writing
estimate: ~18k tokens
Proceed? [y/n/tweak]Example session
Picking an observability stack
user
/hub:brainstorm llm observability for a chatbot with 1000 concurrent users
gate
MEDIUM · hub:product-manager · ~18k tokens · Proceed? [y/n/tweak]
user
y
hub:product-manager
Three options with trade-offs:
- Managed-first (Langfuse + Grafana Cloud)— fastest to prod, recurring SaaS cost. Best if your team hasn't built observability before.
- OSS-core (OTel + Jaeger + Prometheus + Loki) — flexible, cheaper at scale, higher ops burden. Best if you already run an observability stack.
- Hybrid (recommended) — Langfuse for LLM signals, your existing infra stack for system metrics. Balanced speed and control.
Recommendation: option 3. Want me to /hub:plan the rollout?
Pro tips
- Be specific in the prompt.“Brainstorm state management” gets generic. “Brainstorm state management for a multi-tab editor with undo and 100+ live collaborators” gets tailored.
- Always ask for trade-offs by name(“with trade-offs”, “with failure modes”, “with cost implications”). Product-manager will structure accordingly.
- Don't run create after brainstorm. Run
/hub:planfirst — it turns the chosen option into a real file you can review.
Next steps
- Plan — commit the chosen direction to a file.
- Project planner — the agent behind plan.
- Approval gate — how the prompt above is generated.