Smithery Logo
MCPsSkillsDocsPricing
Login
Smithery Logo

Accelerating the Agent Economy

Resources

DocumentationPrivacy PolicySystem Status

Company

PricingAboutBlog

Connect

© 2026 Smithery. All rights reserved.

    asadullah48

    brainstorming

    asadullah48/brainstorming
    Planning
    1
    1 installs

    About

    SKILL.md

    Install

    Install via Skills CLI

    or add to your agent
    • Claude Code
      Claude Code
    • Codex
      Codex
    • OpenClaw
      OpenClaw
    • Cursor
      Cursor
    • Amp
      Amp
    • GitHub Copilot
      GitHub Copilot
    • Gemini CLI
      Gemini CLI
    • Kilo Code
      Kilo Code
    • Junie
      Junie
    • Replit
      Replit
    • Windsurf
      Windsurf
    • Cline
      Cline
    • Continue
      Continue
    • OpenCode
      OpenCode
    • OpenHands
      OpenHands
    • Roo Code
      Roo Code
    • Augment
      Augment
    • Goose
      Goose
    • Trae
      Trae
    • Zencoder
      Zencoder
    • Antigravity
      Antigravity
    ├─
    ├─
    └─

    About

    Use when the user presents an idea, feature request, or problem that needs exploration before implementation - facilitates collaborative ideation through structured questioning and approach evaluation

    SKILL.md

    Brainstorming Ideas Into Designs

    Overview

    Transform ideas into comprehensive designs through structured dialogue.

    Core principle: Progressive refinement through targeted questions, then present approaches with trade-offs.

    Announce at start: "I'm using the brainstorming skill to explore this idea."

    The Process

    Phase 1: Understanding the Idea

    1. Assess current state - What exists today?
    2. Ask clarifying questions - One at a time, prefer multiple choice
    3. Refine progressively - Each answer narrows scope

    Question patterns:

    • "What problem does this solve?"
    • "Who is the primary user?"
    • "What are the constraints?"
    • "What does success look like?"

    Phase 2: Exploring Approaches

    Present 2-3 approaches with trade-offs:

    • Lead with recommended option
    • Explain rationale clearly
    • Show contrast between options

    Phase 3: Presenting Design

    Break into sections of 200-300 words:

    • Architecture
    • Components
    • Data flow
    • Error handling
    • Testing approach

    Validate after each section.

    After the Design

    Documentation:

    • Write to docs/plans/YYYY-MM-DD-<feature-name>.md
    • Commit to git

    Implementation:

    • Confirm readiness
    • Use appropriate skills for execution

    Key Principles

    • One question at a time (avoid overwhelm)
    • Prefer multiple choice options
    • YAGNI: ruthlessly remove unnecessary features
    • Validate incrementally

    Red Flags - STOP

    • Skipping questioning phase
    • Presenting single approach only
    • Assuming requirements without validation
    • Over-engineering features not needed
    Recommended Servers
    Thoughtbox
    Thoughtbox
    Miro
    Miro
    Confluence
    Confluence
    Repository
    asadullah48/hackathon-skills-marketplace
    Files