speckit-iterate-apply

To apply a pending iteration plan, run the iteration apply command to read `pending-iteration.md` and update specification artifacts like `spec.md`, `plan.md`, and `tasks.md` in dependency order. It deletes the pending iteration file after successful completion.

Spec-document drift occurs when specification artifacts become inconsistent with implementation expectations. Prevent it by applying a planned pending iteration that enforces dependency-order updates across `spec.md`, `plan.md`, and `tasks.md` to keep all artifacts synchronized.

Yes, syncing specification artifacts requires the correct repository structure and an existing `pending-iteration.md` file. The workflow guards against missing prerequisites by enforcing feature-context initialization via speckit prerequisites before applying coordinated edits.

Yes, you can apply spec iterations without losing completed tasks or stable requirement IDs. The process preserves stable IDs and never silently edits `[x]` completed tasks, ensuring existing implementation work remains intact during consistency validation.

The best way to update multiple specification artifacts consistently is using an iteration apply workflow that enforces dependency-order updates across `data-model.md`, `plan.md`, `tasks.md`, `quickstart.md`, and `research.md` based on a central pending iteration plan.