# Brainstorming

Use when defining ambiguous or high-complexity new features, product behavior...

- Repository: https://github.com/GanyuanRan/Aegis (1408 stars)
- Category: Design
- License: MIT
- Last updated: 2026-10-25
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add GanyuanRan/Aegis --skill brainstorming -g -a claude-code -y`
Codex: `npx skills add GanyuanRan/Aegis --skill brainstorming -g -a codex -y`
Cursor: `npx skills add GanyuanRan/Aegis --skill brainstorming -g -a cursor -y`
Gemini CLI: `npx skills add GanyuanRan/Aegis --skill brainstorming -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add GanyuanRan/Aegis`

## 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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

<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.

The rest: https://github.com/GanyuanRan/Aegis/blob/HEAD/skills/brainstorming/SKILL.md