Skip to content

forcedotcom/sf-skills / skills/service-itsm-agentic-setup-incident-management

service-itsm-agentic-setup-incident-management

Verified

Orchestrator for Incident Management setup in Service Cloud ITSM: presents the features with live org status, and configures each — Incident preferences, Incident persona PSG assignment, Priority Matrix, SLA & Milestones, Incident dashboards, Email-to-Incident, Major Incident Management (approval group + MIM preferences), Broadcast Communications, Manage Incidents with AI, Service Management Privilege (privilege escalation), and audit tracking. Use for: set up or configure incident management, a walkthrough, what incident features can I configure; the incident preference toggles (default field validations, auto-close child incidents, auto-triage, assign with Einstein, restrict assigned group, rich text descriptions); assigning the Incident Fulfiller or Incident Manager persona PSG. DO NOT TRIGGER for: the master on/off switch alone (use the IncidentMgmt SOR), the Priority Matrix, SLA, or field history tracking alone, the Major Incident Manager PSG, creating/editing PSGs, or Problem/Change/Case Management.

references/priority-matrix.md

View on GitHub
# Feature: Priority Matrix (delegated to the `ItsmPriorityMatrix` SOR)

How the orchestrator runs the **Priority Matrix** feature, which maps each Impact × Urgency combination on
Incident to a Priority. The `ItsmPriorityMatrix` SOR's own steps and guidance decide *how*; the
orchestrator runs them itself under its **SOR hand-off protocol** and owns every user-facing gate. This file
adds what is specific to the Priority Matrix.

1. `discover` the SOR by intent (e.g. "incident priority matrix impact urgency") and `describe` the id
   `discover` returns (`ItsmPriorityMatrix`). Its own prerequisite checks fall under protocol step 2. The
   SOR serves Incident and Problem, so pass the entity type `Incident` on every call (`entityType` on the
   `Priority` read, the matrix reads, and the save; `details` on the default-priority reads).
2. Read first: the org's **active** Incident `Priority` values (`describe-priority-picklist` —
   never hardcode or invent them), the current rows (`fetch-priority-matrix`), both preferences
   (`read-priority-matrix-prefs`, one call each: `IncPriorityMatrixEnabled`, the *Turn on Automatic
   Priority Assignment for IT Service* toggle, and `IncPriorityOverrideEnabled`, the *Set priority
   manually* checkbox), and the default priority (`get-default-priority`).
3. Ask only for what's missing: which cells change, the default priority, and whether manual override
   changes. Offer only active values, and flag a saved row whose Priority is no longer active rather than
   dropping it. If the matrix is off, include turning it on in the plan — with it off, Incidents don't get
   a priority from the matrix.
4. **The save is a full replacement**: `save-priority-matrix` deletes every row it isn't sent. Build the
   complete set from the fetched rows, change only the cells the user asked to change, and keep the
   override as read unless asked. Show which cells are added, changed, or removed, the resulting default,
   and the override state, and get an explicit yes. Re-run `describe-priority-picklist` right
   before the save and send only its active values. A change to only the matrix toggle or only the
   override uses `update-priority-matrix-enablement` instead, one preference per call, confirmed the same
   way.
5. Read back with `verify-priority-matrix` (rows), `verify-default-priority`, and `verify-manual-override`
   (or `verify-priority-matrix-enablement` after a toggle-only change). Mark it `Done` only when every part
   matches.
6. Only after a real write landed this run — never on a view or a no-op — mark the Salesforce Go *Define
   Priority Matrix* step complete (`mark-priority-matrix-step-complete`, then
   `verify-priority-matrix-step-complete`). A `404` there doesn't fail the feature: tell the user to tick
   that step manually on the Salesforce Go page.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall