superpowers-brainstorm
Generates a structured plan including goals, risks, options, and acceptance criteria for technical tasks.
Install
mkdir -p .claude/skills/superpowers-brainstorm && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3164" && unzip -o skill.zip -d .claude/skills/superpowers-brainstorm && rm skill.zipInstalls to .claude/skills/superpowers-brainstorm
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.
Produces a structured brainstorm: goals, constraints, risks, options, recommendation, and acceptance criteria. Use before non-trivial implementation or design changes.Key capabilities
- →Define implementation goals
- →Identify technical constraints and risks
- →Compare multiple implementation options
- →Establish verifiable acceptance criteria
How it works
It enforces a standardized template requiring goals, constraints, risks, options, and acceptance criteria before any code is written.
Inputs & outputs
When to use superpowers-brainstorm
- →Planning a major refactor
- →Defining acceptance criteria for a feature
- →Analyzing technical risks before implementation
About this skill
Brainstorm Skill
When to use this skill
- before implementing non-trivial features
- before refactors with unclear scope
- before debugging complex issues
- before designing an automation workflow
Brainstorm template (use this exact structure)
Goal
- (1–2 sentences)
Constraints
- (tech stack, time, compatibility, performance, “must not change”, etc.)
Known context
- (what exists today; relevant files/components; current behavior)
Risks
- (security, data loss, regressions, surprising side effects)
Options (2–4)
For each option include:
- Summary
- Pros / cons
- Complexity / risk
Recommendation
- Pick one option and explain why
Acceptance criteria
- Bullet list of verifiable outcomes
When not to use it
- →Trivial implementation tasks
- →Tasks without technical uncertainty
Limitations
- →Requires 2-4 distinct options for analysis
- →Must follow the exact provided structure
How it compares
It forces a formal evaluation of multiple options and risks rather than jumping directly into a single implementation strategy.
Compared to similar skills
superpowers-brainstorm side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| superpowers-brainstorm (this skill) | 9 | 6mo | No flags | Beginner |
| brainstorming | 93 | 4mo | Review | Beginner |
| create-plan | 36 | 8mo | Review | Beginner |
| project-planner | 32 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by anthonylee991
View all by anthonylee991 →You might also like
brainstorming
obra
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
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.
confidence-check
SuperClaude-Org
Pre-implementation confidence assessment (≥90% required). Use before starting any implementation to verify readiness with duplicate check, architecture compliance, official docs verification, OSS references, and root cause identification.
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).