Aegis Structured Execution

Use this skill for broad, risky, multi-phase, or proof-heavy work where execution state can drift.

Contract

Identify the deliverable, scope, non-goals, truth sources, and proof requirements.
Split work into phases only when trust boundaries, proof modes, or execution surfaces differ.
Keep final synthesis in the coordinator; helper agents may gather evidence but do not define final truth.
Separate current state, target state, validated proof, unresolved gaps, and drift.
Follow aegis-html-ledger throughout execution: record the active work before it begins and keep its actual state, plan changes, and exact resume point current in the local project ledger. Cloud copying is optional and requires authorization covering this project's records, the destination account and folder, and the content scope. Reuse valid existing authorization; selecting this skill alone does not grant it. With no such authorization, keep the ledger local, mark cloud sync as not enabled, and continue the work. Never copy credentials, private conversations, personal records, or restricted project content by implication.
Use completion messages through the established coordination route alongside the ledger to report the outcome and remaining work.
Report completion only at the strongest proven level: implemented, code_proven, test_proven, runtime_proven, or end_to_end_proven.

Establish whether the reported problem is real before creating its issue. Determine early whether the fix needs one PR or several.