Brainstorm
Opinionated engineering pipeline for Claude Code with 10 skills, 5 agents, 2 hooks. Replaces ad-hoc agent sprawl with brainstorm → story → plan → build → review → ship.
npx -y skills add nicodiansk/turbocharge --skill brainstormAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when starting creative work - creating features, building components, adding functionality, or modifying behavior. Explores requirements through Socratic dialogue before any implementation.
SKILL.md
1.8 KB, as published. Nobody here has run it
Brainstorm
Turn ideas into fully formed designs through collaborative dialogue.
Announce: "Using brainstorm to explore this idea before implementation."
The Iron Law
NO IMPLEMENTATION WITHOUT UNDERSTANDING REQUIREMENTS FIRST
Process
1. Understand Context
- Check project state (files, docs, recent commits)
- Read agent memory for relevant prior context
2. Discover Requirements
- Ask questions one at a time
- Prefer multiple choice when possible
- Focus on: purpose, constraints, success criteria, users
- Don't overwhelm — one question per message
3. Explore Approaches
- Propose 2-3 approaches with trade-offs
- Lead with your recommendation and reasoning
- Be ready to combine or discard
4. Present Design
- Break into sections of 200-300 words
- Ask after each section: "Does this look right?"
- Cover: architecture, components, data flow, error handling, testing
- Apply YAGNI — remove unnecessary features
5. Save and Continue
- Write design to
docs/plans/YYYY-MM-DD-<topic>-design.md - Commit the design document
- Offer: "Ready for story breakdown?" → chains to
/turbocharge:story - Or: "Ready for implementation planning?" → chains to
/turbocharge:plan
Red Flags — STOP
| Flag | Problem |
|---|---|
| Jumping to code | Didn't explore requirements |
| Single approach | Didn't propose 2-3 alternatives |
| Wall of text | Present in 200-300 word sections |
| Unanswered questions | Don't design around unknowns |
| No YAGNI review | Remove unnecessary features |
Workflow Position
brainstorm → story → plan → build → review → ship