From ralph-ban
Explores fuzzy ideas and produces design docs for ralph-ban projects. Use when you have a vague goal or problem that needs exploration before planning.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ralph-ban:rb-brainstorm [idea or problem to explore][idea or problem to explore]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Explore a fuzzy idea and produce a design doc that feeds into `/rb-planning`.
Explore a fuzzy idea and produce a design doc that feeds into /rb-planning.
Before asking questions, build context silently:
bl ready and bl list --status backlog (never full bl list which dumps the large done column). Note existing cards to avoid duplicating work..agent-history/ directory listing for prior designs and investigations.$ARGUMENTS is empty, use AskUserQuestion to ask: "What are you thinking about building or solving?"Ask questions one at a time using AskUserQuestion. Multiple choice preferred over open-ended when possible. Cover these areas, adapting to what's relevant:
Stop when enough context exists to differentiate approaches (typically 3-5 questions). Skip questions the user already answered in $ARGUMENTS.
Propose 2-3 approaches:
AskUserQuestion with lettered options (a/b/c)Before saving, present the draft design doc to the user section by section:
This review loop catches misunderstandings before they propagate to planning and execution.
mkdir -p .agent-history/ (never assume it exists).agent-history/YYYY-MM-DD-<topic>-design.mdreferences/design-doc-template.mdAsk: "Design doc saved to <path>. Want to create board cards now with /rb-planning, or stop here to review first?"
If the user wants to continue, invoke the Skill tool: skill: "rb-planning", args: "<design-doc-path>"
Stopping is a valid end state. The design doc sits in .agent-history/ for future reference.
npx claudepluginhub kylesnowschwartz/ralph-ban --plugin ralph-banGuides collaborative brainstorming to shape requirements, compare approaches, and produce validated design/planning docs before implementation.
Guides a disciplined Socratic brainstorming loop before any creative or implementation work: clarifying questions, pushback, trade-off analysis, design doc, user approval, then handoff to implementation.
Guides structured brainstorming before any creative work: explores user intent, requirements, and design before implementation. Prevents wasted effort from unexamined assumptions.