client-flow-diagramslisted

# Client Flow Diagrams Produce diagrams that help non-technical audiences understand a process — not engineers understand a system. ## Trigger **Use this skill when:** - Creating or revising a business-level workflow, process, or integration diagram for a client or stakeholder - Translating technical documentation (ADRs, architecture notes, code flows) into a client-safe diagram - The audience includes business owners, product managers, client representatives, or non-technical staff - The diagram needs to show system interactions, decision points, or phase boundaries without code-level detail **Do not use this skill when:** - Creating detailed implementation architecture for developers - Documenting code-level control flow (use a developer-facing ADR instead) - The user only needs an internal engineering diagram - A diagram would not improve communication over plain text ## Workflow ### 1 — Clarify before diagramming Confirm or ask: - **Audience**: Who will read this? What is their technical background? - **Purpose**: What decision or understanding should the reader leave with? - **Scope**: Which systems, phases, and boundaries are in and out of scope? - **Detail level**: Does the reader need error paths and decision points, or just the happy path? When source material is technical (ADRs, code, API docs), treat it as confirmed. Treat your own inferences about business meaning as assumptions — flag them and ask when uncertain. ### 2 — Identify actors, systems, and bou