mcpField
B
brainstorming

brainstorming

github.com/mosif16Agent workflows1836 installsUpdated 48w ago
Repository

About brainstorming

brainstorming is an Agent skill for turning early ideas into designs and specifications through questions and incremental validation. It is suited to projects that need to clarify goals, constraints, and trade-offs before implementation.

Key features

  1. 01Checks the current project state
  2. 02Clarifies goals and constraints one question at a time
  3. 03Compares 2–3 approaches and trade-offs
  4. 04Presents and validates designs in sections
  5. 05Writes the design to a plan document

Use cases

  1. 01Turn an initial idea into a design specification
  2. 02Compare architecture options before coding
  3. 03Validate each part of a design incrementally

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mosif16/codex-skills --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