brainstorm

Overview of brainstorm skill

What brainstorm skill does

The brainstorm skill is a guided, interactive ideation workflow for Decision Support. Instead of giving one-shot idea lists, it runs a structured conversation: explore the problem, test assumptions, synthesize insights, then optionally turn the result into a project or captured knowledge. If you want a skill that helps you think better before committing to execution, this is the right fit.

Who should install brainstorm

Install this brainstorm skill if you regularly need to clarify fuzzy ideas, compare options, pressure-test plans, or turn early thoughts into something actionable. It is most useful for founders, product leads, researchers, operators, and anyone making ambiguous decisions where ordinary prompting tends to produce shallow suggestions too quickly.

Why it is different from a generic prompt

The main differentiator is the workflow. The skill explicitly uses probing questions, assumption checks, multiple angles, and techniques like 5 Whys, What if?, analogies, devil's advocate, and constraint shifts. That makes brainstorm stronger than a generic “give me ideas” prompt when you need discovery, not just output.

What to know before you install

This repository evidence is lightweight: the skill is mostly in SKILL.md and does not ship helper scripts, references, or metadata-driven setup. That keeps brainstorm easy to adopt, but it also means output quality depends heavily on how well you answer the facilitator's questions. If you want rigid frameworks or automated downstream actions, expect to add your own process.

How to Use brainstorm skill

Install context and where to read first

To use this brainstorm skill, add the OrbitOS skill from the repo and open EN/.agents/skills/brainstorm/SKILL.md first. That file contains the real operating logic. Because there are no supporting resources, most install decisions come down to whether you want this conversational style of brainstorming and synthesis.

A practical install pattern is:

1. Add the skill from MarsWang42/OrbitOS.
2. Read SKILL.md.
3. Trigger brainstorm only when you want iterative exploration, not instant execution.

What input brainstorm needs to work well

brainstorm performs best when you provide:

• the decision or idea you are working on
• why it matters now
• constraints such as time, budget, audience, or risk tolerance
• what you already know
• what you are unsure about
• the form of output you want at the end

Weak input: “Help me brainstorm an app.”
Strong input: “Use brainstorm for Decision Support on a B2B onboarding tool. I have 2 engineers, 6 weeks, and need options that reduce support tickets without changing pricing. Challenge assumptions and surface tradeoffs.”

How to write a prompt that invokes the skill well

A good brainstorm usage prompt should include context, desired challenge level, and end state. A reliable template is:

Use brainstorm to help me think through [topic]. My goal is [outcome]. Constraints: [constraints]. Current assumptions: [assumptions]. Unknowns: [unknowns]. Please ask probing questions, explore alternatives, and then synthesize the strongest options.

If you want better Decision Support, ask explicitly for comparisons:
Use brainstorm to compare 3 paths, challenge my default choice, and identify what evidence would change the decision.

Suggested workflow for real sessions

Best results usually follow this sequence:

1. Start broad: problem, stakes, users, timing.
2. Let the skill ask questions before requesting solutions.
3. Push for alternative frames: “what if,” “devil's advocate,” and severe constraints.
4. Ask for synthesis only after enough exploration.
5. Finish by choosing one action: create a project, capture knowledge, or list next decisions.

The common mistake is asking for synthesis too early. This brainstorm guide works best when you let the conversation surface hidden assumptions first.

brainstorm skill FAQ

Is brainstorm good for Decision Support?

Yes. brainstorm is especially suited to Decision Support because it is built to surface assumptions, explore multiple angles, and summarize tradeoffs before action. It is a better fit than a plain ideation prompt when the real job is deciding, not just generating options.

When is brainstorm not the right skill?

Skip brainstorm if you already know the task and need execution steps, code, or a finalized plan immediately. It is also a weak fit for highly deterministic work where the answer depends on fixed rules rather than exploration. In those cases, a direct task-specific skill or ordinary prompt may be faster.

Is this brainstorm install beginner-friendly?

Yes, because the skill logic is concentrated in one file and has a clear three-phase flow. The catch is that beginners often under-specify context. If you can describe your goal, constraints, and uncertainties in plain language, you can use the brainstorm skill effectively.

How is brainstorm different from asking ChatGPT to brainstorm?

A normal prompt often jumps to polished ideas without testing the framing. This brainstorm usage pattern is intentionally interactive: it asks questions, challenges assumptions, explores variants, and then synthesizes. The value is not just more ideas; it is better thinking structure.

How to Improve brainstorm skill

Give richer starting context

The fastest way to improve brainstorm output is to supply decision-grade context, not topic labels. Include who the decision affects, what success looks like, what would make an option unacceptable, and what has already been tried. Better input creates sharper questions and more realistic branches.

Ask for specific challenge modes

The skill already supports several techniques, so request the ones you need. Examples:

• “Use 5 Whys to find the root problem.”
• “Play devil's advocate against my preferred option.”
• “Use hard constraints: 1 week, no hiring, no new vendors.”
• “Give analogies from adjacent industries.”

This makes brainstorm more targeted and less generic.

Watch for common failure modes

The main failure modes are vague goals, premature convergence, and untested assumptions. If the session feels shallow, pause and add missing constraints or ask the skill to restate the actual decision. If it becomes too expansive, force prioritization: “Rank the top 3 options by feasibility and downside.”

Iterate after the first synthesis

Do not treat the first summary as final. A strong brainstorm guide uses synthesis as a checkpoint. Ask follow-ups such as:

• “Which assumption is doing the most work here?”
• “What evidence would eliminate option 2?”
• “What did we ignore?”
• “Turn the best option into a small next-step plan.”

That second pass is often where brainstorm becomes genuinely useful for Decision Support rather than just idea generation.