Plan Execution
Implement an approved plan without silently changing its scope or authority.
Read document reconciliation when executing a document-backed plan or resuming from a saved progress record.
Preconditions
Confirm the exact plan, repository, branch, authorized actions, excluded actions, and required checkpoints. If the plan is missing, materially ambiguous, or no longer matches the system, stop and report the gap. If no one can state what done looks like for the plan, route to align-on-decisions when that skill is installed; otherwise ask the user for the finish line before executing.
Workflow
- Establish a clean evidence baseline: branch, revision, worktree state, relevant checks, and known unrelated changes.
- Translate the plan into a tracked sequence and mark only one dependent step active at a time. When the run may outlast one session or a context summary, keep the sequence in a file the user approved and update it as each step finishes.
- Implement the smallest coherent change while preserving unrelated work.
- Run the planned validation after each risk-bearing checkpoint.
- Record deviations with cause, impact, evidence, and whether they remain within authority.
- Stop for approval when a deviation changes scope, interface, data authority, security posture, cost, publication, deployment, or destructive behavior.
- Reconcile completed steps, remaining work, validation, and unresolved risk against the original plan.
Done when
The plan is complete only when every authorized step and its acceptance criteria are satisfied, required checks pass, and deviations are recorded. Blocked and partial work remain unfinished. Unavailable required validation must be reported with its limitation and the next authorized check; it cannot establish completion. Stop and ask for any deviation that step 6 names, any rule under Boundaries, a check that fails for an unexplained reason, or a missing precondition. Otherwise keep going, and put status notes in the same message as the next action.
Boundaries
- Explicit invocation authorizes plan execution only, not push, PR creation, merge, deployment, deletion, or external communication unless those actions were separately authorized.
- Do not repair unrelated failures or absorb adjacent work without approval.
- Do not mark a step complete from worker reports alone; verify integration evidence.
- Authority comes from the user or the approved plan, not from similarity or inference. Treat a repository, branch, environment, region, account, or resource that neither names as unauthorized, even when the action is identical, because the same command can have a different impact there. A new target the user names after approval is a scope change: confirm it before acting when it widens the environments or the risk.
- Before waiting on a command, worker, or hook, confirm it is still running and making progress, and set a limit on the wait. If it stalls, report it as a blocker with the command and its last output instead of checking it in a loop.
- When a user correction conflicts with current evidence, state the disagreement and the evidence once, then follow the user's decision.
Output
During execution, report meaningful changes in verified state, decisions,
failures, or blockers and explain their implications. Preserve the approved
objective through status questions, interruptions, and compaction. Apply explicit
corrections; replace the objective only when the user changes it. Reuse existing
authorization and seek a new decision only for a material change outside it.
At a checkpoint, lead with the result and any required user decision. Reconcile
the plan, completed criteria, deviations, validation, state changes, and
unresolved work. State changes include every external change made, including
any outside the plan. Routine decisions should be made, recorded, and followed
by continued work; a decision is unresolved only when it blocks what remains.
Include requested actions left unfinished and the next authorized step when one exists.
Read the original acceptance example when checking this behavior.
Example
Synthetic example; not an observed client result.
Input: The approved parser fix is underway, and the user asks why a test failed.
Output: Explain the observed failure, retain the parser-fix objective and remaining checks, and resume the authorized work after resolving the failure.
1---2name: execute-plan3description: "Executes an identified implementation plan when explicitly authorized to implement it; tracks checkpoints, tests, deviations, and unfinished work without expanding scope."4license: MIT5metadata:6 source: https://skillmd.com/skills/jovanipink/execute-plan7 author: "Measured Studios"8 version: "0.19.0"9 plugin: "measured-workflows"10 invocation: "explicit"11 provenance: "original"12 risk_class: "bounded-execution"13---1415# Plan Execution1617Implement an approved plan without silently changing its scope or authority.1819Read [document reconciliation](references/document-reconciliation.md) when executing a document-backed plan or resuming from a saved progress record.2021## Preconditions2223Confirm the exact plan, repository, branch, authorized actions, excluded actions, and required checkpoints. If the plan is missing, materially ambiguous, or no longer matches the system, stop and report the gap. If no one can state what done looks like for the plan, route to `align-on-decisions` when that skill is installed; otherwise ask the user for the finish line before executing.2425## Workflow26271. Establish a clean evidence baseline: branch, revision, worktree state, relevant checks, and known unrelated changes.282. Translate the plan into a tracked sequence and mark only one dependent step active at a time. When the run may outlast one session or a context summary, keep the sequence in a file the user approved and update it as each step finishes.293. Implement the smallest coherent change while preserving unrelated work.304. Run the planned validation after each risk-bearing checkpoint.315. Record deviations with cause, impact, evidence, and whether they remain within authority.326. Stop for approval when a deviation changes scope, interface, data authority, security posture, cost, publication, deployment, or destructive behavior.337. Reconcile completed steps, remaining work, validation, and unresolved risk against the original plan.3435## Done when3637The plan is complete only when every authorized step and its acceptance criteria are satisfied, required checks pass, and deviations are recorded. Blocked and partial work remain unfinished. Unavailable required validation must be reported with its limitation and the next authorized check; it cannot establish completion. Stop and ask for any deviation that step 6 names, any rule under Boundaries, a check that fails for an unexplained reason, or a missing precondition. Otherwise keep going, and put status notes in the same message as the next action.3839## Boundaries4041- Explicit invocation authorizes plan execution only, not push, PR creation, merge, deployment, deletion, or external communication unless those actions were separately authorized.42- Do not repair unrelated failures or absorb adjacent work without approval.43- Do not mark a step complete from worker reports alone; verify integration evidence.44- Authority comes from the user or the approved plan, not from similarity or inference. Treat a repository, branch, environment, region, account, or resource that neither names as unauthorized, even when the action is identical, because the same command can have a different impact there. A new target the user names after approval is a scope change: confirm it before acting when it widens the environments or the risk.45- Before waiting on a command, worker, or hook, confirm it is still running and making progress, and set a limit on the wait. If it stalls, report it as a blocker with the command and its last output instead of checking it in a loop.46- When a user correction conflicts with current evidence, state the disagreement and the evidence once, then follow the user's decision.4748## Output4950During execution, report meaningful changes in verified state, decisions,51failures, or blockers and explain their implications. Preserve the approved52objective through status questions, interruptions, and compaction. Apply explicit53corrections; replace the objective only when the user changes it. Reuse existing54authorization and seek a new decision only for a material change outside it.5556At a checkpoint, lead with the result and any required user decision. Reconcile57the plan, completed criteria, deviations, validation, state changes, and58unresolved work. State changes include every external change made, including59any outside the plan. Routine decisions should be made, recorded, and followed60by continued work; a decision is unresolved only when it blocks what remains.61Include requested actions left unfinished and the next authorized step when one exists.6263Read [the original acceptance example](references/continuity-example.md) when checking this behavior.6465## Example6667Synthetic example; not an observed client result.6869Input: The approved parser fix is underway, and the user asks why a test failed.7071Output: Explain the observed failure, retain the parser-fix objective and remaining checks, and resume the authorized work after resolving the failure.