project-surgeon-issue-changer

What problem does it solve?

It prevents scope creep and broken execution by managing change requests with mandatory impact analysis and controlled plan updates within a project-surgeon workflow.

Core Features & Use Cases

• Mid-workflow change handling (Mode A): Pauses Phase 4 execution, runs impact analysis, updates only what’s necessary, then resumes from the first affected task.
• Post-completion change handling (Mode B): Uses an abbreviated mini-workflow to plan and execute incremental changes after the project is marked completed.
• Impact Matrix with severity classification: Scans existing plans and source code to classify changes as light, moderate, or major, and routes to the correct resolution path.
• Strict safety guardrails: Ensures no code/plan changes occur before impact analysis and user confirmation, and preserves completed unaffected work.
• Change tracking in state.json: Records every change request in .project-surgeon/state.json with lifecycle status and resolution metadata.

Quick Start

Invoke /project-surgeon-issue-changer with your change description (for example: add “new requirement: notification system”) to pause, analyze impact, and apply an approved scope change to the active or completed project.