problem-management

Automate root-cause analysis workflows for ServiceNow problems and linked records.

77|23|Updated Jul 16, 2025
One-click install
npx skills add https://github.com/serac-labs/serac --skill problem-management-serac-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-management
Source: https://github.com/serac-labs/serac/tree/main/packages/opencode/src/bundled-skills/problem-management
Command: npx skills add https://github.com/serac-labs/serac --skill problem-management-serac-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates root-cause analysis and workflow management for ServiceNow problems, incidents, and their related records to accelerate containment and permanent fixes.

Core Features & Use Cases

  • Root Cause Analysis workflow creation and task coordination
  • Linking incidents to problems and tracking RCA progress
  • Documenting root causes, contributing factors, and Known Errors for knowledge sharing
  • Propagating fixes to Known Errors and aligning with change requests

Quick Start

Identify a problem record and initiate an RCA workflow with tasks and related incidents.

Frequently Asked Questions about problem-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate root-cause analysis workflows for ServiceNow problems?

Root-cause analysis workflows for ServiceNow problems are automated by creating problem records from incidents, coordinating RCA tasks, documenting root causes, and closing known errors across related records.

What is the process for linking incidents to problems for RCA tracking in ServiceNow?

Linking incidents to problems for RCA tracking in ServiceNow involves creating a problem record, associating related incidents, and coordinating workflow tasks to monitor analysis progress and document findings.

Can I propagate fixes to Known Errors and align them with change requests in ServiceNow?

Fixes can be propagated to Known Errors and aligned with change requests in ServiceNow by documenting root causes and contributing factors, then linking the resolution to the appropriate change records.

Does this approach support ES5 scripting for problem management tasks in ServiceNow?

ES5 scripting guidance is supported for problem management tasks in ServiceNow, ensuring workflow coordination and table structure manipulation remain compatible with the required scripting standards.

How do I document root causes and contributing factors for known errors in ServiceNow?

Documenting root causes and contributing factors for known errors in ServiceNow requires creating knowledge article links within the defined table structure to share findings and close related records.

What is the best way to create problems from incidents for root-cause analysis?

Creating problems from incidents for root-cause analysis is best handled by initiating an RCA workflow with tasks and related incidents, using a defined table structure to coordinate the investigation.