mcpField
B
brainstorming

brainstorming

github.com/mavscuiAgent workflows19360 installsUpdated 33w ago
Repository

About brainstorming

brainstorming is an Agent skill for developing ideas into validated designs and specifications through structured dialogue. It suits people planning a project, guiding them through context gathering, alternative approaches and incremental design review.

Key features

  1. 01Review project files, documents and commits
  2. 02Ask focused questions one at a time
  3. 03Compare two or three approaches and trade-offs
  4. 04Present and validate designs in sections
  5. 05Document approved designs in a dated file
  6. 06Prepare an implementation plan when requested

Use cases

  1. 01Clarifying goals and constraints for a new project
  2. 02Comparing architecture options before choosing
  3. 03Reviewing a design incrementally with stakeholders
  4. 04Recording an agreed design before implementation

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mavscui/agent-skills-hunter --skill brainstorming

After installing, type/brainstormingin Claude Code to confirm it loaded.

Details

From the project README

Brainstorming Ideas Into Designs

Overview

Help turn ideas into fully formed designs and specs through natural collaborative dialogue.

Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design in small sections (200-300 words), checking after each section whether it looks right so far.

The Process

Understanding the idea:

  • Check out the current project state first (files, docs, recent commits)
  • Ask questions one at a time to refine the idea
  • Prefer multiple choice questions when possible, but open-ended is fine too
  • Only one question per message - if a topic needs more exploration, break it into multiple questions
  • Focus on understanding: purpose, constraints, success criteria

Exploring approaches:

  • Propose 2-3 different approaches with trade-offs
  • Present options conversationally with your recommendation and reasoning
  • Lead with your recommended option and explain why

Presenting the design:

  • Once you believe you understand what you're building, present the design
  • Break it into sections of 200-300 words
  • Ask after each section whether it looks right so far
  • Cover: architecture, components, data flow, error handling, testing
  • Be ready to go back and clarify if something doesn't make sense

After the Design

Documentation:

  • Write the validated design to docs/plans/YYYY-MM-DD-<topic>-design.md
  • Use elements-of-style:writing-clearly-and-concisely skill if available
  • Commit the design document to git

Implementation (if continuing):

  • Ask: "Ready to set up for implementation?"
  • Use superpowers:using-git-worktrees to create isolated workspace
  • Use superpowers:writing-plans to create detailed implementation plan

Key Principles

  • One question at a time - Don't overwhelm with multiple questions
  • Multiple choice preferred - Easier to answer than open-ended when possible
  • YAGNI ruthlessly - Remove unnecessary features from all designs
  • Explore alternatives - Always propose 2-3 approaches before settling
  • Incremental validation - Present design in sections, validate each
  • Be flexible - Go back and clarify when something doesn't make sense

Comments

Markdown supported