skills sourced live from GitHub · all skills listed are free · each skill is provided under its author's license.
home / Productivity / Brainstorming Skill by @obra
The skill is the skills/brainstorming folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.
A discipline for agents to use before creative work: establish shared understanding of intent, requirements and design before implementing. It offers three paths and warns against skipping design because something looks too simple.
The original SKILL.md is organised into these sections:
Written and maintained by @obra. It is published under the MIT license, which allows reuse with attribution. See the author profile. SkillDirectory does not claim authorship: this page adds our own review and links back to the original, and the skill's text belongs to its author.
------|---------| | "This is too simple to need a design" | Follow the selected path: a bounded change gets a short chat design; an architectural change gets the written spec and planning handoffs. | | "I'll call it bounded and skip the spec" | Reaching for a label to skip work IS the doubt — take the heavier path. | | "It's bounded and the design is obvious — I'll start while they read it" | The gate is the approval, not the design's length. Present, then stop until you hear yes. | | "I understand this kind of app, so it's bounded" | Bounded measures the repo, not your familiarity. A new project has no existing flow — it is architectural. | | "The spike works, so I'll keep the code" | A spike's output is an answer. Keeping the code is a new request — classify it. | | "It grew, but I'm almost done — no need to re-classify" | Hidden complexity upgrades the path mid-task. Stop and say so. | …
Excerpt only, quoted from the author's repository. Open the repository for the complete file.