speckit-iterate-applylisted

## User Input ```text $ARGUMENTS ``` You **MUST** consider the user input before proceeding (if not empty). If the user provides arguments, treat them as adjustments or notes for the apply process (e.g., "skip task completion marking" or "only update spec.md and tasks.md"). The primary source of truth for what to change is `pending-iteration.md`. ## Outline Goal: Execute the iteration plan defined in `pending-iteration.md` by updating all spec artifacts that `speckit.implement` relies on. After apply completes, the user can go directly to `/speckit.implement` — skipping `/speckit.plan` and `/speckit.tasks` since this command already handles those updates. ### 1. Initialize Feature Context Run `.specify/scripts/bash/check-prerequisites.sh --json --paths-only` from repo root **once**. Parse JSON payload fields: - `FEATURE_DIR` - `FEATURE_SPEC` - (Optionally capture `IMPL_PLAN`, `TASKS` for downstream use.) If JSON parsing fails, abort and instruct the user to run `/speckit.specify` or verify the feature branch environment. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot"). ### 2. Load Pending Iteration Check for `FEATURE_DIR/pending-iteration.md`. If it does **not** exist, abort with: > No pending iteration found. Run `/speckit.iterate.define <change request>` first to define what you want to change. If it exists, read and parse the file: - **Frontmatter**: `status`, `created`, `change_req