executing-plans

# Executing Plans ## Overview Load plan, review critically, execute all tasks, report when complete. **Announce at start:** "I'm using the executing-plans skill to implement this plan." For non-trivial plan execution, include `Aegis Visibility` in natural prose: name why Aegis is keeping the current slice tied to the approved plan, checkpoint, drift check, pre-edit governance, or verification boundary. This visibility belongs to the active execution workflow; do not replace it with a generic used-skills log. When execution reaches completion, do not invent a separate final report shape for this workflow. Pass plan adherence, checkpoint/drift status, verification, complexity, and residual risk into `verification-before-completion` so the user-facing closeout uses the unified Aegis impact/safety receipt. **Note:** Tell your human partner that Aegis works much better with access to subagents. The quality of its work will be significantly higher if run on a platform with subagent support (such as Claude Code or Codex). If subagents are available, use aegis:subagent-driven-development instead of this skill. ## The Process ### Step 1: Load and Review Plan 1. Read plan file 2. If the plan or active checkpoint includes an `Execution Readiness View`, read it before implementation and compare the plan against its intent lock, scope fence, baseline lock, owner / contract constraints, compatibility boundary, retirement boundary, test obligations, review gates, drift / ...