agentleFS
MrCipherSmithMrCipherSmith/goodai-base/skills/brainstorm/SKILL.md

brainstorm

Skill0 starsChanged 5 months agoMITView on GitHub

Use when exploring architecture decisions, tech choices, feature ideas, or any open-ended problem that benefits from multiple perspectives.

189 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use playtest-report, team-polish and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CoralGameSkill

    playtest-report

    Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.

    Also in 9 projects that use this

  • CoralGameSkill

    team-polish

    Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.

    Also in 11 projects that use this

  • lilangMaxSkill

    soak-test

    Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.

    Also in 6 projects that use this

  • lilangMaxSkill

    team-live-ops

    Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.

    Also in 6 projects that use this

  • +8 more from CoralGame

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 156 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If in a project directory, scan codebase for relevant context

    line 35
  2. Distinctive:

    Add: Security Analyst (auth, data exposure, compliance) and UX Advocate (complexity, learning curve, accessibility).

    line 82
  3. Distinctive:

    Don't dismiss "boring" solutions — they often win

    line 89

“Common” is measured: kept by at least 6 in 10 of the 156 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Brainstorm

Structured brainstorming that explores a topic from multiple angles and converges on actionable options.

Arguments

  • /brainstorm <topic> — full brainstorm with 3 parallel agents
  • /brainstorm --quick <topic> — inline fast brainstorm (no agents, for simple decisions)
  • /brainstorm --deep <topic> — 5 agents (+Security Analyst, +UX Advocate)
  • /brainstorm --code — focus on code architecture (reads codebase for context)

Workflow

Step 1: Frame the Problem

  1. Restate the user's challenge in clear terms
  2. Identify constraints: technical, business, quality
  3. If in a project directory, scan codebase for relevant context

Step 2: Diverge — Generate Ideas (3 Parallel Agents)

Launch 3 agents simultaneously:

Agent 1 — Pragmatist

"Propose 2-3 solutions optimizing for speed of delivery, simplicity, and maintainability. Use boring, proven technology. For each: approach, pros/cons, effort (S/M/L)."

Agent 2 — Innovator

"Propose 2-3 unconventional or cutting-edge solutions. Think new patterns, emerging tools, or approaches from other domains. For each: approach, pros/cons, effort."

Agent 3 — Critic

"What are the hidden risks? What will break at scale? What will be painful to maintain? Produce 5-7 critical questions any solution must address."

Step 3: Converge — Synthesize

## Ideas Map
### Option A: [Name]
**Approach:** ... | **Pros:** ... | **Cons:** ...
**Effort:** S/M/L | **Risk:** Low/Med/High

## Critical Questions
(from Critic — apply to ALL options)

## Comparison Matrix
| Criteria        | Option A | Option B | Option C |
|-----------------|----------|----------|----------|
| Effort          | S        | M        | L        |
| Risk            | Low      | Med      | High     |
| Scalability     | ★★★      | ★★★★     | ★★★★★    |
| Time to ship    | 1 week   | 3 weeks  | 6 weeks  |

Step 4: Recommend

  1. Recommended option with reasoning
  2. Runner-up and when you'd pick it instead
  3. Next steps — concrete action items

Step 5: Discuss

Offer to go deeper on any option or kick off /feature-dev / /prd-creator.

Quick Mode (--quick)

Skip agents. Inline: 3-5 options in table, score each, recommend one.

Deep Mode (--deep)

Add: Security Analyst (auth, data exposure, compliance) and UX Advocate (complexity, learning curve, accessibility).

Rules

  • Ground ideas in the project's actual tech stack and constraints
  • Include effort estimates — ideas without estimates aren't actionable
  • The Critic's questions must be answered by the recommendation
  • Don't dismiss "boring" solutions — they often win
  • End with concrete next steps, not just analysis

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.