What problem does it solve? When the agreed to-be process map needs to change mid-project, ad-hoc edits cause the map, backlog, and completed work to silently diverge. This Skill enforces a single consistent protocol for every process change, regardless of where the trigger surfaces. ## Core Features & Use Cases - Trigger capture and change documentation: Logs the source of every change (stakeholder input, demo gap, technical constraint, solo realization) and classifies it as a refinement, addition, or restructure before any work begins. - Three-tier impact scan: Audits scheduled, in-progress, and completed slices against the changed process step, assigning an explicit verdict to every item so nothing is assumed safe. - Decide, execute, re-prioritize, confirm: Applies solo-approved decisions (revise, retire, reopen, create, absorb), updates the to-be map and backlog, proposes a new build sequence, and gates resumption on explicit solo confirmation. - Use Case: During a build, a developer discovers an agreed process step is technically impossible. The Skill pauses work, logs the trigger, scans all slices for impact, updates the map and backlog, and re-sequences the remaining work before build resumes. ## Quick Start Tell the assistant that a step in the to-be process map needs to change and ask it to run the process change protocol to assess the impact and update the backlog.
