forcedotcom/sf-skills / skills/service-itsm-incident-priority-configure
service-itsm-incident-priority-configure
FlaggedConfigures the Incident Priority Matrix for Salesforce ITSM through the sf CLI — enabling or disabling the matrix, shaping the Impact x Urgency grid that derives Priority on Incident records, toggling the manual-override preference, and reading or setting the default fallback priority. Reads every value before writing, is idempotent, and requires explicit user confirmation before any mutation. Use when the user wants to view, enable, disable, set up, seed, add to, change, or remove priority matrix configuration for Incident records, change the default incident priority, or asks about incident priority setup, impact/urgency mapping, override, or the ITSM incident priority matrix. DO NOT TRIGGER for Problem or ChangeRequest priority matrices, Case priority fields, standard Priority picklists outside ITSM, SLA or milestone configuration, or enabling Incident Management itself (use the service-itsm-incident-mgmt-configure skill).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 22.2 KB |
| examples/matrix-operations.md | markdown | 9.4 KB |
| examples/render-matrix.md | markdown | 2.2 KB |
| examples/seed-full-matrix.md | markdown | 3.5 KB |
| references/sf-cli-invocation.md | markdown | 16.1 KB |
examples/seed-full-matrix.md
View on GitHub# Seeding a Full Matrix
Seed all cells at once with the conventional Impact × Urgency mapping. With the sf-CLI Tooling API path, each cell is its own POST — there is no server-side "replace whole matrix" endpoint. Compose the plan first, confirm with the user, then dispatch one POST per cell.
## Pre-requisites
1. Fetch the entity's active picklist values — see `../references/sf-cli-invocation.md` § Picklist extraction.
2. Read the current matrix rows via Tooling SOQL. If the matrix is non-empty and the user asked to *seed*, ask whether they want to **replace** (delete existing rows first) or **augment** (add only missing cells) — do not seed blindly on top of existing rows.
3. Confirm the conventional mapping below uses only values in the fetched picklists. If the org has customized picklists, adjust the plan before dispatch — do not silently coerce.
## Conventional mapping (defaults only)
```text
Impact ↓ / Urgency → High Medium Low
High Critical High Moderate
Medium High Moderate Low
Low Moderate Low Low
```
Treat as a starting point; customers often grow to 4–5 levels per axis and add `Trivial` / `Emergency`. Confirm the resulting priorities with the user before dispatch.
## Dispatch — one POST per row
Replace `<alias>` with the user's target-org alias. Pick starting `<unique>` as `max(current DeveloperName suffix) + 1`, incrementing for each row.
```bash
# One row per POST — repeat for each of the nine cells.
# Pass each body inline with --body '{...}'; sf api request rest also accepts
# --body @file, but inline keeps the payload in the skill's control.
sf api request rest \
"/services/data/v67.0/tooling/sobjects/ServiceOpPriorityConfig" \
--method POST \
--header "Content-Type:application/json" \
--body '{"ReferenceObject": "Incident", "Impact": "High", "Urgency": "High", "Priority": "Critical", "DeveloperName": "ServiceOpPriorityConfigIncidentSeed0", "MasterLabel": "ServiceOpPriorityConfigIncidentSeed0"}' \
--target-org <alias>
# Repeat for rows 1–8 with the mapping above (increment the Seed<N> suffix).
```
Each POST returns `201 {"id": "<Id>", "success": true}`. If any POST returns a non-2xx, halt and surface the raw response — do not continue seeding partially.
For a scripted seed, iterate the mapping array in the caller's language of choice (bash + `jq`, node, etc.). Every row must be validated against the Phase-1 picklists before dispatch — the Tooling REST endpoint accepts garbage values silently.
## Replace vs. augment
The Tooling API path is not atomic across rows. Two choices:
**Augment (recommended):** For each conventional row, check the Phase-2 snapshot. Only POST rows whose `(Impact, Urgency)` coordinate is not already present. Existing rows keep their current Priority. The server does NOT enforce uniqueness on `(ReferenceObject, Urgency, Impact)`, so a POST on an already-present coordinate silently persists as a duplicate row — dedup is client-side only.
**Replace:** First `sf data delete record --sobject ServiceOpPriorityConfig --use-tooling-api --record-id <Id>` for every existing row, then POST the conventional set. Between the delete and the last POST the matrix is *partially populated* — the runtime priority derivation will use whatever rows are present at each moment. Warn the user before choosing replace.
Do not seed blindly on an entity with existing rows — surface the current state and confirm the intended semantics (replace vs. augment) with the user before Phase 4.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |