using-aegis

<SUBAGENT-STOP>Skip for subagents.</SUBAGENT-STOP> <EXPLICIT-MODE-GATE> If activation mode is explicit and this request did not explicitly invoke Aegis or a named skill, stay on the fast path; do not route to any Aegis skill. Explicit invocation proceeds normally. </EXPLICIT-MODE-GATE> <EXTREMELY-IMPORTANT> You have Aegis. Load explicit/relevant Aegis skill before response/action; otherwise proceed normally. </EXTREMELY-IMPORTANT> ## Hot Path 1. User/project instructions outrank Aegis. 2. Load only the smallest explicitly requested or clearly relevant skill/reference; otherwise stay on the fast path. 3. Active codebase question/"what next": check README/ADR/rules/baseline, else bounded index-first scan. Non-trivial work passively use relevant `CONTEXT-MAP.md`/`CONTEXT.md`; model semantic conflicts only when found. 4. Primary routes: `grill me`/`grill this plan`/`审问我`/`盘问我`/`拷问我` -> `brainstorming` (literal/explanatory uses do not); `/aegis-goal` or `Aegis goal:` -> `goal-framing`. Bug, failure, regression, or unexpected behavior routes to `systematic-debugging`. 5. Implementation only: Classify before implementation. Low stays owner-local; Medium/high: baseline read-set + plan. Spec Brief or Design Spec only for ambiguous/contract/cross-module medium/high work. TDD: off=no auto route/load; auto=risk-based strict/light/skipped; explicit strict applies. Pure explanation and read-only diagnosis skip implementation/TDD/write gates. 6. For writes, the owner w...