Brainstorming (Idea → Design Spec)
Forces a collaborative requirements interview, 2–3 alternative designs, and a committed spec document before any code is written.
Dev & CodingBeginner★ 1,652⑂ 239AI score 10/10Last updated: Aug 13, 2026
What it does
- Applies a hard gate: no code, no scaffolding, no implementation until you approve the design — even for "simple" projects.
- Explores project context (files, docs, recent commits), then asks one question at a time, preferring multiple-choice, focused on purpose, constraints, and success criteria.
- Always proposes 2–3 approaches with trade-offs and a recommendation stated first with reasoning.
- Presents the design section by section (architecture, components, data flow, error handling, testing) and confirms each section with you.
- Writes the approved spec to
docs/specs/YYYY-MM-DD-<topic>-design.md, commits it, then self-reviews for placeholders, contradictions, ambiguity, and scope creep. - Flags oversized requests and helps split them into sub-projects, each with its own spec → plan → implement loop.
- Offers a browser-based visual companion just-in-time, only when a question is genuinely visual.
Who it's for
- Anyone who has wasted work because the agent started coding on unverified assumptions.
- Solo devs and small teams who want consistent design docs without inventing a template each time.
- People scoping a large feature before handing it to an AI agent.
Example uses
- "Brainstorm an internal document search bot" → sequential questions about data sources and quality bar, then three architectures compared with a recommendation.
- "Build a platform with chat, file storage, billing, and analytics" → immediately calls out that it's too large for one spec and proposes a decomposition order.
- Choosing between two onboarding wizard layouts → sends a standalone message offering to open mockups in a browser tab.
Note: the skill body is written in Chinese, though Claude will converse in your language. By design it is not for bug fixes, config changes, or tasks with an obvious implementation path.
· · · Install guide · · ·
Try it now, no install
Paste this into Claude to use the skill without installing anything.
Read the instructions in this file and follow them to help me: https://raw.githubusercontent.com/feiskyer/claude-code-settings/HEAD/skills/brainstorming/SKILL.md What I want: (describe your task here)
If Claude can't open the link, open it yourself and paste the contents instead.
↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.
Install in the Claude app (no terminal)
- Download the ZIP with the button below.
- In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
- Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
Install in Claude Code
Let Claude do it — paste this into Claude Code
Install the skill I found on Claude Skill Mart. Copy the skills/brainstorming folder from the GitHub repo feiskyer/claude-code-settings into my ~/.claude/skills/brainstorming/. When it's done, tell me in one line what this skill can do.
Install with a command instead
git clone https://github.com/feiskyer/claude-code-settings.git && mkdir -p ~/.claude/skills && cp -r claude-code-settings/skills/brainstorming ~/.claude/skills/⚠ This is a third-party skill. Check the source repository before installing.
- Open a terminal (Terminal on macOS/Linux, PowerShell or WSL on Windows).
- Clone the repo:
git clone https://github.com/feiskyer/claude-code-settings.git - Create the skills directory:
mkdir -p ~/.claude/skills - Copy just this skill:
cp -r claude-code-settings/skills/brainstorming ~/.claude/skills/ - Verify the companion files came along:
ls ~/.claude/skills/brainstorming(expectvisual-companion.mdandspec-document-reviewer-prompt.md). - Restart Claude Code and say something like "use the brainstorming skill to design feature X".
- Run it inside a git repository, since the design doc is saved and committed under
docs/specs/.
View source on GitHub ↗License: MIT