executing-plans

1# Executing Plans
2 
3## Overview
4 
5Load plan, review critically, execute all tasks, report when complete.
6 
7**Announce at start:** "I'm using the executing-plans skill to implement this plan."
8 
9For non-trivial execution, include `Aegis Visibility`: briefly tie the active
10slice to its plan, checkpoint, drift or verification boundary. At completion,
11pass plan adherence, evidence, complexity and residual risk to
12`verification-before-completion` for the unified receipt.
13 
14If subagents are available and the plan has genuinely independent tasks,
15prefer `subagent-driven-development`; lack of subagent support does not block
16inline execution. Same-task agents share one workspace, and the coordinator
17remains the only Git mutation owner.
18 
19## The Process
20 
21### Step 1: Load and Review Plan
221. Read plan file
232. If the plan or active checkpoint includes an `Execution Readiness View`,
24   read it before implementation and compare the plan against its intent lock,
25   scope fence, baseline lock, owner / contract constraints, compatibility
26   boundary, retirement boundary, test obligations, review gates, drift /
27   rewind rules, and evidence required before completion.
283. Review critically - identify any questions or concerns about the plan
294. If the view contradicts the plan, baseline, or current worktree evidence,
30   return to plan review or refresh the advisory handoff before editing.
315. Run the TDD Route Guard before implementation: confirm `Mode`, `Decision`, `Strict authority`,
32…