agentleFS
Sign inStart free
YassimbaYassimba/loom/skills/brainstorming/SKILL.md

brainstorming

Skill9 starsChanged 2 months agoApache-2.0View on GitHub

Use when the user wants to brainstorm or explore an idea — a feature, product direction, or "what if" — before deciding whether it deserves a plan. Ideation only — ends in an idea brief, not a design.

190 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use chinese-code-review, chinese-commit-conventions 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.
  • Leodorareluctant259Skill

    chinese-code-review

    中文代码审查规范——在保持专业严谨的同时，用符合国内团队文化的方式给出有效反馈

    Also in 8 projects that use this

  • Leodorareluctant259Skill

    chinese-commit-conventions

    中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化

    Also in 8 projects that use this

  • ryanportfolioSkill

    addskill

    Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.

    Also in 6 projects that use this

  • ryanportfolioSkill

    apply-firmware

    Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.

    Also in 6 projects that use this

  • +2 more from Leodorareluctant259
  • +6 more from ryanportfolio

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 170 edited versions we read keep these.

  • 2

    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:

    If invoked with no idea attached, read references/gamechanging-feature.md and follow it to surface a candidate.

    line 10
  2. Distinctive:

    Sketch what has shape: When the idea is visual — UI, workflow, comparison, diagram, mental model — a sketch beats another paragraph, so …

    line 16
  3. Very specific:

    If they agree, read references/visual-companion.md and follow it.

    line 18
  4. Distinctive:

    When you can fill every field of the brief from the user's own answers — not your guesses — produce it:

    line 23

“Common” is measured: kept by at least 6 in 10 of the 170 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

Brainstorming

Turn a fuzzy idea into a clear direction through conversation. Brainstorming answers what are we trying to do? — how will we build it? belongs to grill-me, so when the conversation drifts toward architecture, code, or "how should this fit this repo?", stop and offer to move there. The brief below is the only artifact this skill produces: no specs, issues, commits, or code.

If invoked with no idea attached, read references/gamechanging-feature.md and follow it to surface a candidate.

Diverge

  1. Name the raw idea. Restate it in one or two sentences so the user can correct you early.
  2. Ask one question per turn about purpose, audience, pain, outcome, constraints, and non-goals. Make each easy to answer: concrete options, multiple choice when it helps, your recommended answer included.
  3. Sketch what has shape. When the idea is visual — UI, workflow, comparison, diagram, mental model — a sketch beats another paragraph, so reach for the companion routinely. Offer it in its own message and wait:

    Want me to spin up a local browser companion for sketches and diagrams? It's token-heavier but often clearer than text. (Requires opening a local URL.) If they agree, read references/visual-companion.md and follow it; if they decline, continue text-only.

  4. Offer 2–3 directions with plain-language trade-offs.

Converge

When you can fill every field of the brief from the user's own answers — not your guesses — produce it:

## Idea brief

Idea:

Audience:

Problem / pain:

Desired outcome:

Non-goals:

Promising directions:
1.
2.
3.

Recommended direction:

Open questions for `grill-me`:
-
-

Then ask (use AskUserQuestion if available):

Want to run grill-me to refine this idea further? Want to save this idea to pick up later?

If they save it: write the brief to ai-docs/plans/<YYYY-MM-DD-project>/idea.md (today's date, short kebab-case project slug; create the directory), and if the visual companion ran, copy its mockup HTML files from the session's screen_dir into mockups/ beside the brief. In that same directory, /to-spec will later write spec.md and /to-tickets will write issues/<NNN>-<name>.md.

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