Brainstorming Engine

Chooses an ideation pattern for your problem, produces 8 to 12 distinct ideas, then refines the top three with risks and concrete next steps.

Used by our engineering team

What It Does

Most brainstorms produce variations on the first idea. This skill picks a method that fits the problem, runs it, and says which one it used and why.

There are ten patterns: Perspective Multiplication, Constraint Variation, Inversion, Chain-of-Thought, Extreme Scaling, Analogical Reasoning, Assumption Reversal, First Principles, Jobs-to-be-Done and Random Input.

The work runs in two stages. First it diverges, producing 8 to 12 specific, distinct ideas with reasoning. Then it converges on the three strongest, with the trade-offs and a next step you can do now. If you say the ideas are too safe, too wild or too shallow, it switches pattern and says so.

It asks at most two or three questions, one at a time, and states every assumption it makes.

Who Uses It

Our engineering team uses it when scoping features, finding test scenarios and edge cases, naming things, or choosing between approaches. Other teams use it for campaign and content ideas.

Setup

Nothing needs installing, and no accounts or tools are needed. Use either route.

1. Copy the skill/ folder into your agent's skills folder and name it brainstorming-engine. For Claude Code that is .claude/skills/brainstorming-engine/ in a project, or the equivalent skills folder in your home directory. Other agents use their own skills folder, so follow its documentation.
2. Or fetch the skill through the Thinqmesh MCP server and let your agent install it.

Then start a new session and ask, for example: "Brainstorm ways to reduce failed deployments." You can also share a brief or spec and ask for ideas based on it.

Example Result

An invented request, answered in outline:

## Ideation results

Your request: ways to reduce failed deployments
Pattern used: Inversion
Why this pattern: finding how to make deployments fail on purpose exposes hidden weak points.

### Stage 1: Divergent ideas
1. Run every change through a staging copy first
   - Description: promote only builds that passed there
   - Reasoning: removes surprises from production

### Stage 2: Refined concepts
| Idea | Why it works | Trade-offs | Next step |
|------|--------------|------------|-----------|
| Staging gate | Catches environment differences | Slower releases | Trial it on one service for two weeks |

Recommendation: start with the staging gate.

How to Adapt

Add a domain to the inferred domains and give it its own example. Change the default idea count or the safe-to-stretch mix in the safe defaults. If your team has a favourite method, add it as an eleventh pattern in the same form, with when to use it, how to apply it and an example.