agentleFS
karim-embarekkarim-embarek/superpowers-antigravity/skills/superpowers-brainstorming/SKILL.md

superpowers-brainstorming

Skill2 starsChanged 3 months agoMITView on GitHub

Interactive Socratic design refinement before writing code. Explores requirements, architectural trade-offs, and creates formal specifications.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    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:

    Use this skill before starting code implementation for new features, complex components, or structural refactoring.

    line 8
  2. Distinctive:

    Ask targeted Socratic questions to resolve ambiguities.

    line 12

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

Superpowers: Brainstorming Skill

Use this skill before starting code implementation for new features, complex components, or structural refactoring.

Objectives

  1. Prevent premature coding by clarifying requirements up front.
  2. Ask targeted Socratic questions to resolve ambiguities.
  3. Explore alternate architectures and trade-offs.
  4. Output a clear, structured design document or implementation plan before execution.

Workflow Step-by-Step

Step 1: Understand & Explore Requirements

  • Analyze the user request against existing codebase patterns and dependencies.
  • Identify missing constraints, edge cases, data structures, and scope limits.

Step 2: Socratic Interview & Design Trade-offs

  • Present concise, structured choices or questions to the user.
  • Highlight pros, cons, and performance/complexity implications for each alternative.

Step 3: Formalize Design Document

  • Summarize the agreed-upon architecture into a design artifact or plan.
  • Include:
    • System Boundaries & Components
    • Data Flow & Schemas
    • Error Handling & Edge Cases
    • Test Strategy

Step 4: User Validation

  • Request explicit user review of the design before proceeding to writing plans or code.

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.