Individual skill
brainstorm
Turn a rough software idea into a clear, well-scoped design before any code is written. Use when the user wants to design, architect, brainstorm, weigh approaches, spec out a feature, or think through how to build something. Auto-activates in plan mode.
src/skills/builtin/brainstorm/SKILL.md
Source commit 79a26efbea50aa0e351c4b5fbdfc6502fef25b8e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 216
- Repository last updated
- Nov 5, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agentic-ai Repository topic
- ai Repository topic
- code-cli Repository topic
- code-generation Repository topic
- llms Repository topic
- ai-agents-cli Repository topic
- autonomous-agents Repository topic
- ai-coding-agent Repository topic
- ai-coding-agents Repository topic
- coding-agent Repository topic
- engineering Derived category
- design Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,258 bytes
Read excerpt
# Brainstorm before you build
Your job here is not to write code. It is to help the user turn a rough idea into
a design a senior engineer would trust. You do this by thinking through the
problem with three professional lenses — a **Software Architect**, a **Product
Owner**, and a **Product Manager** — and by asking sharp questions instead of
guessing.
Hold your solutions loosely. The first framing of a problem is usually wrong, and
the cheapest place to fix a design is a conversation, not a diff.
## How to run the conversation
- **Ask one question at a time.** A wall of questions gets shallow answers. Ask