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/render-matrix.md
View on GitHub# Rendering the Matrix
Format the rows returned by `SELECT ... FROM ServiceOpPriorityConfig` (via `sf data query --use-tooling-api`) as an aligned Impact × Urgency grid. Use this layout both for the initial "view" operation and for the before/after snapshots around a mutation.
## Input
Tooling SOQL result body (`sf data query --json ...`):
```json
{
"result": {
"records": [
{ "Id": "1NHSG00000007374AA", "ReferenceObject": "Incident", "Impact": "High", "Urgency": "High", "Priority": "Critical" },
{ "Id": "1NHSG00000007384AA", "ReferenceObject": "Incident", "Impact": "High", "Urgency": "Medium", "Priority": "High" },
{ "Id": "1NHSG00000007394AA", "ReferenceObject": "Incident", "Impact": "Medium", "Urgency": "High", "Priority": "High" }
]
}
}
```
Row keys are PascalCase (`Id`, `ReferenceObject`, `Impact`, `Urgency`, `Priority`) — these are Tooling SObject field names.
Plus the active picklist values fetched from the Incident describe (used for the axes).
## Output layout
```text
Priority Matrix — Incident (3 of 9 cells configured)
Impact \ Urgency High Medium Low
------------------------------------------------
High Critical High ·
Medium High · ·
Low · · ·
Configured rows:
Impact=High Urgency=High -> Priority=Critical
Impact=High Urgency=Medium -> Priority=High
Impact=Medium Urgency=High -> Priority=High
```
Layout rules:
- Rows are the entity's `Impact` picklist values, columns are `Urgency` — both ordered as returned by describe (typically High → Medium → Low; do not reorder).
- Fill each cell with the matching row's `Priority`, or `·` if no row exists for that `(Impact, Urgency)` coordinate.
- Total cells expected = `|Impact| × |Urgency|`. Show `<configured>/<total>` in the header — do not hardcode 9.
- After the grid, list configured rows for easy copy/paste when composing a mutation.
## When to render
- **Phase 2** — the view operation and the before-snapshot for any mutation.
- **Phase 5** — after a write, render again as the after-snapshot.
Present both before and after when a mutation ran; users need the diff.
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 |