speckit-iterate-define

To plan a feature iteration from a change request, the Skill analyzes your request against existing spec files and git diff history, then writes a reviewable pending-iteration.md file without modifying current artifacts.

A pending iteration plan in spec-kit is a reviewable document generated by analyzing a change request against current feature spec state and task progress, ensuring spec changes are planned rather than guessed.

You can analyze task impact for a change request by parsing task status and git diff history against existing spec artifacts. This cross-check determines what is already built before generating an impact summary.

No, the iteration planning workflow does not modify existing spec files. It safely writes only a pending-iteration.md file to your feature directory after you confirm the presented impact summary.

Yes, you need to run prerequisite checks before generating an iteration plan. The workflow requires executing the repo check-prerequisites.sh script to validate your environment paths before analyzing the change request.

The best way to triage a change request scope is to classify it as feature-wide, phase, task, subtraction, or pivot based on your current spec state, producing a concrete impact summary for confirmation before planning.