From wicked-garden
Orchestrates AI-powered brainstorming sessions with dynamic focus groups. This skill should be used when the user wants to brainstorm, explore ideas, get feedback on concepts, or run a focus group discussion. Sessions are tracked as native tasks (process) and stored in wicked-garden:mem (outcome). Use when: "brainstorm this", "explore ideas", "get different perspectives", "focus group", "what do you think about", "pros and cons"
npx claudepluginhub mikeparcewski/wicked-garden --plugin wicked-gardenThis skill uses the workspace's default tool permissions.
Generate diverse perspectives through structured focus group sessions.
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
Generate diverse perspectives through structured focus group sessions.
/brainstorm)Best for: Important decisions, complex problems, strategic thinking
/jam)Best for: Quick decisions, gut checks, rapid exploration
/perspectives)Best for: Gathering input, self-directed thinking, discussion prep
| Type | Focus | Examples |
|---|---|---|
| Technical | How it works | Architect, Debugger, Security |
| User | Who uses it | Power User, Newcomer, Support |
| Business | Why it matters | PM, Skeptic, Evangelist |
| Process | How it ships | Maintainer, Tester, Ops |
| Mode | Flag | Behavior |
|---|---|---|
| Normal | (default) | Run all planned rounds, then synthesize |
| Fast | --converge fast | After each round, check if signal is sufficient; skip remaining rounds if yes |
Fast convergence checks three criteria after each round: (1) at least 2 actionable insights, (2) directional agreement, (3) tensions are well-characterized. If all pass, synthesis begins immediately.
Quick jam (/jam) always uses forced fast convergence (1 round, then synthesize).
Each persona shares their view:
Convergence check (fast mode: synthesize if criteria met)
Personas respond to each other:
Convergence check (fast mode: synthesize if criteria met)
Find common ground:
Good synthesis:
Bad synthesis:
At session start:
prior = mem_recall(topic) # via /wicked-garden:mem:recall
inject_context(prior)
At session end:
if user_approves:
mem_store(insights, type="decision", tags=[topic]) # via /wicked-garden:mem:store
Sessions are tracked as native tasks for process visibility:
# On session start
TaskCreate(
subject="Jam: {topic}",
metadata={
"event_type": "task",
"chain_id": "jam-{topic-slug}.root",
"source_agent": "jam-facilitator",
"initiative": "{topic-slug}"
}
)
# After each persona round — append to description
TaskUpdate(taskId, description="{previous}\n\n{persona_name}: {key_insight}")
# After synthesis
TaskUpdate(taskId, description="{previous}\n\nSynthesis: {summary}")
# On decision
TaskUpdate(taskId, description="{previous}\n\nDecision: {decision_record}")
Wrap all task calls in graceful degradation — if TaskCreate/TaskUpdate fail, skip silently. Native tasks track process; wicked-garden:mem stores outcomes. Both can coexist.
Called during clarify, design, and build phases. See "Crew Engagement" section below.
| Phase | Mode | When |
|---|---|---|
| Clarify | Quick jam (4 personas, 1 round) | Approach options, framing decisions |
| Design | Full brainstorm (4-6 personas, 2-3 rounds) | Architecture decisions, complex tradeoffs |
| Build checkpoint | Quick jam | Course corrections when unexpected complexity arises |
Jam auto-engages when: ambiguity detected, complexity >= 4, architecture signals present, or content/documentation-heavy scope.
refs/facilitation-patterns.md — Match persona archetypes to problem types; session length guidance; anti-patterns to avoidrefs/synthesis-patterns.md — Synthesis structure, quality checklist, techniques (non-obvious connections, surprising agreements, productive tensions), decision record format, examplesSynthesis-first: ## Brainstorm: {Topic} → ### Key Insights (read first) → ### Action Items → ### Open Questions → ### Session Details (personas, rounds, summary).