process-maplisted

## What this skill does Produces a structured process map with swim lanes, task nodes, decision diamonds, and handoff arrows. Output is in **Mermaid** flowchart notation (renderable in GitHub, VS Code, Confluence, and Miro) or **BPMN-lite** text when a formal notation is required. It also generates a companion process narrative for documentation. ## When to use it - User asks to "map a process", "document a workflow", or "draw an AS-IS/TO-BE diagram". - User needs to identify bottlenecks, redundancies, or handoff gaps in an existing process. - User is designing a new process and needs a visual spec before implementation. - User wants to feed the output into a `miro-board` or include it in a `requirements-document`. ## Key concepts ### AS-IS vs. TO-BE | | AS-IS | TO-BE | | --- | --- | --- | | **Purpose** | Document what currently happens, including workarounds and pain points | Define the improved or target process | | **Annotation** | Mark pain points (⚠), manual steps (M), and system steps (S) | Mark new capabilities (NEW) and removed steps (REMOVED) | | **Output** | Evidence base for improvement | Specification for change | ### Process map elements | Element | Notation | Mermaid syntax | | --- | --- | --- | | Start / End | Circle | `([Start])` / `([End])` | | Task / Activity | Rectangle | `[Task name]` | | Decision | Diamond | `{Decision?}` | | Sub-process | Double border | `[[Sub-process]]` | | Data store | Cylinder | `[(Data store)]` | | Swim lane | Subgraph | `su