Purpose

• oil:get_customer_context({ customer }) for vault-first prefetch (account IDs, known opportunity GUIDs).
• msx-crm:list_accounts_by_tpid({ tpid }) if TPID is provided.
• msx-crm:get_my_active_opportunities({ customerKeyword }) to discover opportunities by name.

Layout Specification

Node hierarchy

Account (top-level container)
├── Opportunity 1 (grouped by MCEM stage)
│   ├── Milestone A (color-coded by status)
│   │   └── Tasks (collapsed unless blockers)
│   └── Milestone B
├── Opportunity 2
│   └── ...
└── Deal Team (side panel)
    ├── Role: Person
    └── ...

Element types and styling

MCEM stage colors

Role colors (deal team panel)

Excalidraw Output Format

Generate a valid Excalidraw JSON scene wrapped in an Obsidian-compatible code block. The structure must follow Excalidraw v2 schema:

{
  "type": "excalidraw",
  "version": 2,
  "source": "mcaps-iq",
  "elements": [
    {
      "type": "rectangle",
      "id": "<unique-id>",
      "x": 0, "y": 0,
      "width": 300, "height": 60,
      "backgroundColor": "<fill>",
      "strokeColor": "<border>",
      "strokeWidth": 2,
      "roundness": { "type": 3 },
      "boundElements": [{ "type": "text", "id": "<text-id>" }]
    },
    {
      "type": "text",
      "id": "<text-id>",
      "x": 10, "y": 15,
      "text": "<label>",
      "fontSize": 16,
      "containerId": "<parent-rect-id>"
    },
    {
      "type": "arrow",
      "id": "<arrow-id>",
      "startBinding": { "elementId": "<from>", "focus": 0, "gap": 5 },
      "endBinding": { "elementId": "<to>", "focus": 0, "gap": 5 }
    }
  ],
  "appState": { "gridSize": null, "viewBackgroundColor": "#ffffff" }
}

Layout algorithm

• Y-axis: group opportunities by MCEM stage (Stage 1 at top → Stage 5 at bottom).
• X-axis: milestones flow left-to-right within each opportunity by msp_milestonedate.
• Deal team panel: positioned to the right of the main structure.
• Spacing: 120px vertical between opportunity rows, 160px horizontal between milestone columns.
• Container width: scale to content; minimum 800px wide.

ID generation

Use deterministic IDs derived from CRM entity IDs: acc-{accountid}, opp-{opportunityid}, ms-{milestoneid}, role-{systemuserid}.

Decision Logic

• If >10 opportunities: group by solution play (msp_salesplay) into collapsible clusters; show counts per cluster. Expand only At Risk / Blocked opportunities by default.
• If single opportunity: expand fully with all milestones and tasks visible.
• If role lens active: dim (reduce opacity to 30%) elements outside the role's accountability scope.
• If vault stakeholder map available: add stakeholder nodes linked to their associated milestones.
• If stage divergence detected (from mcem-stage-identification): add a warning badge on the opportunity node showing CRM: Stage X → Functional: Stage Y.

Output Schema

• diagram: Excalidraw JSON scene in ```excalidraw code block
• summary: one-paragraph natural language description of the account structure
• health_snapshot: counts by status (on_track, at_risk, blocked, completed)
• stage_distribution: opportunity count per MCEM stage
• role_coverage: deal team members mapped to their owned milestones
• next_action: suggests follow-up skill based on findings — e.g., pipeline-hygiene-triage if stale items detected, risk-surfacing if At Risk milestones found, milestone-health-review for governance prep
• connect_hook_hint: Impact Area(s): Customer Impact, Culture & Collaboration — "Generated account structure diagram for {customer}: {n} opportunities across Stages {stages}, {health_snapshot}"