Execute an existing implementation plan as written rather than re-planning the work from scratch.

Treat the plan as the source of truth for major steps and sequencing unless the user explicitly approves a change.

Expect the plan to be passed explicitly, preferably as an attached path such as @plan.md or @path/to/plan.md.

Workflow

Read the entire plan file before taking any action.
Inspect the current codebase enough to map each plan step to real files, modules, commands, and constraints.
Summarize that mapping briefly.
Reply with exactly: Plan loaded successfully. Starting Step 1: [Step title]
Execute one plan step at a time.
Before editing, show a concise diff preview describing the intended changes.
Apply only the edits needed for the current step.
Run the narrowest relevant validation first, then expand only as needed.
Report the validation result after the step.
Continue to the next step only when the current step is complete or the plan explicitly allows parallel work.

Plan Fidelity Rules

Execute an existing implementation plan as written rather than re-planning the work from scratch.

Treat the plan as the source of truth for major steps and sequencing unless the user explicitly approves a change.

Expect the plan to be passed explicitly, preferably as an attached path such as @plan.md or @path/to/plan.md.

Read the entire plan file before taking any action.
Inspect the current codebase enough to map each plan step to real files, modules, commands, and constraints.
Summarize that mapping briefly.
Reply with exactly: Plan loaded successfully. Starting Step 1: [Step title]
Execute one plan step at a time.
Before editing, show a concise diff preview describing the intended changes.
Apply only the edits needed for the current step.
Run the narrowest relevant validation first, then expand only as needed.
Report the validation result after the step.
Continue to the next step only when the current step is complete or the plan explicitly allows parallel work.