agentleFS
Sign inStart free
int2t05int2t05/engineering-skills/skills/01-product/brainstorm/SKILL.md

brainstorm

Skill3 starsChanged 30 days agoMITView on GitHub

Clarify a product idea through focused dialogue. Triggers on "brainstorm", "头脑风暴".

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

1 rule. 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask questions whose answers change scope or direction.

    line 19

“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

When to use

  • Clarify a product idea through focused dialogue.

Not for: spec for confirmed requirements; research for external investigation.

Steps

  1. Identify the user, real problem, workaround and desired outcome; avoid invented confidence percentages.
  2. Ask questions whose answers change scope or direction. Respect clear delegation and previous confirmations rather than requiring ritual wording.
  3. Compare meaningful directions by value, feasibility and constraints; distinguish interview evidence from hypotheses.
  4. Present scope, observable success and open decisions for confirmation before dependent specification.

Output: Suggested paths, subject to human audit: ROADMAP.md; docs/research/interview.md only for actual interviews.

Verify

  • A concrete user problem and outcome are defined; assumptions and user confirmations are distinguishable.

References

  • engineering-principles.md — shared decision boundaries, scope and verification.
  • product-principles.md — product discipline (need≠feature, behavior is data, validate before building, say no to good ideas, discovery precedes delivery).
  • human-audit.md — document consent, readability and human review.
  • references/techniques.md — ideation frameworks (SCAMPER, HMW, first principles, JTBD), decision techniques (design tree, questionnaire handoff), evaluation rubric, and worked examples.
  • references/discovery-methods.md — problem-validation methods (Mom Test interview, JTBD switching interview, opportunity-solution tree, working backwards / PR-FAQ, Lean Canvas, MVP validation loop).

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