Brainstorming
Design-first approach that generates and evaluates multiple alternatives before coding
Install
npx skills add 0xranx/agentbrief --skill brainstorminggit clone --depth 1 https://github.com/0xranx/agentbrief.git /tmp/agentbrief
mkdir -p ~/.claude/skills
cp -r /tmp/agentbrief/briefs/growth-engineer/skills/brainstorming ~/.claude/skills/brainstormingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
> Methodology from [obra/superpowers](https://github.com/obra/superpowers) (MIT) # Brainstorming & Design-First Hard gate: **no code before design approval.** ## Phase 1 -- Understand the Problem 1. Clarify the user's goal. Ask "what problem does this solve?" not "what should I build?" 2. Identify constraints: timeline, tech stack, existing patterns, user expectations. 3. Define success criteria -- how will we know this is done and done well? 4. List non-goals explicitly to prevent scope creep. ## Phase 2 -- Generate Alternatives 1. Propose 2-3 distinct approaches. Not variations of one idea -- genuinely different strategies. 2. For each approach, describe: - **How it works** (one paragraph, plain language). - **Pros** -- what it does well. - **Cons** -- what it does poorly or makes harder. - **Effort** -- rough size (small / medium / large). 3. Highlight the trade-offs between approaches, not just feature lists. ## Phase 3 -- Decide 1. Present the alternatives to the user (or evaluate against success criteria if working solo). 2. Recommend one approach with a clear rationale. 3. Wait for approval before writing any code. 4. If the user picks a different option, adopt it fully -- do not smuggle in your preference. ## Phase 4 -- Apply YAGNI Ruthlessly 1. Before adding any feature, ask: "Is this needed right now, or might it be needed someday?" 2. If "someday", cut it. You can add it later when the need is real.
Details
- Skill name
brainstorming- Repository
- 0xranx/agentbrief
- Path
briefs/growth-engineer/skills/brainstorming/SKILL.md- License
- MIT
- Repo updated
- 28 March 2026
FAQ
What does the Brainstorming skill do?
Design-first approach that generates and evaluates multiple alternatives before coding
How do I install the Brainstorming skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add 0xranx/agentbrief --skill brainstorming. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Brainstorming popular?
It lives in 0xranx/agentbrief, which has 43 GitHub stars and 0 forks.
Related skills
Typescript Advanced Types
430xranx/agentbrief
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.
Analytics Setup
430xranx/agentbrief
When the user needs to set up product analytics, event tracking, or says 'set up analytics,' 'add tracking,' 'GA4,' 'Mixpanel,' 'PostHog,' 'Amplitude,' 'what events should we track,' 'conversion tracking,' 'funnel tracking,' or is launching a product and needs to instrument it for data collection.
API Documentation
430xranx/agentbrief
Create comprehensive API documentation for developers. Use when documenting REST APIs, GraphQL schemas, or SDK methods. Handles OpenAPI/Swagger, interactive docs, examples, and API reference guides.
Doubt Driven Development
48frankxai/claude-skills-library
Cross-examine a non-trivial decision with a fresh, adversarial reviewer before it stands, ideally a different model family. Use before committing branching logic, a boundary change, a safety or idempotence claim, an irreversible step (deploy, migration, merge, public claim), or any confident statement that is cheaper to disprove now than to debug later.
Architecture Review
430xranx/agentbrief
When reviewing code that involves architectural decisions, new modules, data flow changes, or system design. Use when the PR introduces new services, changes API boundaries, modifies database schemas, adds new dependencies, or restructures significant portions of the codebase. Also use when the user says 'review the architecture,' 'is this the right approach,' or 'design review.
Feynman Thinking
48frankxai/claude-skills-library
Explains a software architecture, algorithm, or control flow in plain language, using a mental model (inputs, transformation, outputs), a text or ASCII flow diagram, and Socratic questions that expose hidden assumptions, then flags needless abstraction. Use when the user asks to explain something simply, "Feynman style", to build a mental model of a system, to explain an architecture to a junior developer, or to challenge a design for over-engineering. Do not use for mechanical edits (renames, typo fixes, formatting, format conversions), boilerplate config, or when the user asks for code only
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.