agentleFS
Sign inStart free
RBraga01RBraga01/a-team/skills/brainstorming/SKILL.md

brainstorming

Skill24 starsChanged 24 days agoMITView on GitHub

Use BEFORE any creative work — creating features, building components, adding functionality. Explores user intent, requirements, and design before implementation. Hard-gated: no code until user approves the spec.

190 other projects use a version of this, 49 of them edited.

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

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 170 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do NOT write any code, scaffold any project, or take any implementation action until you have presented a design and the user has …

    line 11
  2. Very specific:

    Write spec to docs/specs/YYYY-MM-DD-<topic>-design.md

    line 38
  3. Distinctive:

    Run spec self-review (check: placeholders?

    line 39
  4. Distinctive:

    Ask user to review and approve spec

    line 40
  5. Distinctive:

    Do sections contradict each other?

    line 48

“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 Ideas Into Designs

Help turn ideas into fully formed designs and specs through natural collaborative dialogue.

<HARD-GATE> Do NOT write any code, scaffold any project, or take any implementation action until you have presented a design and the user has explicitly approved it. This applies to EVERY project regardless of perceived simplicity. </HARD-GATE>

Checklist (Complete in Order)

  1. Explore project context — check files, docs, recent commits
  2. Offer visual companion (if visual questions ahead) — own message, not combined
  3. Ask clarifying questions — one at a time: purpose, constraints, success criteria
  4. Propose 2-3 approaches — with trade-offs and your recommendation
  5. Present design — scaled to complexity, get approval section by section
  6. Write design doc — save to docs/specs/YYYY-MM-DD-<topic>-design.md and commit
  7. Spec self-review — scan for placeholders, contradictions, ambiguity, scope
  8. User reviews spec — wait for user approval before proceeding
  9. Transition — invoke writing-plans skill to create implementation plan

Key Principles

  • One question at a time — never multiple questions in one message
  • Multiple choice preferred — easier to answer than open-ended
  • YAGNI ruthlessly — remove unnecessary features from all designs
  • Explore alternatives — always propose 2-3 approaches before settling
  • Incremental validation — present design sections, get approval before moving on

After the Design

  • Write spec to docs/specs/YYYY-MM-DD-<topic>-design.md
  • Run spec self-review (check: placeholders? contradictions? scope? ambiguity?)
  • Ask user to review and approve spec
  • Invoke writing-plans skill — not any other skill

The terminal state is invoking writing-plans. Do NOT invoke any implementation skill.

Spec Self-Review Checklist

  1. Any "TBD" or incomplete sections? Fix them.
  2. Do sections contradict each other? Resolve.
  3. Is this focused enough for a single plan, or needs decomposition?
  4. Can any requirement be interpreted two ways? Pick one and make it explicit.

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