activity-diagramlisted

# PMO Skill: Activity Diagram (Swimlane) > **Related Skills:** > - Always load `pmo-lark-plantuml` when writing .puml files > - Load `references/case-analysis.md` for detailed case examples > - Load `references/case-checklist.md` for the 20-item checklist > - Load `references/mom-validation.md` for MOM Validation Workflow --- ## 1. Always Use PlantUML Activity Diagram (Swimlane) Every diagram must use Swimlane syntax separating lanes by actor/system: ``` |#BackgroundColor|Actor Name| ``` --- ## 2. Ask Actor Before Creating **Must ask user every time before creating a diagram:** - How many actors/systems? - What is each actor's name? (e.g., Backend API, Admin, Frontend App, Customer App) Never assume actors without asking (unless user specifies them all in the request). --- ## 3. Lane Background Colors by Actor | Type | Color | Hex Code | Example Actor | |------|-------|----------|---------------| | Backend / API / Scheduler | Cream yellow | `#FFF9E0` | Backend API, Cron Job | | Admin / Back-office User | Light blue | `#E8F0FE` | Admin, Admin (Finance) | | Frontend / UI | Light green | `#EDF7E8` | Frontend App, Customer App | | External / 3rd Party | Light purple | `#F3E5F5` | Payment Gateway, SMS Provider | | Customer / End User | Light pink | `#FCE4EC` | Customer, User | Additional colors for extra actors: | Color | Hex Code | |-------|----------| | Light gray | `#ECEFF1` | | Light teal | `#E0F7FA` | | Light orange | `#FFF3E0` | --- ## 4. Syntax Rules ### 4.