Brainstorming
- 532 installs
- 29.9k repo stars
- Updated July 27, 2026
- davila7/claude-code-templates
brainstorming is a Claude skill that runs structured dialogue before any creative coding work so developers ship features, components, and behavior changes with agreed purpose, constraints, and a reviewed design.
About
brainstorming is an agent skill from the davila7 Claude Code templates that forces a design conversation before your agent writes code. It treats implementation as the last step: first align on project context, then refine the idea through focused questions—one per turn—about purpose, constraints, and success criteria. When the problem space is clear, it explores two or three architectural approaches with explicit trade-offs and a stated recommendation, then drafts the design in digestible sections so you can correct course early. developers benefit because it prevents expensive rework on features, UI components, integrations, and behavioral tweaks across any stack. Use it whenever the spec lives only in chat, when multiple valid designs exist, or when you want the agent to behave like a patient product partner instead of jumping straight to patches.
- Hard requirement: use before any creative work—features, components, new functionality, or behavior changes
- Inspects current project state (files, docs, recent commits) before asking clarifying questions
- One question per message with preference for multiple-choice when it speeds decisions
- Presents 2–3 approaches with trade-offs, leading with a recommended option and reasoning
- Design delivery in 200–300 word sections with confirmation after each section (architecture, components, data)
Brainstorming by the numbers
- 532 all-time installs (skills.sh)
- Ranked #725 of 3,301 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/davila7/claude-code-templates --skill brainstormingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 532 |
|---|---|
| repo stars | ★ 29.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 27, 2026 |
| Repository | davila7/claude-code-templates ↗ |
How do you design a feature before writing code?
Run structured dialogue before coding so features, components, and behavior changes ship with agreed purpose, constraints, and a reviewed design—not improvised prompts.
Who is it for?
Developers or tech leads starting a new feature, component, or behavior change who want alignment before implementation.
Skip if: Trivial one-line fixes, urgent hotfixes, or tasks where requirements and design are already fully specified.
When should I use this skill?
The user wants to create features, build components, add functionality, or modify behavior without an approved design yet.
What you get
A reviewed design spec with agreed requirements, constraints, and section-by-section developer approval.
- reviewed design spec
- agreed requirements and constraints
By the numbers
- Design sections are presented in 200–300-word blocks with per-section approval
Files
Brainstorming Ideas Into Designs
Overview
Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design in small sections (200-300 words), checking after each section whether it looks right so far.
The Process
Understanding the idea:
- Check out the current project state first (files, docs, recent commits)
- Ask questions one at a time to refine the idea
- Prefer multiple choice questions when possible, but open-ended is fine too
- Only one question per message - if a topic needs more exploration, break it into multiple questions
- Focus on understanding: purpose, constraints, success criteria
Exploring approaches:
- Propose 2-3 different approaches with trade-offs
- Present options conversationally with your recommendation and reasoning
- Lead with your recommended option and explain why
Presenting the design:
- Once you believe you understand what you're building, present the design
- Break it into sections of 200-300 words
- Ask after each section whether it looks right so far
- Cover: architecture, components, data flow, error handling, testing
- Be ready to go back and clarify if something doesn't make sense
After the Design
Documentation:
- Write the validated design to
docs/plans/YYYY-MM-DD-<topic>-design.md - Use elements-of-style:writing-clearly-and-concisely skill if available
- Commit the design document to git
Implementation (if continuing):
- Ask: "Ready to set up for implementation?"
- Use superpowers:using-git-worktrees to create isolated workspace
- Use superpowers:writing-plans to create detailed implementation plan
Key Principles
- One question at a time - Don't overwhelm with multiple questions
- Multiple choice preferred - Easier to answer than open-ended when possible
- YAGNI ruthlessly - Remove unnecessary features from all designs
- Explore alternatives - Always propose 2-3 approaches before settling
- Incremental validation - Present design in sections, validate each
- Be flexible - Go back and clarify when something doesn't make sense
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.645k185kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.547k185k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.466kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).466kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.466kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.465kHow it compares
Use brainstorming for interactive design dialogue when a written PRD already exists and only needs execution.
FAQ
When must brainstorming run in Claude Code?
brainstorming is marked mandatory before creative work—creating features, building components, adding functionality, or modifying behavior—so design and constraints are agreed before any implementation starts.
How does brainstorming present the design?
brainstorming delivers the design in sections of 200–300 words each, checking after every section whether the direction looks right before continuing to the next part of the spec.
Is Brainstorming safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.