What problem does it solve? Software projects drift from the agreed business process because no authoritative process map exists to hold design, build, and test decisions accountable. This Skill captures how a process works today and how it should work after the product is built, then enforces that agreement across every phase. ## Core Features & Use Cases - As-Is Mapping: Documents the current process exactly as it exists, including manual steps, spreadsheets, email handoffs, and workarounds, saved as Mermaid flowcharts in docs/process/. - To-Be Process Contract: Produces a validated target-state map that every screen, backlog slice, and test scenario must trace back to. - Drift Detection: Flags gaps and contradictions during design sprints, slice definition, build, and phase testing, requiring explicit decisions before any process change. - Use Case: During discovery for a player evaluation tool, the solo describes a spreadsheet-based workflow. The Skill maps it as-is, drafts the to-be flow, and later flags that no slice covers the escalation branch shown in the agreed map. ## Quick Start Activate guided mode and describe how your current process works so the as-is and to-be process maps can be drafted and validated.
