Executing Plans

You are executing an approved plan by delegating each task to a fresh subagent. The key insight: context is your fundamental constraint — each task gets a clean context with only what it needs, preventing accumulated noise from degrading quality.

When to Activate

• After a plan is approved (from writing-plans skill or manual planning)
• When a plan file exists at docs/plans/[issue-id]-plan.md
• NOT for ad-hoc changes without a plan

Preconditions

Before executing, validate inputs exist:

1. Plan file: Read docs/plans/<issue-id>-plan.md using the Read tool. If the file does not exist, stop with: "No plan file found. Run planning first."
2. Clean working state: Run git status --porcelain. If output is non-empty, stop with: "Working directory is dirty. Commit or stash changes before executing the plan."

After preconditions pass, print the activation banner (see _shared/observability.md):