Use when defining new features, product behavior, UI/component design, architecture choices, contract changes, or ambiguous medium/high-complexity work before implementation.
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when a task is multi-step, may span context resets or sessions, uses subagents, or risks losing state before completion.
Use when the user asks to create, write, update, amend, supersede, or evaluate an ADR, architecture decision record, durable architecture decision, decision log, or baseline sync after architecture-changing work.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when strict TDD is explicitly requested, or when an approved atomic implementation task has already chosen TDD Route strict.
Use when the user says `aegis:update`, asks to update or upgrade an installed Aegis method-pack, wants the latest Aegis version, or asks whether Aegis is current on this host.
Use when starting a turn or checking Aegis skill routing.