SkillAgentSearch skills...

brainstorming

Use when defining ambiguous or high-complexity new features, product behavior, UI/component design, architecture choices, contract changes, or when grilling/pressure-testing a plan or design. Routine small requests stay on the fast path.

Install / Use

npx skills add GanyuanRan/Aegis --skill brainstorming

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

93/100

Category

Legal

Supported Platforms

Universal

Our assessment of brainstorming

brainstorming scores 93/100 on our quality scale, 26th of 209 Legal skills we index (top 13%).

Its SKILL.md is 24 KB long, well organised into 19 sections with 9 code examples: a thorough specification that gives an agent plenty to work with.

With 1,273 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so brainstorming is actively maintained.
  • Our last check on 2026-10-26 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

brainstorming compared with similar skills

All 4 of these similar skills score higher than brainstorming; compare them before choosing.

SkillScoreStarsUpdatedFormat
brainstorming (this skill)by GanyuanRan931.3k53d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install brainstorming?
Run npx skills add GanyuanRan/Aegis --skill brainstorming. The install tabs above show the steps for each supported agent.
Which AI agents does brainstorming work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is brainstorming safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is brainstorming still maintained?
The repository was last updated about 2 months ago, so brainstorming is actively maintained.

name: brainstorming description: "Use when defining ambiguous or high-complexity new features, product behavior, UI/component design, architecture choices, contract changes, or when grilling/pressure-testing a plan or design. Routine small requests stay on the fast path."

<EXPLICIT-MODE-GATE> If activation mode is explicit (`~/.config/aegis/config.toml` has `activation_mode = "explicit"`, or `AEGIS_ACTIVATION_MODE=explicit` is visible in the environment) and the current user request did not explicitly invoke Aegis or this skill by name, exit back to the fast path: answer concisely without this workflow's checklist, ceremony, or document requirements. If the user explicitly named Aegis or this skill, proceed normally. </EXPLICIT-MODE-GATE>

Execute

→ Direct grilling or plan/design pressure-test? → Enter Grilling Mode below. Soft challenge intent? → Use its one-line mode confirmation. Do not start normal design artifacts, document writing, task planning, or implementation during the interview. → New feature, product behavior, UI/component design, architecture/contract change, or ambiguous medium/high-complexity work? → Design first. No implementation until the needed design/spec is approved.

  1. Explore project context → read authority docs, check for existing patterns
  2. Ask clarifying questions one at a time (prefer multiple choice)
  3. Propose 2-3 approaches with trade-offs and your recommendation
  4. Present design sections → get user approval after each
  5. Write spec → self-review → user review → transition to writing-plans → HARD GATE: For tasks that match this skill, do NOT write code, scaffold projects, or invoke implementation skills until design/spec approval is satisfied.

Route Fixtures

These rows are calibration expectations for method behavior, not a runtime regex router. The Agent selects the route from evidence; route selection is not a user question.

| Scenario | Route | | --- | --- | | 想法还没想清楚,先梳理功能设计 | normal brainstorming, compact output first | | 讨论公共 API 契约和兼容边界 | normal brainstorming, design sections before implementation | | 盘问/拷问/审问这个方案,不要顺着我 | Grilling Mode | | 修复登录按钮的空指针 | systematic-debugging | | review 当前 PR / diff / 当前代码 | requesting-code-review | | 给我一个有目标的方案 | goal-framing when goal intent is explicit; otherwise normal brainstorming | | 把按钮文案从保存改成提交 | fast-path; no design ceremony |

Brainstorming Ideas Into Designs

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

Start by understanding the current project context and authority boundary, then ask questions one at a time to refine the idea. Once you understand what you're building, present the smallest design artifact that stabilizes the work and get the required approval.

<HARD-GATE> Do NOT invoke any implementation skill, write any code, scaffold any project, or take implementation action for work that matches this skill until you have presented the required design/spec and the user has approved it where this workflow requires approval. </HARD-GATE>

Grilling Mode

Mode Precedence

While Grilling Mode is active, it overrides the normal brainstorming execution flow. Suspend Checklist, The Process, the Compact output contract, and all documentation or design-transition requirements until the user exits the interview; retain the no-implementation hard gates.

Grilling Entry Signals

  • Direct: The user asks to grill or interrogate an idea, plan, or design, or explicitly requests a pressure-test. Direct phrases include grill me, grill this plan, 审问我, 盘问我, and 拷问我. Enter the mode immediately.
  • Soft: The user asks to challenge assumptions, find holes, red-team, or "别顺着我" about a draft idea, plan, or design. Ask only: Grill or normal brainstorming? Enter the mode only after confirmation.
  • Not grilling: A bare/literal phrase reference, or a PR, diff, or current-code review. Explain literal phrases normally; route implementation review to requesting-code-review.

Opening Card

After the user has entered the mode, emit this once in the user's language, then begin the interview:

◆ Grilling Session
Target: <idea / plan / design>
Question path: value -> boundaries -> failure modes -> acceptance
Pace: deep (default) | fast (user-requested)

Pace

  • Deep: Ask exactly one decision question per turn when it is blocking or depends on the previous answer. State the recommended answer and the most relevant trade-off before waiting.
  • Fast: Only when the user explicitly asks for a fast or batched interview (for example, fast, batch, 快问, or 一次问几个), ask at most three independent decision questions. Give each question its recommendation and trade-off, then wait for the user's responses. Return to deep pace for dependent follow-ups.
  1. Explore the codebase and current authority docs for facts before asking. Do not ask the user for facts that can be found locally.
  2. The user owns the decision. Do not treat a recommendation, a tentative answer, or a shared-understanding checkpoint as final approval.
  3. Aside from the one-time opening card, keep the turn to the observation, recommendation, and the selected pace's questions. Do not emit a full design ceremony, write docs, create a plan, or implement while the interview is active.
  4. End when the user says to stop, defer, or that the questions are sufficient. Reconfirm in a structured Challenge Result. That summary does not grant completion authority.
Challenge Result
- Survived assumptions
- Rejected assumptions
- New evidence needed
- Design changes required
- Residual risks
- Return state: interview | design | approaches | writing-plans
  1. If the user asks to proceed after the interview, return to the normal brainstorming design gate. A design/spec still needs the required approval before planning or implementation.

Route Away / Doc Necessity Gate

Do not force this workflow onto low-complexity work. A tiny wording edit, single-owner bug fix, simple config/status question, local utility change, or mechanical multi-file change can proceed through concise intent, baseline check, TDD/debugging, and verification without any new document. Run the Doc Necessity Gate before writing any spec, plan, ADR, or baseline artifact:

  1. Does an existing spec/plan/ADR/baseline already cover this change surface? -> Update that owner document in place; never create a sibling document.
  2. Is the surface durable/irreversible (schema, public API, owner, dependency direction, migration, compat-path retirement), cross-session/cross-person handoff, approval-gated, or authority-required? -> Yes: write the smallest artifact for that surface (see Documentation). -> No: write no document; keep compact drafts in-session.
  3. Re-check at edit time and at closeout; escalate to the smallest stabilizing spec if uncertainty or impact grows.

Route Precedence

  1. Route-away cases leave this workflow first (systematic-debugging, requesting-code-review, goal-framing when goal intent is explicit, fast-path micro-tasks).
  2. Grilling Mode requires explicit challenge intent. Ordinary discussion, evaluation, or the need to clarify understanding is not grilling.
  3. Otherwise run the normal brainstorming flow and escalate depth on evidence: contracts, owners, persistence, migration, security, consumer count, or blast radius. Escalate after evidence, not merely because the first request sounds ambitious.
  4. File count alone is not a design signal: a mechanical multi-file change can still be fast-path, and a one-file contract change can still be full design.

Role And Authority Contract

Agent-owned decisions

Resolve these directly without asking the user:

  • repository investigation strategy and evidence gathering order
  • file and function organization inside an accepted owner
  • testing commands and proportional verification mechanics
  • inline versus subagent execution when policy already allows it
  • reversible implementation structure that does not change product behavior, contract, authority, or durable boundaries

User-owned decisions

Ask the user only for:

  • product behavior or preference
  • irreversible, destructive, external, public, production, or sensitive impact
  • explicit product/contract commitments only the user can make
  • necessary information unavailable from repository, tools, and authority docs

Every user question must pass this test:

If the user chooses another answer, which design boundary, behavior, owner, acceptance criterion, or risk decision changes?

If none changes, do not ask. When a question passes this test, attach a recommended option and the reason for it, so the user decides between framed choices instead of researching. This classification clarifies which decisions are user-owned; it does not remove the approval points this workflow already defines.

Checklist

You MUST create a task for each of these items and complete them in order:

  1. Explore project context — check files, docs, recent commits, authority docs, and passively consume relevant active CONTEXT.md language without loading active modeling
  2. Choose the path and scope — real design? diagnosis? route accordingly or decompose first
  3. Ask clarifying questions — one at a time, understand purpose/constraints/success criteria
  4. Draft working artifacts — TaskIntentDraft, BaselineReadSetHint, BaselineUsageDraft, ImpactStatementDraft
  5. Run existence check when adding new surfaces — only if an approach adds a new owner, skill, artifact, adapter, fallback, workflow step, or benchmark metric
  6. Propose 2-3 approaches — with trade-offs and your recommendation
  7. Present design — in sections scaled to complexity, get user approval where required
  8. Write spec artifact — only after the Doc Necessity Gate passes and no existing owner spec/plan covers the surface; if covered, update that document instead of creating a sibling
  9. Spec self-review — check for placeholders, contradictions, ambiguity, scope, boundary
  10. User reviews written spec — ask user to review before proceeding
  11. Transition to implementation — invoke writing-plans skill (terminal state)

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

The Process

Understanding the idea:

  • Check current project state first (files, docs, recent commits)
  • Read relevant authority docs before asking deep questions
  • Use existing canonical terms in questions, options, scenarios, and the spec. If terminology crystallizes or conflicts, compose establishing-project-context; do not leave the resolution only in the spec.
  • If the request is diagnosis/root-cause/follow-up to an approved plan → route to correct workflow
  • If the request spans multiple independent subsystems → flag and decompose first
  • Ask clarifying questions one at a time, prefer multiple choice
  • Separate facts, assumptions, unknowns while exploring

Working artifacts: Keep four drafts: TaskIntentDraft (outcome, goal, success evidence, stop condition, non-goals, scope, risks), BaselineReadSetHint (candidate docs, authority gaps), BaselineUsageDraft (required refs, optionally delivered context refs, acknowledged-before-plan refs, cited refs, missing refs, advisory decision), and ImpactStatementDraft (affected layers, owners, invariants, compat, non-goals). Refresh when scope changes.

Compact output contract: Aegis Visibility, TaskIntentDraft, BaselineReadSetHint, BaselineUsageDraft, Requirement Ready Check, ImpactStatementDraft, Existence Check, Product Risk Lens, Architecture Integrity Lens, Prior-Art & Reuse Lens, Baseline Role Alignment, Plan-Time Complexity Check, Options, and Decision Needed. Use this compact shape before expanding into a full design structure.

Aegis Visibility for this

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars1.3k
CategoryLegal
Updated1mo ago
Forks64

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions