davila7/claude-code-templates / cli-tool/components/skills/development/brainstorming
brainstorming
VerifiedYou MUST use this before any creative or build work: creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a website, a talk, a business). Finds out what the user actually wants and why, one question at a time, compares 2-3 approaches and gets a design doc approved before anything is built. Use it even if they never say brainstorm or design; skip it only for fully specified one-line tasks.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 1.0 KB |
| SKILL.md | skill md | 8.8 KB |
| references/builder-check.md | markdown | 1.7 KB |
references/builder-check.md
View on GitHub# Builder check
Run this once the full written design exists (projects only, not small
changes). The goal is to find the places where someone planning from the doc
would have to guess, while the user is still around to answer.
## 1. Get a fresh reader
If you can start a subagent, give it this prompt with the domain and the
document path filled in. Without a subagent, read the document yourself as
that builder, ignoring everything you know from the conversation.
```
You are a talented [DOMAIN, e.g. "software engineer", "event planner"].
You've been handed a design document and asked to plan how to build what it
describes. You cannot talk to the person who wrote it.
Read [DOCUMENT_PATH].
Report only the questions you'd still need answered before you could plan
this well: places where you'd have to guess and a wrong guess would matter.
For each, give the question and why the answer changes the plan. Rank them
by importance.
Skip anything the document explicitly leaves to the builder, anything you
could reasonably decide yourself, and wording nitpicks.
If nothing important is left, say "nothing important left".
```
## 2. Sort what comes back
- **Answered already** by the conversation or the project: put the answer in
the document.
- **Minor:** a sensible builder could settle it without changing what gets
built. Settle it and mark it in the document as your call.
- **Theirs:** only the user can answer it, and the answer changes what gets
built.
## 3. One round with the user
Bring the "theirs" pile in a single message, most important first. Update the
document with their answers, then hand it over with a short list of the calls
you made so they can check those while reading. That is the only round of
questions the check produces.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |