# iterate-plan (Unified Skill)

## Core Instructions (SKILL.md)

# Iterate Implementation Plan

Update an existing implementation plan based on feedback and current codebase reality.

## Procedure

1. Read the current plan completely.
2. Understand the requested changes.
3. Research only if the requested change requires new technical context.
4. Confirm your understanding with the user before editing.
5. Make focused updates to the plan.
6. Present the changes and iterate until approved.

## Rules

- Preserve completed work unless the user explicitly wants to revise it.
- Prefer surgical edits over wholesale rewrites.
- Ask normal clarifying questions if the request is ambiguous.
- If the plan needs substantial restructuring, recommend creating a new plan.

## References

- Use `references/change-template.md` when summarizing planned edits.
- Use `references/common-scenarios.md` for common iteration patterns.


---

## Reference: change-template.md

```text
Based on your feedback, I understand you want to:
- [Change 1]
- [Change 2]

[If research was done]
My research found:
- [Relevant pattern or constraint]

I plan to update the plan by:
1. [Specific modification]
2. [Specific modification]

Does this align with your intent?
```


---

## Reference: common-scenarios.md

## Common Iteration Scenarios

- Adding a new phase
- Changing the implementation approach
- Adding missing detail
- Removing scope
- Splitting an oversized phase
- Correcting a technical error

For each case:
- identify the affected sections,
- research only what changed,
- update success criteria and dependencies if needed,
- preserve completed work.


---