mcpField
B
brainstorming

brainstorming

github.com/hjewkesAgent workflows448 installsUpdated 36w ago
Repository

About brainstorming

brainstorming is a skill for turning ideas into designs and specifications through collaborative dialogue. It guides project exploration, clarifying questions, approach comparison, design approval, and transition to implementation planning.

Key features

  1. 01Explore project context before design
  2. 02Ask clarifying questions one at a time
  3. 03Compare multiple approaches and trade-offs
  4. 04Present designs for approval before implementation
  5. 05Create a design document and implementation plan

Use cases

  1. 01Clarifying requirements for a new project
  2. 02Comparing design options before implementation
  3. 03Getting design approval before any coding begins

Install

Copy the command and run it in a terminal.

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

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

Bundled files

References and scripts installed along with SKILL.md.

references/
debugging-principles.md
detailed-process.md
tdd-principles.md
verification-principles.md

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 and get user approval.

Do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until you have presented a design and the user has approved it. This applies to EVERY project regardless of perceived simplicity.

Anti-Pattern: "This Is Too Simple To Need A Design"

Every project goes through this process. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be short, but you MUST present it and get approval.

Checklist

You MUST create a task for each of these items and complete them in order:

  1. Explore project context — check files, docs, recent commits
  2. Ask clarifying questions — one at a time, understand purpose/constraints/success criteria
  3. Propose 2-3 approaches — with trade-offs and your recommendation
  4. Present design — in sections scaled to their complexity, including test strategy, error handling approach, and verification criteria (see Quality Principles below), get user approval after each section
  5. Write design doc — save to .claude/plans/YYYY-MM-DD-<topic>-design.md and commit
  6. Transition to implementation — invoke writing-plans skill to create implementation plan

Quality Principles

Plans produced by this skill should address these concerns at design time:

Process Flow

digraph brainstorming {
    "Explore project context" [shape=box];
    "Ask clarifying questions" [shape=box];
    "Propose 2-3 approaches" [shape=box];
    "Present design sections" [shape=box];
    "User approves design?" [shape=diamond];
    "Write design doc" [shape=box];
    "Invoke writing-plans skill" [shape=doublecircle];

    "Explore project context" -> "Ask clarifying questions";
    "Ask clarifying questions" -> "Propose 2-3 approaches";
    "Propose 2-3 approaches" -> "Present design sections";
    "Present design sections" -> "User approves design?";
    "User approves design?" -> "Present design sections" [label="no, revise"];
    "User approves design?" -> "Write design doc" [label="yes"];
    "Write design doc" -> "Invoke writing-plans skill";
}

The terminal state is invoking writing-plans. Do NOT invoke frontend-design, mcp-builder, or any other implementation skill.

For detailed process steps (questioning technique, design presentation, documentation, key principles), see references/detailed-process.md.

Comments

Markdown supported