How do I install the Just Brainstorm skill?

Run npx skillmds@latest add kevmoo/just-brainstorm in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Just Brainstorm safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Just Brainstorm?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Just Brainstorm free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Just Brainstorm?

kevmoo (@kevmoo) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Just Brainstorm by kevmoo — Agent Skill

Name: Just Brainstorm
Author: kevmoo

Just Brainstorm

Ponder architectural designs, explore potential solutions, weigh tradeoffs, or analyze the impact of proposed codebase changes without making code changes. Always outputs the analysis to a Markdown artifact.

kevmoo a28866f 2 files · 2.9 KB Updated Sep 17, 2026

File contents

When to use this skill

Activate this skill when you need to think through a design, explore options, or evaluate the impact of a potential change before writing code.

Examples of trigger phrases:

"Let me brainstorm..."
"Just brainstorming here..."
"What if we [do specific change]..."
"What would break if we..."
"How hard would it be to migrate..."
"Help me design..."

Critical Rule: Zero Codebase Changes

NO CODEBASE FILE EDITS OR CREATION: Do not edit existing project files, write new implementation code, or modify repository state.
MANDATORY ARTIFACT GENERATION: The only permitted file creation is the design/analysis artifact (.md file in the conversation artifacts directory).

Procedural Workflow

1. Gather Context & Empirical Data (Read-Only)

Inspect the codebase using read-only tools (grep_search, view_file, list_dir) to ground your brainstorming or analysis in reality.
For Impact Analysis ("What-if"): Gather real statistics. Calculate usage counts, identify affected call sites, and map out dependencies. Do not guess.

2. Interactive Alignment (`ask_question`)

Use ask_question early if the goals, constraints, or the scope of the "what-if" scenario are unclear.

3. Generate the Artifact

Write the output to a .md file in the conversation artifacts directory.
Use RequestFeedback: false in the artifact metadata (do not block with "Proceed" gates).
Structure for Design Brainstorming:
- Present 2–4 distinct options.
- Highlight tradeoffs (pros/cons) and relative complexity.
Structure for Impact Analysis ("What-if"):
- Detail the step-by-step impact if the change were executed.
- List breaking changes, migration friction, and affected modules with metrics.
- Provide a summary risk/feasibility verdict.

4. Conclude with Next Steps

Suggest 1–3 actionable next steps (e.g., create an implementation plan, explore a specific option deeper, or start implementation).

---name: just-brainstormdescription: Ponder architectural designs, explore potential solutions, weigh tradeoffs, or analyze the impact of proposed codebase changes without making code changes. Always outputs the analysis to a Markdown artifact.---## When to use this skillActivate this skill when you need to think through a design, explore options,or evaluate the impact of a potential change before writing code.Examples of trigger phrases:- "Let me brainstorm..."- "Just brainstorming here..."- "What if we [do specific change]..."- "What would break if we..."- "How hard would it be to migrate..."- "Help me design..."## Critical Rule: Zero Codebase Changes- **NO CODEBASE FILE EDITS OR CREATION**: Do not edit existing project files, write new implementation code, or modify repository state.- **MANDATORY ARTIFACT GENERATION**: The only permitted file creation is the design/analysis artifact (`.md` file in the conversation artifacts directory).## Procedural Workflow### 1. Gather Context & Empirical Data (Read-Only)- Inspect the codebase using read-only tools (`grep_search`, `view_file`, `list_dir`) to ground your brainstorming or analysis in reality.- **For Impact Analysis ("What-if")**: Gather real statistics. Calculate usage counts, identify affected call sites, and map out dependencies. Do not guess.### 2. Interactive Alignment (`ask_question`)- Use `ask_question` early if the goals, constraints, or the scope of the "what-if" scenario are unclear.### 3. Generate the Artifact- Write the output to a `.md` file in the conversation artifacts directory.- Use `RequestFeedback: false` in the artifact metadata (do not block with "Proceed" gates).- **Structure for Design Brainstorming**: - Present 2–4 distinct options. - Highlight tradeoffs (pros/cons) and relative complexity.- **Structure for Impact Analysis ("What-if")**: - Detail the step-by-step impact if the change were executed. - List breaking changes, migration friction, and affected modules with metrics. - Provide a summary risk/feasibility verdict.### 4. Conclude with Next Steps- Suggest 1–3 actionable next steps (e.g., create an implementation plan, explore a specific option deeper, or start implementation).

Frequently asked questions