- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add GanyuanRan/Aegis --skill brainstorming -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add GanyuanRan/Aegis --skill brainstorming -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add GanyuanRan/Aegis --skill brainstorming -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add GanyuanRan/Aegis --skill brainstorming -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/GanyuanRan/Aegis/tree/HEAD/skills/brainstormingDe l'éditeur
Choose the route before reading references:
systematic-debugging; PR, diff,
or current-code review uses requesting-code-review; explicit goal framing
uses goal-framing. File count alone does not decide design complexity.Grilling Mode below; soft challenge intent
requires its one-line mode confirmation. Ordinary evaluation is not grilling.Default Design Path. Escalate depth from evidence:
contracts, owners, persistence, migration, security, consumers and blast radius.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.
grill me, grill this plan, 审问我, 盘问我, 拷问我, or an
explicit request to interrogate/pressure-test a plan enters this mode.Grill or normal brainstorming? and
enter only after confirmation.requesting-code-review.Grilling Mode overrides the normal brainstorming execution flow. Suspend the
Default Design Path, compact output contract, and documentation or planning
requirements until the user exits the interview; retain the no-implementation
gate. Only after entry, read grilling-mode-reference.md for interview pace,
opening, questions and exit procedure. Do not read it for ordinary design,
soft-intent confirmation, or literal phrase explanations.
Stop the interview when the user says stop, defer, or that questions are
sufficient. Its summary does not authorize planning or implementation; return
to the normal design approval gate if the user asks to proceed.
Track the applicable steps in order; conditional steps do not create tasks or artifacts until their trigger is met. Keep one workflow, not separate checklist, process and after-design passes.
CONTEXT.md/CONTEXT-MAP.md terms;
compose establishing-project-context only for a real semantic conflict.
Decompose independent subsystems before designing them. Define the user's
usable result, delivery and meaningful failure states; an unsupported action
remains an unmet need, not a reason to silently narrow the requirement.writing-plans, not another implementation
skill. For a scope ending at discussion or options, deliver that result;
do not advance beyond the user's request.Use natural, proportional prose, not a mandatory stack of named cards.
Aegis Visibility briefly explains the task-specific value of design first.
Keep these working drafts current as scope changes; they are in-session views
unless the Doc Necessity Gate requires persistence:
TaskIntentDraft: outcome, goal, success evidence, stop condition, non-goals,
scope and risks;BaselineReadSetHint: candidate authority refs and gaps;BaselineUsageDraft: required, delivered-context (optional), acknowledged,
cited and missing refs, plus the advisory decision;ImpactStatementDraft: affected layers, owners, invariants, compatibility
and non-goals.Present the relevant intent, evidence, impact, options and decision needed at this stage. Conditional lenses below add only their applicable findings; mentioning a lens does not activate its template. Do not repeat satisfied checks or emit empty cards. Preserve decision-relevant meaning and evidence limits.
Before writing any spec, plan, ADR or baseline artifact:
Resolve these directly without asking the user:
Ask the user only for:
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.
For design detail, read only the evidence-matched heading of
expanded-design-guidance.md, never the whole file. Do not load design detail
for route selection, first-turn clarification, route-away cases, or an active
Grilling Mode interview. The main file owns routing, approval and handoff;
references supply the selected procedure or template only.
Before approach selection, unresolved new/duplicate owners, fallback, adapter,
compat-only carrier, delete-first questions, unverified assumptions or a
"long-term stable" claim after Existence Check escalate to
first-principles-review and its Decision Hygiene Review; return here once
that decision surface is clean. Do not make this a universal design ceremony.
For narrower architecture coherence risks, use Architecture Integrity Lens:
invariant, canonical owner/contract, responsibility overlap, higher-level
simplification, retirement/falsifier and verdict. For internal retirement vs
compatibility retention vs persistent-state confirmation, compose anti-entropy-governance;
it chooses delete-first | compat-exception | confirmation-first without
transferring destructive authority to this skill.
For user-facing interface or interaction design, compose ui-ux-governance and
carry scoped experience rules into existing acceptance criteria. Design approval
and handoff remain here.
Approach selection is ready when:
Not every unknown must be eliminated; only decision-changing unknowns block convergence.
The design can hand off when all applicable conditions hold:
Design Complete is method readiness, not completion authority. Transition to writing-plans only after these conditions hold; do not carry unresolved decision-changing unknowns into the plan.
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
---name: brainstormingdescription: Use when defining ambiguous or high-complexity new features, product behavior, UI/component design…---# skills/brainstorming/SKILL.mdVue d'ensemble
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.
FAQ
Téléchargez skills/brainstorming/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/GanyuanRan/Aegis.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.