Help us improve
Share bugs, ideas, or general feedback.
From brain-storm-plugin
Brainstorm future features and improvements based on the current codebase. This is the ideation step BEFORE writing specs (/writing-specs). Use when user asks to brainstorm ideas, generate feature ideas, explore improvements, or mentions 브레인스톰, 아이디어, 기능 제안, 개선 아이디어, 뭐 만들까, 앞으로 뭐 하지. Also trigger for cleanup requests like 브레인스톰 정리, 구현된 아이디어 정리. Proactively trigger when the user wants creative exploration of what COULD be built.
npx claudepluginhub devstefancho/claude-plugins --plugin brain-storm-pluginHow this skill is triggered — by the user, by Claude, or both
Slash command
/brain-storm-plugin:brain-stormThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
`/writing-specs`로 스펙을 작성하기 전 단계. 사용자가 전달한 아이디어를 바탕으로 추가적이고 구체적인 아이디어를 도출한다. 아이디어마다 대략적인 wireframe을 포함하여 구현 방향을 시각화하고, 선정된 아이디어를 `brain-storm/` 디렉토리에 마크다운으로 저장한다.
Scans codebase to generate grounded feature ideas with ASCII wireframes, saving them as notes in `brain-storm/`. Includes cleanup mode to remove implemented ideas.
Generate and critically evaluate grounded improvement ideas for the current project by scanning the codebase. Use for 'what to improve', 'give ideas', or proactive project direction suggestions.
Guides structured brainstorming to clarify requirements, explore user intent, approaches, trade-offs, and feature scope before implementing components or changes.
Share bugs, ideas, or general feedback.
/writing-specs로 스펙을 작성하기 전 단계. 사용자가 전달한 아이디어를 바탕으로 추가적이고 구체적인 아이디어를 도출한다. 아이디어마다 대략적인 wireframe을 포함하여 구현 방향을 시각화하고, 선정된 아이디어를 brain-storm/ 디렉토리에 마크다운으로 저장한다.
이 스킬은 두 가지 모드로 동작한다. 사용자 요청에 따라 적절한 모드를 선택한다.
brain-storm/ at the project rootbrain-storm/{name}.md or brain-storm/{subdir}/{name}.mdbrain-storm/auth/sso-login.md OK, brain-storm/auth/v2/sso.md NOT OK)dark-mode-toggle.md)First understand the codebase, then generate ideas:
Glob on key directories (src/**, app/**, pages/**, components/**, lib/**, etc.) to map project structureGlob brain-storm/**/*.md to list existing brainstorm ideaspackage.json, README.md, or equivalent to understand tech stackIdeas should be grounded in the actual codebase (reference specific files/patterns), actionable, and varied in scope.
For each selected idea:
Grep across brain-storm/**/*.md for those keywords{path}. 업데이트할까요, 새로 생성할까요, 건너뛸까요?"brain-storm/After writing all idea files, output a summary report directly (no separate file needed):
## Brain Storm Report
| Field | Value |
|-------|-------|
| Action | Created / Updated |
| Ideas Proposed | {count} |
| Ideas Saved | {count} |
### Saved Ideas
| File | Title | Complexity |
|------|-------|-----------|
| `{path}` | {title} | {complexity} |
### Next Steps
- 스펙으로 발전시키려면: /writing-specs {idea title}
The report is part of the final response message, not a separate file. This ensures it always gets delivered.
Triggered by: "브레인스톰 정리", "구현된 아이디어 정리", "clean up brainstorm"
Glob brain-storm/**/*.md to list all idea filesGrep for those keywords in source code (exclude brain-storm/, specs/, node_modules/, .git/)
d. Mark as implemented if 3+ keywords match in source code AND the code actually implements the described functionality (not just naming coincidence or TODOs)## Cleanup Report
| Idea | Status | Evidence |
|------|--------|----------|
| `{path}` | Implemented (deleted) | {matched files} |
| `{path}` | Not implemented (kept) | - |