pm-process-flowslisted

Identifies the system's user types (actors) and maps end-to-end processes - both a lean business process map per domain (for dev + design understanding) and per-user-type user flows connected to screens (a designer brief). User-type identification is adaptive - analyse the docs, confirm with the user, ask if unsure, or propose from context. Process maps reference entity states by name and do NOT duplicate them (low-maintenance). Phase 4-5 bridge into design; feeds pm-feature-design's UX context and the designer (impeccable / Figma).
ljucask/pureinn-product-development · ★ 2 · AI & Automation · score 78

Install: claude install-skill ljucask/pureinn-product-development

# 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. --- ## Standalone run Runs with or without a Pureinn workspace - it needs no other skill's artifact, so it works as a single tool from an install that never ran `/pureinn`. - No workspace: create just the folder this skill writes into, or write to a path the user names, and say where the file went. Do not scaffold a project, do not invent a `state.json`, and do not send the user to `/pureinn` first. - Read `pureinn-variables.md` / `state.json` where a value is actually used, not at the top of the run. Missing value: continue and name the capability it costs. --- ## 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,