MCPInstall

brainstorm-diverge-converge

Applies structured divergent-convergent thinking to generate many creative options, organize them into meaningful clusters, then systematically evaluate and narrow to the strongest choices. Balances creative exploration with disciplined decision-making. Use when exploring product ideas, solving open-ended problems, generating strategic alternatives, developing research questions, designing experiments, or when user mentions brainstorming, ideation, divergent thinking, generating options, or evaluating alternatives.

Installs
148
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/lyndonkl/claude --skill brainstorm-diverge-converge
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads brainstorm-diverge-converge automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Brainstorm Diverge-Converge

Table of Contents

Three phases: Diverge (generate many ideas without judgment), Cluster (group into themes), Converge (evaluate against criteria and select).

Quick Example:

# Problem: How to improve customer onboarding?

## Diverge (30 ideas)
- In-app video tutorials
- Interactive walkthroughs
- Email drip campaign
- Live webinar onboarding
- 1-on-1 concierge calls
- ... (25 more ideas)

## Cluster (6 themes)
1. **Self-serve content** (videos, docs, tooltips)
2. **Interactive guidance** (walkthroughs, checklists)
3. **Human touch** (calls, webinars, chat)
4. **Motivation** (gamification, progress tracking)
5. **Timing** (just-in-time help, preemptive)
6. **Social** (community, peer examples)

## Converge (Top 3)
1. Interactive walkthrough (high impact, medium effort) - 8.5/10
2. Email drip campaign (medium impact, low effort) - 8.0/10
3. Just-in-time tooltips (medium impact, low effort) - 7.5/10

Workflow

Copy this checklist and track your progress:

Brainstorm Progress:
- [ ] Step 1: Gather requirements
- [ ] Step 2: Diverge (generate ideas)
- [ ] Step 3: Cluster (group themes)
- [ ] Step 4: Converge (evaluate and select)
- [ ] Step 5: Document and validate

Step 1: Gather requirements

Clarify topic/problem (what are you brainstorming?), goal (what decision will this inform?), constraints (must-haves, no-gos, boundaries), evaluation criteria (what makes an idea "good" - impact, feasibility, cost, speed, risk, alignment), target quantity (suggest 20-50 ideas), and rounds (single session or multiple rounds, default: 1).

Step 2: Diverge (generate ideas)

Generate 20-50 ideas without judgment or filtering. Suspend criticism (all ideas valid during divergence), aim for quantity and variety (different types, scales, approaches), and use creative prompts: "What if unlimited resources?", "What would competitor do?", "Simplest approach?", "Most ambitious?", "Unconventional alternatives?". Output: Numbered list of raw ideas. For simple topics → generate directly. For complex topics → Use resources/template.md for structured prompts.

Step 3: Cluster (group themes)

Organize ideas into 4-8 distinct clusters by identifying patterns, creating categories (mechanism, user/audience, timeline, effort, risk, strategic objective), naming clusters clearly, and checking coverage (distinct approaches). Fewer than 4 = not enough variety, more than 8 = too fragmented. Output: Ideas grouped under cluster labels.

Step 4: Converge (evaluate and select)

Define criteria (from step 1), score ideas on criteria (1-10 or Low/Med/High scale), rank by total/weighted score, select top 3-5 options, and document tradeoffs (why chosen, what deprioritized). Evaluation patterns: Impact/Effort matrix, weighted scoring, must-have filtering, pairwise comparison. See Common Patterns for domain-specific approaches.

Step 5: Document and validate

Create brainstorm-diverge-converge.md with: problem statement, diverge (full list), cluster (organized themes), converge (scored/ranked/selected), and next steps. Validate using resources/evaluators/rubric_brainstorm_diverge_converge.json: verify 20+ ideas with variety, distinct clusters, explicit criteria, consistent scoring, top selections clearly better, actionable next steps. Minimum standard: Score ≥ 3.5.

Common Patterns

For product/feature ideation:

  • Diverge: 30-50 feature ideas
  • Cluster by: User need, use case, or feature type
  • Converge: Impact vs. effort scoring
  • Select: Top 3-5 for roadmap

For problem-solving:

  • Diverge: 20-40 solution approaches
  • Cluster by: Mechanism (how it solves problem)
  • Converge: Feasibility vs. effectiveness
  • Select: Top 2-3 to prototype

For research questions:

  • Diverge: 25-40 potential questions
  • Cluster by: Research method or domain
  • Converge: Novelty, tractability, impact
  • Select: Top 3-5 to investigate

For strategic planning:

  • Diverge: 20-30 strategic initiatives
  • Cluster by: Time horizon or strategic pillar
  • Converge: Strategic value vs. resource requirements
  • Select: Top 5 for quarterly planning

Guardrails

Do:

  • Generate at least 20 ideas in diverge phase (quantity matters)
  • Suspend judgment during divergence (criticism kills creativity)
  • Create distinct clusters (avoid overlap and confusion)
  • Use explicit, relevant criteria for convergence (not vague "goodness")
  • Score consistently across all ideas
  • Document why top ideas were selected (transparency)
  • Include "runner-up" ideas (for later consideration)

Don't:

  • Filter ideas during divergence (defeats the purpose)
  • Create clusters that are too similar or overlapping
  • Use vague evaluation criteria ("better", "more appealing")
  • Cherry-pick scores to favor pet ideas
  • Select ideas without systematic evaluation
  • Ignore constraints from requirements gathering
  • Skip documentation of the full process

Quick Reference

  • Template: resources/template.md - Structured prompts and techniques for diverge-cluster-converge
  • Quality rubric: resources/evaluators/rubric_brainstorm_diverge_converge.json
  • Output file: brainstorm-diverge-converge.md
  • Typical idea count: 20-50 ideas → 4-8 clusters → 3-5 selections
  • Common criteria: Impact, Feasibility, Cost, Speed, Risk, Alignment

FAQ

What does the brainstorm-diverge-converge skill do?

Applies structured divergent-convergent thinking to generate many creative options, organize them into meaningful clusters, then systematically evaluate and narrow to the strongest choices. Balances creative exploration with disciplined decision-making. Use when exploring product ideas, solving open-ended problems, generating strategic alternatives, developing research questions, designing experiments, or when user mentions brainstorming, ideation, divergent thinking, generating options, or evaluating alternatives.

How do I install brainstorm-diverge-converge?

Run npx skills add https://github.com/lyndonkl/claude --skill brainstorm-diverge-converge in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/brainstorm-diverge-converge/ (personal) or .claude/skills/brainstorm-diverge-converge/ (project).

Which AI agents can use brainstorm-diverge-converge?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is brainstorm-diverge-converge safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains brainstorm-diverge-converge?

It is published by lyndonkl in lyndonkl/claude. It has 148 recorded installs.

More from lyndonkl/claude

View all →

evaluation-rubrics

lyndonkl/claude

Designs structured scoring tools with explicit criteria, performance scales, and descriptors for consistent, transparent quality assessment. Use when need quality criteria and scoring scales to evaluate work consistently, compare alternatives objectively, set acceptance thresholds, reduce subjective bias, or when user mentions rubric, scoring criteria, quality standards, evaluation framework, inter-rater reliability, or grading/assessing work.

Develops business strategies grounded in rigorous competitive and market analysis using proven frameworks (Good Strategy kernel, Porter's 5 Forces, SWOT, Blue Ocean, Playing to Win, Value Chain Analysis, BCG Matrix). Use when developing strategy (market entry, product launch, expansion, M&A, turnaround), conducting competitive analysis, making strategic decisions (build vs buy, pricing, positioning), planning strategic initiatives, or when user mentions strategy, competitive analysis, Porter's 5 Forces, SWOT, market positioning, or strategic frameworks.

Business & Finance491 installs

Guides systematic multi-pass review and editing of scientific manuscripts (research articles, reviews, perspectives) to improve clarity, structure, scientific rigor, and reader comprehension. Use when reviewing or editing research manuscripts, journal articles, or perspectives, when user mentions manuscript, paper draft, article, research writing, journal submission, reviewer feedback, or needs to improve scientific writing.

Open the skill to read its SKILL.md instructions.

Open the skill to read its SKILL.md instructions.

417 installs

Guides creation and review of competitive grant proposals (NIH R01/R21/K, NSF, foundations) by applying reviewer-perspective thinking to ensure clear hypotheses, compelling significance, genuine innovation, and feasible approaches. Use when writing or reviewing grant proposals, crafting specific aims, drafting significance/innovation/approach sections, or when user mentions R01, R21, K-series, grant writing, proposal review, study section, or fundable hypothesis.

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.