source-command-ff-iterate-plan

Provide the plan file path and your feedback, such as adding a phase or adjusting scope. The Skill reads the entire plan, researches the codebase if needed, confirms the intended changes with you, then applies precise edits while preserving the existing structure.

Invoke the command with just the plan file path, and it will prompt you for the changes you want. If you provide no arguments at all, it first asks which plan file to update, then asks for your feedback before proceeding.

Yes, but only when the requested changes require new technical understanding. It spawns parallel research sub-tasks such as codebase-locator and codebase-analyzer with specific directory context, then waits for all results before editing.

Success criteria keep their two-category structure: automated verification using commands like make test, and manual verification for UI or edge cases. Updates ensure criteria remain measurable and reference specific file paths and line numbers.

Avoid it when no plan exists yet, since it requires an existing plan file to edit. It is also unnecessary for trivial typo fixes, as the process is designed for changes that may need research, confirmation, and consistency checks across plan sections.