project-surgeon-issue-changer

To manage project scope changes safely, this Skill pauses Phase 4 execution to run mandatory impact analysis on existing plans and source code. It only applies modifications after user approval, then resumes execution from the first affected task.

Impact analysis for change requests scans existing plans and source code to classify severity as light, moderate, or major. This matrix routes scope modifications to the correct resolution path, preserving unaffected work.

To apply incremental changes after a project is completed, use the post-completion mini-workflow. It plans and executes new scope changes through an abbreviated process while still requiring mandatory impact analysis and user approval.

No, you cannot modify source code or plans before user approval. Strict safety guardrails ensure no modifications occur until impact analysis is reviewed and explicitly confirmed by the user.

Change request state tracking is recorded in `.project-surgeon/state.json`. It logs every scope modification with lifecycle status and resolution metadata to maintain consistent project state.

The best way to prevent scope creep during mid-workflow plan modifications is enforcing mandatory impact analysis and controlled updates. This Skill pauses execution, analyzes severity, and updates only necessary tasks before resuming.