pm-process-flowslisted

# PM - Process Flows (User Types + Process Maps + User Flows) ## Agent mode (`--agent`) Supports `--agent`: runs autonomously in a subagent, drafts the artifact from existing inputs, and returns a short summary + coverage note. - **No flag** → interactive (default); if inputs are heavy, offer agent mode. - **`--agent`** → obey. First check inputs are complete. Anything missing: do NOT invent it - mark `[ASSUMED - what/why]` in the output and summary. Never hallucinate to fill a gap. --- ## What this skill does Two connected outputs that bridge the domain model into design: 1. **System user types** - the actors/roles in the system (e.g. Admin, Courier, Dispatcher, Customer, System). Identified **adaptively**. 2. **Flows** - two views built on those user types: - **2A. Process map per domain / process area** - the end-to-end business process, for dev + design understanding. - **2B. User flows per user type, connected to screens** - how each user moves through the processes E2E, with screen touchpoints and UI behaviour, so a designer can complete the screen design from the user's perspective. This sits between the domain registers and per-feature design. `pm-feature-design`'s per-feature UX context (Section 3b) is atomic; this gives the **E2E big picture** across a module that the per-feature view then refines. **Lean by design (low maintenance):** process maps and flows reference entity states and attributes **by name** - they do NOT restate state machines or at