Execute Implementation Plan
Implement plan tasks sequentially while keeping the plan, code, and verification results aligned.
Safety Rules
- Read the plan and project instructions before editing.
- Ask before editing when task order, target files, acceptance criteria, verification, or scope is unclear.
- Do not use destructive git commands unless explicitly requested and approved.
- Do not auto-rebase, squash, push, publish, or create releases.
- Respect existing uncommitted changes. Never revert user changes without explicit instruction.
- Execute only the requested scope.
Clarifying Questions
- Ask before implementation if the selected task, plan order, scope, required files, or acceptance criteria are missing, contradictory, or unclear.
- Do not proceed on assumptions that affect behavior, tests, data, APIs, release actions, or user changes.
- Ask numbered questions with lettered options; option A must be recommended. Continue only when the next task can be completed without decision-critical assumptions.
Do Not Trigger
- No existing plan or checklist.
- Exploratory design or tradeoff analysis.
- Publishing releases, pushing branches, or rewriting history.
Execution Loop
- Establish baseline: read the plan, check git status, identify the next incomplete task.
- Implement one coherent task: read relevant files, make the smallest scoped change, add/update tests.
- Verify immediately with focused commands. Fix failures before moving on.
- Update plan state only after work is done; record blockers and newly required work without silently changing scope.
- Stop when the next task needs user input, credentials, external systems, or a scope change.
- Run broader verification listed in the plan when selected scope is complete.
Commit Policy
- Do not commit unless the user explicitly asks.
- If commits are requested, commit only completed logical units with passing verification.
- Never amend, rebase, squash, or push unless explicitly requested.
Output
**Implemented**
- [Changed behavior.]
**Files**
- [Touched files.]
**Verification**
- `[command]`: [passed/failed/not run + reason]
**Remaining**
- [Blockers, skipped checks, or risks.]
Done Criteria
- Selected plan scope is complete or explicitly blocked.
- Verification was run when available.
- Skipped verification and remaining risks are reported.
1---2name: execute-implementation-plan3description: Safely execute an existing implementation plan task by task. Use when the user asks to implement, execute, run, continue, or finish a plan file or checklist, especially plans under docs/plans or Codex-created implementation plans.4---56# Execute Implementation Plan78Implement plan tasks sequentially while keeping the plan, code, and verification results aligned.910## Safety Rules1112- Read the plan and project instructions before editing.13- Ask before editing when task order, target files, acceptance criteria, verification, or scope is unclear.14- Do not use destructive git commands unless explicitly requested and approved.15- Do not auto-rebase, squash, push, publish, or create releases.16- Respect existing uncommitted changes. Never revert user changes without explicit instruction.17- Execute only the requested scope.1819## Clarifying Questions2021- Ask before implementation if the selected task, plan order, scope, required files, or acceptance criteria are missing, contradictory, or unclear.22- Do not proceed on assumptions that affect behavior, tests, data, APIs, release actions, or user changes.23- Ask numbered questions with lettered options; option A must be recommended. Continue only when the next task can be completed without decision-critical assumptions.2425## Do Not Trigger2627- No existing plan or checklist.28- Exploratory design or tradeoff analysis.29- Publishing releases, pushing branches, or rewriting history.3031## Execution Loop32331. Establish baseline: read the plan, check git status, identify the next incomplete task.342. Implement one coherent task: read relevant files, make the smallest scoped change, add/update tests.353. Verify immediately with focused commands. Fix failures before moving on.364. Update plan state only after work is done; record blockers and newly required work without silently changing scope.375. Stop when the next task needs user input, credentials, external systems, or a scope change.386. Run broader verification listed in the plan when selected scope is complete.3940## Commit Policy4142- Do not commit unless the user explicitly asks.43- If commits are requested, commit only completed logical units with passing verification.44- Never amend, rebase, squash, or push unless explicitly requested.4546## Output4748```markdown49**Implemented**50- [Changed behavior.]5152**Files**53- [Touched files.]5455**Verification**56- `[command]`: [passed/failed/not run + reason]5758**Remaining**59- [Blockers, skipped checks, or risks.]60```6162## Done Criteria6364- Selected plan scope is complete or explicitly blocked.65- Verification was run when available.66- Skipped verification and remaining risks are reported.
gslava