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 execution, include `Aegis Visibility`: briefly tie the active slice to its plan, checkpoint, drift or verification boundary. At completion, pass plan adherence, evidence, complexity and residual risk to `verification-before-completion` for the unified receipt. If subagents are available and the plan has genuinely independent tasks, prefer `subagent-driven-development`; lack of subagent support does not block inline execution. Same-task agents share one workspace, and the coordinator remains the only Git mutation owner. ## 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 / rewind rules, and evidence required before completion. 3. Review critically - identify any questions or concerns about the plan 4. If the view contradicts the plan, baseline, or current worktree evidence, return to plan review or refresh the advisory handoff before editing. 5. Run the TDD Route Guard before implementation: confirm `Mode`, `Decision`, `Strict authority`, strict signals...