brainstorming
starsforks
How to install brainstorming?
omnigentx/jarvis/brainstorming
$npx -y skills add omnigentx/jarvis --skill brainstormingStructured approach to explore ideas, clarify requirements, and propose designs before implementation. Use before any creative or planning work.
SKILL.md
| 1 | # Brainstorming Ideas Into Designs |
| 2 | |
| 3 | Inspired by [obra/superpowers](https://github.com/obra/superpowers/tree/main/skills/brainstorming). |
| 4 | |
| 5 | Turn rough ideas into fully-formed designs through structured exploration. |
| 6 | |
| 7 | **Core rule:** Do NOT implement anything until the design is agreed upon. |
| 8 | |
| 9 | ## Process |
| 10 | |
| 11 | ### 1. Understand Context |
| 12 | - Review current project state (files, docs, existing code) |
| 13 | - Assess scope — is this one task or multiple sub-projects? |
| 14 | - If too large, decompose into smaller pieces first |
| 15 | |
| 16 | ### 2. Ask Clarifying Questions |
| 17 | - One question at a time |
| 18 | - Prefer multiple-choice when possible |
| 19 | - Focus on: purpose, constraints, success criteria |
| 20 | |
| 21 | ### 3. Explore Approaches |
| 22 | - Propose 2-3 different approaches with trade-offs |
| 23 | - Lead with your recommendation and explain why |
| 24 | - Be honest about complexity vs. simplicity |
| 25 | |
| 26 | ### 4. Present Design |
| 27 | - Architecture overview |
| 28 | - Components and their responsibilities |
| 29 | - Data flow |
| 30 | - Error handling strategy |
| 31 | - Testing approach |
| 32 | |
| 33 | ### 5. Get Agreement |
| 34 | - Present each section, confirm before moving on |
| 35 | - Be ready to revise based on feedback |
| 36 | - Document the final design |
| 37 | |
| 38 | ## Key Principles |
| 39 | |
| 40 | - **YAGNI ruthlessly** — Remove features that aren't needed yet |
| 41 | - **Explore alternatives** — Always propose 2-3 approaches |
| 42 | - **Incremental validation** — Confirm each section |
| 43 | - **Design for isolation** — Each component should have one clear purpose |
| 44 | - **Smaller units** — Easier to understand, test, and modify |
| 45 | |
| 46 | ## In Multi-Agent Context |
| 47 | |
| 48 | When brainstorming in a meeting: |
| 49 | - Use `speak()` to propose ideas and ask questions |
| 50 | - Wait for other agents' input before finalizing |
| 51 | - Summarize the agreed design before moving to implementation |
People who liked this also viewed
6 picksType
- web-design-guidelinesReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".SkillsJul 2026
- lark-slides飞书幻灯片：创建和编辑幻灯片。创建演示文稿、读取幻灯片内容、管理幻灯片页面（创建、删除、读取、局部替换）。当用户需要创建或编辑幻灯片、读取或修改单个页面时使用。当用户给出 doubao.com 的 /slides/ URL/token 时，也应直接使用本 skill，不要因为域名不是飞书而回退到 WebFetch；路由依据是 URL 路径模式和 token，而不是域名。不负责：云文档内容编辑（走 SkillsJul 2026
- design-taste-frontendTaste-Skill - gives your AI good taste. stops the AI from generating boring, generic slop SkillsJul 2026
- ui-ux-pro-maxUI/UX design intelligence for web and mobile. Searchable local database with 84 styles, 192 color palettes, 74 font pairings, 192 product types, 98 UX guidelines, 104 icon entries, 16 GSAP motion presSkillsJul 2026
- caveman-helpQuick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".SkillsJul 2026
- codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-nSkillsJul 2026
