Help us improve
Share bugs, ideas, or general feedback.
From cobrew
Converts ambiguous ideas into structured design briefs through contextual analysis, requirement clarification, and incremental design validation.
npx claudepluginhub buiducnhat/cobrew --plugin cobrewHow this skill is triggered — by the user, by Claude, or both
Slash command
/cobrew:brainstorm [brief description of the idea or problem to solve][brief description of the idea or problem to solve]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to convert rough ideas into clear, reviewable design outputs through structured dialogue.
Guides collaborative brainstorming to shape requirements, compare approaches, and produce validated design/planning docs before implementation.
Guides pre-implementation ideation for features, components, and changes by exploring context, clarifying requirements, proposing trade-offs, and creating approved design docs.
Conducts structured brainstorming to clarify vague ideas, explore approaches with pros/cons, and document designs before research or planning.
Share bugs, ideas, or general feedback.
Use this skill to convert rough ideas into clear, reviewable design outputs through structured dialogue.
The goal is to:
Load only the project context relevant to the current idea:
docs/SUMMARY.md exists, read it first.Code Standard docs for implementation conventions.Also check key implementation files relevant to the idea and note constraints from existing architecture, dependencies, and conventions.
Keep this pass focused. Only gather what is needed for the current idea.
Ask targeted questions sequentially to remove ambiguity with input/question tool:
Do not jump to implementation details too early.
Propose 2-5 viable approaches.
For each approach, include:
Lead with your recommended option and explain why it best fits the project context and constraints.
After presenting all approaches, use input/question tool to let the user pick their preferred approach. List the summary options. Example:
with the tag added for the recommended approach to guide the user.
Once requirements are clear, present the design incrementally in logical phases (about 200-300 words per phase) to avoid overwhelming the user.
After presenting each phase, use input/question tool immediately to ask whether to:
After you and the user have worked through requirements and the design is validated, determine the next actions.
Use input/question tool to present the user with three high-level next actions:
write-plan handoff.If the user picks Write artifacts, proceed to Step 6. Once the draft artifacts exist, use input/question tool again to validate them with options:
If the user picked Write plan immediately, initiate a handoff to use skill write-plan using the current brainstorming context; no additional artifact validation is required.
If the user picked End session, simply stop. The information collected so far is considered sufficient.
Only perform this step after the user has explicitly chosen "Write artifacts" during Step 5.
Persist results to the standardized location:
docs/brainstorms/YYMMDD-HHmm-<topic-slug>/docs/brainstorms/YYMMDD-HHmm-<topic-slug>/SUMMARY.mddocs/brainstorms/YYMMDD-HHmm-<topic-slug>/section-01-<slug>.mddocs/brainstorms/YYMMDD-HHmm-<topic-slug>/section-02-<slug>.mdSUMMARY.md format: strictly follow the template inside references/summary-template.md.