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>

Outcome Anchor

Understand the requested object, scope, actions, conditions, and deliverables from the conversation. Complete the authorized task within business constraints and deliver a usable, verifiable result. Project goals guide durable choices; they do not override the user's current scope. Preserve outstanding intent across follow-ups; clarify material ambiguity before dependent action and continue independent authorized work. Do not repeat satisfied approvals.

Judge success by the requested outcome. Execution, parsing, tests, and architecture alignment prove only their covered scope; tests of real acceptance criteria can prove that outcome. Fix the problem class at its owner, preserving neighboring behavior. Report delivered results and remaining gaps honestly; partial work is not complete. These are decision principles, not a new artifact, universal goal-framing route, or completion authority.

Preserve task fidelity through understanding, transformation, execution and delivery: retain decision-relevant meaning and evidence status, checking both omissions and unsupported additions. Authorized summaries, designs and evidence-based corrections are valid. Use existing checkpoints and sufficient current evidence; no extra approval, six-item report or exhaustive trace is required.

Hot Path