brainstorming
A planning skill for brainstorming solutions, comparing architecture, and building consensus before writing code.
Install
mkdir -p .claude/skills/brainstorming-anoopkarnik && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12533" && unzip -o skill.zip -d .claude/skills/brainstorming-anoopkarnik && rm skill.zipInstalls to .claude/skills/brainstorming-anoopkarnik
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use this skill when the user asks to brainstorm, explore approaches, design architecture, compare options, or plan before implementation.Key capabilities
- →Understand the repository context
- →Identify relevant files and architecture boundaries
- →Provide 2-4 viable approaches
- →Explain tradeoffs honestly
- →Recommend one approach
- →Create a concrete implementation checklist
How it works
The skill first understands the problem and repository context, then identifies relevant files and architecture boundaries. It generates multiple approaches with tradeoffs, recommends one, and provides an implementation checklist.
Inputs & outputs
When to use brainstorming
- →Brainstorming feature approaches
- →Comparing architecture designs
- →Planning complex tasks
About this skill
Brainstorming Skill
Use this skill when the user asks to brainstorm, explore approaches, design architecture, compare options, or plan before implementation.
Rules
- Do not edit files unless the user explicitly approves implementation.
- Do not run destructive commands.
- First understand the repo context.
- Identify relevant files and architecture boundaries.
- Give 2–4 viable approaches.
- Explain tradeoffs honestly.
- Recommend one approach.
- End with a concrete implementation checklist.
- Ask for approval before coding.
Output format
Understanding
Summarize the problem.
Options
Compare possible solutions.
Recommendation
Pick one and explain why.
Implementation plan
List steps and likely files.
Risks
Mention edge cases and unknowns.
Approval
Ask whether to implement.
When not to use it
- →When the user explicitly approves implementation without prior planning
- →When running destructive commands
- →When the user is not asking to brainstorm, explore approaches, design architecture, compare options, or plan before implementation
Limitations
- →Does not edit files unless the user explicitly approves implementation
- →Does not run destructive commands
How it compares
This workflow provides a structured output format including options, recommendations, and an implementation plan, which is more detailed than a casual brainstorming session.
Compared to similar skills
brainstorming side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| brainstorming (this skill) | 0 | 2mo | No flags | Beginner |
| create-plan | 36 | 8mo | Review | Beginner |
| project-planner | 32 | 9mo | Review | Intermediate |
| system-design | 19 | 9mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
create-plan
antinomyhq
Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.
system-design
lagz0ne
Use when designing, architecting, or planning a new system from requirements or ideas - transforms concepts into navigable design catalog using EventStorming methodology, Mermaid diagrams, and progressive elaboration through 5 phases (Requirements, Big Picture, Processes, Data/Flows, Integration)
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
sparc-methodology
ruvnet
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
spec-workflow
TencentCloudBase
Standard software engineering workflow for requirement analysis, technical design, and task planning. Use this skill when developing new features, complex architecture designs, multi-module integrations, or projects involving database/UI design.