forcedotcom/sf-skills / skills/service-itsm-agentic-setup-incident-management
service-itsm-agentic-setup-incident-management
VerifiedOrchestrator 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 21.1 KB |
| examples/output-templates.md | markdown | 8.1 KB |
| references/audit-tracking.md | markdown | 3.3 KB |
| references/broadcast-communications.md | markdown | 1.9 KB |
| references/email-to-incident.md | markdown | 1.8 KB |
| references/incident-dashboards.md | markdown | 2.2 KB |
| references/incident-persona-psg.md | markdown | 2.9 KB |
| references/incident-preferences.md | markdown | 3.1 KB |
| references/major-incident-management.md | markdown | 2.9 KB |
| references/manage-incidents-with-ai.md | markdown | 3.2 KB |
| references/priority-matrix.md | markdown | 2.8 KB |
| references/service-mgmt-privilege.md | markdown | 2.9 KB |
| references/sla-milestones.md | markdown | 9.0 KB |
| references/status-checks.md | markdown | 22.4 KB |
references/audit-tracking.md
View on GitHub# Feature: Audit Tracking (delegated to the `FieldHistoryTracking` SOR)
How the orchestrator runs the **Audit Tracking** feature — field history on the Incident fields the user
chooses — over Salesforce's **Field History Tracking SOR**. This file re-derives none of the SOR's steps —
the SOR's own steps and guidance decide *how*. The orchestrator runs them under its **SOR hand-off
protocol** and owns the user-facing gates:
1. `discover` the SOR by intent (e.g. "field history tracking") and `describe` the id `discover` returns
(`FieldHistoryTracking`). Judge availability by what the calls return, not by a step's `status` label —
a step labelled `proposed` may still be served. A `discover` miss or a `401`/`403`/`404` means the
surface isn't available to this user or org: surface it and stop.
2. Use the Incident fields the user already named, or ask which fields to track if the choice is missing
or ambiguous, plus anything else `describe` says it needs. If the user chooses no fields, leave the
feature `Not done` and stop; do not treat an empty choice as already configured.
3. Through the SOR, check Setup access, read Incident with `get-single-entity-data-with-metadata`, and get
its per-object tracked-field limit. Use the returned tracking flag, field labels, `canBeTracked` values,
current tracked set, and `fieldEnumOrId` keys to resolve the user's choices; do not guess field keys.
4. The save replaces the object's whole tracked-field set, so send the **union** of what's already tracked
and the chosen fields using their returned keys, with Incident's object-level tracking flag on — never
drop an already-tracked field unless the user asks. If a chosen field can't be tracked, or the union
would exceed the limit, say so plainly; never untrack another field to make room. Report it as done
with no write only if the nonempty chosen set is already tracked **and** Incident's object-level tracking
is on. If the fields are selected but that flag is off, the change still needs a save.
5. Show the exact final tracked-field list by field label (disambiguate matching labels) in either case.
Before any save, also show that object-level tracking will be enabled and get an explicit yes
(`AskUserQuestion`) for that plan; when the user already named the fields, this confirms the selection.
6. After any save, read Incident's tracked fields back through the SOR. Mark the feature `Done` only when
the live read (for the no-write case) or post-save read-back shows Incident's object-level tracking on,
the chosen fields tracked, and no field dropped that the user didn't ask to drop — a save response alone
is not proof.
## Rules
- ALWAYS keep every already-tracked Incident field in the save unless the user asked to stop tracking it,
confirm the exact final field list before the save, and verify by read-back before marking it `Done` (or
verify the already-configured state by live read with no write) — the SOR asks the user nothing itself
## Before marking it `Done`
- [ ] A live metadata read resolved the fields and complete labeled set; any save kept every
already-tracked field the user didn't ask to drop, was confirmed before it ran, and was verified by
read-back; a no-write `Done` also had Incident's object-level tracking confirmed on
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |