agentleFS
Sign inStart free
gerard-labsgerard-labs/superpowers-api-platform/skills/brainstorming/SKILL.md

brainstorming

Skill2 starsChanged 6 months agoMITView on GitHub

Pre-architecture brainstorming for an API Platform feature — when the story isn't yet stable enough to feed `/architect`. Explores requirements, identifies invariants, considers alternatives, surfaces unknowns, defines the smallest valuable slice. Output: a refined story description ready for `/architect <story>` or `/api-resource-pipeline <story>`. Use BEFORE the pipeline when the prompt is too vague.

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

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 170 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:

    No premature pattern selection (CQRS vs simple service, DTO vs Object Mapper, etc.) — that's also the architect's decision.

    line 31

“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 (pre-architecture)

Use when

  • A story is too vague to feed /architect directly
  • You want to explore requirements + alternatives before committing to a plan
  • Multiple framings of the same feature exist; you want to pick one
  • The "smallest next step" is unclear

Position: this skill is upstream of the pipeline. Output = refined story description suitable for /architect <story> or /api-resource-pipeline <story>. Once the brainstorm converges, exit and feed the pipeline.

Default workflow

  1. Restate the story in your own words. Get explicit agreement on the goal.
  2. Surface invariants : what MUST be true at the end? (user-visible features + non-functional like perf, security, a11y).
  3. List alternatives : 2-3 ways to deliver the invariants. Compare on complexity / risk / time.
  4. Pick the smallest valuable slice : the smallest PR that surfaces the most risky hypothesis.
  5. Identify unknowns : what would falsify the design? Where are the spikes needed?
  6. Refine the story description — one paragraph, ready to feed /architect.

Guardrails

  • Stay upstream. Don't propose code, file paths, or skill dispatch — that's the architect's job.
  • Time-box the brainstorm. If you can't refine the story in 10 prompts, the story is too big — split it.
  • No premature pattern selection (CQRS vs simple service, DTO vs Object Mapper, etc.) — that's also the architect's decision.

Output contract

  • A refined story description (1 paragraph) usable as $ARGUMENTS of /architect.
  • A short list of explicit invariants + non-invariants ("nice to have" excluded).
  • A note on the smallest valuable slice.

Progressive disclosure

  • This file for the brainstorm flow
  • docs/complexity-tiers.md for sizing the brainstorm output

References

  • docs/complexity-tiers.md
  • docs/symfony/pipeline-overview.md — what happens after the brainstorm converges

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