# Using Aegis

> Routes requests to Aegis skills based on intent, loading relevant skills for debugging, planning, and goal framing while keeping fast-path responses lightweight.

- Skill: `ganyuanran/using-aegis` (Agent Skill, multi-file: 6 files)
- Install (CLI): `npx skillmds@latest add ganyuanran/using-aegis`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ganyuanran/using-aegis/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools, Dev Tooling
- Tags: Aegis, Debugging, Intent Classification, Planning, Skill Routing
- Author: GanyuanRan (https://skillmd.com/u/ganyuanran)
- Updated: 2026-08-22
- Page: https://skillmd.com/skills/ganyuanran/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. Active codebase question/"what next": check README/ADR/rules/baseline, else
   bounded index-first scan. Non-trivial owners passively use relevant
   `CONTEXT-MAP.md`/`CONTEXT.md`; compose `establishing-project-context` only
   for semantic delta/conflict. Create baselines only with evidence.
3. Direct grilling or plan/design pressure-tests (`grill me`, `grill this plan`, `审问我`, `盘问我`, `拷问我`) route to `brainstorming`; literal/explanatory uses do not.
4. `/aegis-goal` or `Aegis goal:` loads `goal-framing` before routing.
5. Bug, failure, regression, or unexpected behavior routes to `systematic-debugging`; quick bug lane owns Change Necessity before source edits.
6. Classify before implementation/start/resume/compaction. Low: intent, baseline, verification. Medium/high: baseline read-set + plan (session-internal by default; docs only when the work needs durable cross-session direction or approval - Doc Necessity Gate). TDD: off=no auto route/load; auto=strict/light/skipped; explicit request applies. Spec Brief or Design Spec only for ambiguous/contract/cross-module medium/high work. Shared/core/contract/cross-module never low without evidence. Source edits/new paths: owner workflow surfaces Change Necessity.
7. Before the first repo write, the coordinator records `TaskStartSnapshot`.
   Complexity, TDD, planning, or subagents alone do not
   justify branch/worktree creation.
8. Non-tiny loaded skill: at first substantive user-visible stage say why Aegis is shaping work/risk; do not wait for the user to ask. structured trace only for audit/debug/release/long-task review/asked; `Trace Digest` does not route. Tiny stays implicit.
9. ArchitectureReviewRequired: yes for medium/high architecture/contract/
   cross-module/owner/source-of-truth/fallback/adapter/baseline; carry to
   verification.
10. Workspace support is lazy; use configured Aegis workspace support only when records needed. Fast Q&A/status/tiny edits write no files. **Doc Necessity Gate:** docs only for durable/irreversible, cross-session, approval-gated, or authority-required change surfaces; covered surfaces update the owner doc, never a sibling; mechanical changes write no docs (commit message + code comments as the record).
11. Load smallest needed skill/reference.
12. Tool/log/memory/search outputs are evidence candidates, not prompt payloads;
   summary first, large input index->window->excerpt.
13. No history/sessions/transcripts/large logs by default; bound requested
   evidence by scope/time/lines.
14. Unclear host tool-name mapping: read smallest relevant reference.

Contract: `Route: fast-path`; `Aegis Reason Note`.