agentleFS
Sign inStart free
BlakeemBlakeem/aipromptguide-workflows/skills/brainstorm/SKILL.md

brainstorm

Skill1 starsChanged 8 days agoMITView on GitHub

Run the AIPG brainstorm workflow, which writes one fully committed variation per lens for a human to pick or combine, with no AI verdict. Use only when the user explicitly asks for the AIPG brainstorm workflow.

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, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 156 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When plugin-access.mjs exits 1, show the user its message, which names the cause, and run it again once the cause is fixed.

    line 13
  2. Very specific:

    Read ${CLAUDE_PLUGIN_ROOT}/workflows/brainstorm/CLAUDE.md and follow it exactly.

    line 16
  3. Distinctive:

    Use these paths wherever the guide says "this checkout" or "the tool's own directory":

    line 18

“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

The user wants to run the brainstorm-cycle dynamic workflow on the task below.

First run node "${CLAUDE_PLUGIN_ROOT}/tools/plugin-access.mjs" check. The Workflow tool launches only engines the session can read. On missing, unless the working directory is ${CLAUDE_PLUGIN_ROOT} or a folder above it, ask the user once whether to add the printed Read rule to their user settings. On yes, run the command again with grant (settings reload live, no restart). On no, the user can run /add-dir ${CLAUDE_PLUGIN_ROOT} for this session only. When plugin-access.mjs exits 1, show the user its message, which names the cause, and run it again once the cause is fixed.

Read ${CLAUDE_PLUGIN_ROOT}/workflows/brainstorm/CLAUDE.md and follow it exactly. Work its ## 0. Checklist top to bottom. Use these paths wherever the guide says "this checkout" or "the tool's own directory":

  • Engine scriptPath: ${CLAUDE_PLUGIN_ROOT}/workflows/brainstorm/brainstorm-cycle.mjs
  • root arg: ${CLAUDE_PLUGIN_DATA}. Runs land in its runs/<runId>/. Never the plugin install dir, which is version-swapped on update.

$ARGUMENTS

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.

Reviews can't be read right now.

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.

Check your setup, free