Brainstorming
A battle-tested Claude Code skill collection that enforces Plan→Execute→Verify→Handoff workflow. Auto-triggers brainstorming, planning, debugging, UI/UX, security, and review skills.
npx -y skills add kjhk3082/master-assistant-skill --skill brainstormingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
[EN] You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation. [KO] 새로운 기능 생성, 컴포넌트 구축 등 창의적인 작업 전에 반드시 사용해야 합니다. 구현 전에 사용자 의도, 요구사항, 설계를 탐색합니다.
SKILL.md
1.9 KB, 331 tokens by cl100k_base, as published. Nobody here has run it
Brainstorming Ideas Into Designs
Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design and get user approval.
<HARD-GATE> Do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until you have presented a design and the user has approved it. This applies to EVERY project regardless of perceived simplicity. </HARD-GATE>Anti-Pattern: "This Is Too Simple To Need A Design"
Every project goes through this process. A todo list, a single-function utility, a config change - all of them. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be short (a few sentences for truly simple projects), but you MUST present it and get approval.
Checklist
You MUST create a task for each of these items and complete them in order:
- Explore project context - check files, docs, recent commits
- Ask clarifying questions - one at a time, understand purpose/constraints/success criteria
- Propose 2-3 approaches - with trade-offs and your recommendation
- Present design - in sections scaled to their complexity, get user approval after each section
- Write design doc - save to
docs/specs/YYYY-MM-DD-<topic>-design.mdand commit - Transition to implementation - invoke planning skill to create implementation plan