e2ec-it/sp-brainstorming
crush/skills/sp-brainstorming/SKILL.md
SUPERPOWERS-style brainstorming: MUST run before implementing features/behavior changes. Clarify intent, propose options, present design, get approval.
data-ai
Updated Apr 21, 2026
$ install --global
skillsauthnpx skillsauth add e2ec-it/pub-xifan-crush-best-practices sp-brainstormingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 21, 2026, 6:31 PM131.2s1 file scanned
SKILL.md
- name:
- sp-brainstorming
- description:
- SUPERPOWERS-style brainstorming: MUST run before implementing features/behavior changes. Clarify intent, propose options, present design, get approval.
Superpowers: Brainstorming (Crush Adaptation)
Based on obra/superpowers brainstorming skill. (MIT)
Upstream reference: skills/brainstorming/SKILL.md
Rules
- Do not write production code or change files until a design is presented and the user approves it.
- Ask one clarifying question per message.
- Always propose 2–3 approaches with tradeoffs and a recommendation.
Checklist (do in order)
- Explore repo context (read relevant files/docs; check conventions).
- Ask clarifying questions (one at a time) until constraints + success criteria are clear.
- Propose 2–3 approaches with tradeoffs; recommend one.
- Present the design in sections (architecture/components/data flow/errors/testing). Ask for approval after each section.
- Save a design note to
docs/plans/YYYY-MM-DD--design.md(or your repo's convention) and commit. - Transition to sp-writing-plans to produce a task-by-task implementation plan.
Terminal state
The only valid next skill after this is sp-writing-plans.
Related Skills
e2ec-it/sp-writing-plans
content-media
VerifiedTrustedCommunity
SUPERPOWERS-style implementation planning: turn an approved design into 2–5 minute tasks with exact file paths, commands, verifications, and frequent commits.
SKILL.mdUpdated Apr 21, 2026
e2ec-it/sp-tdd
development
VerifiedTrustedCommunity
SUPERPOWERS TDD enforcement: NO production code without a failing test first. Delete code written before tests.
SKILL.mdUpdated Apr 21, 2026
e2ec-it/sp-subagent-dev
development
VerifiedTrustedCommunity
Execute plan per task with role separation and review loops (spec then quality). In Crush, simulate subagents via role prompts / new sessions.
SKILL.mdUpdated Apr 21, 2026
e2ec-it/sp-request-code-review
development
VerifiedTrustedCommunity
Request review between tasks and before merge. Use git SHAs to scope changes and produce actionable findings.
SKILL.mdUpdated Apr 21, 2026