Brainstorm
- 944 installs
- 1.3k repo stars
- Updated July 26, 2026
- neolabhq/context-engineering-kit
brainstorm is a Claude skill that turns rough feature ideas into structured, validated designs through guided one-question-at-a-time dialogue before any code or detailed implementation plans are written.
About
brainstorm is a context-engineering-kit Claude skill for refining rough ideas into fully formed designs and specifications through collaborative dialogue. It starts by understanding current project context, asks questions one at a time to narrow scope, explores alternatives, and incrementally validates assumptions before presenting a design. The skill accepts an optional initial feature concept, topic, or draft specification file as an argument hint. Developers reach for brainstorm when a feature idea is still vague, when they need structured discovery before writing code or implementation plans, and explicitly not during mechanical execution tasks where requirements are already clear and implementation steps are predetermined.
- Begins by analyzing current project state including files, docs, and recent commits
- Asks one question at a time to refine purpose, constraints, and success criteria
- Generates 6 distinct approaches each with explicit trade-offs and numeric probabilities
- Presents design in 200-300 word sections with confirmation after each
- Explicitly avoids mechanical implementation tasks once direction is clear
Brainstorm by the numbers
- 944 all-time installs (skills.sh)
- +52 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #495 of 3,301 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/neolabhq/context-engineering-kit --skill brainstormAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 944 |
|---|---|
| repo stars | ★ 1.3k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 26, 2026 |
| Repository | neolabhq/context-engineering-kit ↗ |
How do you refine vague feature ideas before coding?
Turn vague feature ideas into structured, validated designs through guided collaborative dialogue before committing to code or detailed plans.
Who is it for?
Developers or tech leads with early-stage feature ideas who need structured discovery dialogue before committing to code or detailed plans.
Skip if: Mechanical implementation tasks where requirements are already defined and only execution remains.
When should I use this skill?
The user has a rough feature idea and wants collaborative questioning to shape a design before any code or implementation plan is written.
What you get
A validated feature design, explored alternatives log, and structured specification ready for implementation planning.
- Validated feature design
- Structured specification draft
By the numbers
- Uses one-question-at-a-time dialogue pattern for incremental validation
Files
Brainstorming Ideas Into Designs
Overview
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 in small sections (200-300 words), checking after each section whether it looks right so far.
The Process
Understanding the idea:
- Check out the current project state first (files, docs, recent commits)
- Ask questions one at a time to refine the idea
- Prefer multiple choice questions when possible, but open-ended is fine too
- Only one question per message - if a topic needs more exploration, break it into multiple questions
- Focus on understanding: purpose, constraints, success criteria
Exploring approaches:
- Generate 6 possible approaches with trade-offs. Approaches should each include a text and a numeric probability. Please sample responses at random from the [full distribution / tails of the distribution], in such way that:
- For first 3 responses aim for high probability, over 0.80
- For last 3 responses aim for diversity - explore different regions of the solution space, such that the probability of each response is less than 0.10
- Present options conversationally with your recommendation and reasoning
- Lead with your recommended option and explain why
Presenting the design:
- Once you believe you understand what you're building, present the design
- Break it into sections of 200-300 words
- Ask after each section whether it looks right so far
- Cover: architecture, components, data flow, error handling, testing
- Be ready to go back and clarify if something doesn't make sense
After the Design
if user provided draft specification file, then update it directly, if not then use /add-task skill to create task file for target approach
Important: In specification file, write target approach in sections, in ## Initial User Prompt -> ### Requirements section, before ## Description section. Description will be filled in future stage.
After filling task file, suggest use to run /clear and then /plan-task <task-file-path> to refine the task file.
Key Principles
- One question at a time - Don't overwhelm with multiple questions
- Multiple choice preferred - Easier to answer than open-ended when possible
- YAGNI ruthlessly - Remove unnecessary features from all designs
- Explore alternatives - Always propose 2-3 approaches before settling
- Incremental validation - Present design in sections, validate each
- Be flexible - Go back and clarify when something doesn't make sense
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.645k185kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.547k185k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.466kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).466kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.466kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.465kHow it compares
Pick brainstorm over implementation skills when the problem is unclear scope, not missing code patterns.
FAQ
When should developers use brainstorm?
brainstorm fits before writing code or implementation plans when a feature concept is still rough. The skill asks questions one at a time, explores alternatives, and validates assumptions to produce a formed design rather than jumping to execution.
What does brainstorm produce?
brainstorm delivers a fully formed feature design and specification through collaborative dialogue. It starts from project context and optional initial concept input, then incrementally narrows scope until the design is ready for planning.
Is Brainstorm safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.