superpowers brainstorm
- Repo stars 774
- Author repo gemini-superpowers-antigravity
- Domain
- Design
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @anthonylee991 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# 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
Sections and files
Listed in source order.
sections -> When to use this skill → Brainstorm template (use this exact structure) → Goal → Constraints → Known context → Risks
terms -> No English key terms available
files/cmd -> files/components
body sha256 -> 74e976472fca
When to use this skill
before implementing non-trivial features before refactors with unclear scope before debugging complex issues before designing an automation workflow
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)