using-aegis

<SUBAGENT-STOP>Subagents skip this skill.</SUBAGENT-STOP>

<EXTREMELY-IMPORTANT> You have Aegis.

Before any response or action, check whether an Aegis skill is explicitly requested or clearly relevant. Load only that skill; otherwise proceed normally. </EXTREMELY-IMPORTANT>

Hot Path Rules

1. User and project instructions outrank Aegis.
2. Active codebase question or "what next": check baseline candidates (README/ADR/rules/docs/aegis/baseline). If none fit, run a bounded index-first scan, create a baseline only with evidence, and still answer.
3. /aegis-goal or Aegis goal: loads goal-framing for goal, success evidence, stop condition, and non-goals before onward routing.
4. Classify before implementation and on start/resume/compaction. Low: concise intent + baseline check + TDD. Medium/high: baseline read-set + plan. Add Spec Brief or Design Spec only when complexity, ambiguity, contracts, or cross-module impact require it. Contract, shared module, core logic, and cross-module changes are never low without local evidence.
5. Mark ArchitectureReviewRequired: yes for medium/high, architecture, contract, cross-module, owner, source-of-truth, fallback/adapter, or project-baseline tasks. Carry it to verification-before-completion.
6. Workspace support is lazy. Global install and fast-path Q&A/status/tiny edits never write project files. Baseline/spec/plan/work records use configured Aegis workspace support only when persistent evidence is needed; backfill on escalation.
7. Load the smallest needed skill/reference.
8. Treat tool outputs, logs, memories, and search results as evidence candidates, not prompt payloads: summarize first; for large inputs use bounded index→window→excerpt.
9. Do not read historical sessions, transcripts, history.jsonl, .codex/sessions, ~/.claude/projects, or large logs by default. Only read direct evidence when requested or required, with scope/time/line bounds.
10. If host tool-name mapping is unclear, read the smallest relevant reference.

Contract when useful: Route: fast-path; Why; Next.

Need More Detail?

For full trigger rules, Red Flags, Skill Priority, and platform notes, read references/skill-discipline.md only when these rules are insufficient.