agentleFS
Sign inStart free
aprameyakaprameyak/coding-skills/brainstorm/SKILL.md

brainstorm

Skill1 starsChanged 41 days agoMITView on GitHub

Clarify requirements with one question at a time before coding. Use when the ask is vague, when the user says grill me or interview me, or before non-trivial design work.

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

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

  • 0

    Common

    Most of the 156 edited versions we read keep these.

  • 6

    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:

    Ask one question at a time.

    line 15
  2. Distinctive:

    If the codebase can answer a question, read it instead of asking.

    line 16
  3. Distinctive:

    Stop when remaining unknowns are cheap to resolve during build.

    line 19
  4. Distinctive:

    Do not batch five questions in one message.

    line 38
  5. Distinctive:

    Do not invent product requirements silently.

    line 39
  6. Distinctive:

    Prefer concrete options over open-ended prompts.

    line 40

“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

Goal

Reach shared understanding before implementation. Do not write production code until confidence is high.

Process

  1. Restate the problem in one sentence; ask the user to correct it if wrong.
  2. Ask one question at a time. Prefer questions that unlock the next decision.
  3. If the codebase can answer a question, read it instead of asking.
  4. Offer a recommended answer when helpful; let the user override.
  5. Capture decisions as they land (constraints, non-goals, success checks).
  6. Stop when remaining unknowns are cheap to resolve during build.
  7. Output a short agreed summary before coding.

Output

Problem: ...
Decisions:
- ...
Non-goals:
- ...
Success checks:
- [ ] ...
Open risks:
- ...

Rules

  • Do not batch five questions in one message.
  • Do not invent product requirements silently.
  • Prefer concrete options over open-ended prompts.

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.

Check your setup, free