problem-analysis

Automate root cause analysis and problem management workflows for ServiceNow incidents.

34|13|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/Happy-Technologies-LLC/happy-servicenow-skills --skill problem-analysis-happy-technologies-llc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-analysis
Source: https://github.com/Happy-Technologies-LLC/happy-servicenow-skills/tree/main/skills/itsm/problem-analysis
Command: npx skills add https://github.com/Happy-Technologies-LLC/happy-servicenow-skills --skill problem-analysis-happy-technologies-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Root cause analysis and problem management in ServiceNow; it helps teams identify recurring incidents, document root causes, and manage known errors and permanent fixes.

Core Features & Use Cases

  • Identify problem candidates from incidents and group patterns
  • Perform RCA using 5-Whys and Fishbone analysis
  • Create problem records, link related incidents, document known errors and workarounds, and track fixes

Quick Start

Identify a series of related incidents and start a new problem record to begin RCA using this skill.

Frequently Asked Questions about problem-analysis

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

FAQPage Schema
How do I perform root cause analysis for recurring incidents in ServiceNow?

Root cause analysis for recurring ServiceNow incidents is automated by creating problem records, grouping incident patterns, and applying structured 5-Whys or Fishbone analysis to identify underlying issues.

When do I need to create a problem record instead of just resolving individual incidents?

Create a problem record when multiple incidents share patterns or a recurring issue requires formal root cause analysis, documented workarounds, and tracking toward a permanent fix.

Can I document known errors and workarounds alongside problem management?

Known errors and workarounds are documented directly within the problem management workflow, linking related incidents and known errors via MCP and REST endpoints for comprehensive knowledge capture.

Does this approach support structured RCA techniques like 5-Whys and Fishbone analysis?

Structured RCA techniques including 5-Whys and Fishbone analysis are fully supported, enabling data-driven problem identification and systematic documentation of root causes within ServiceNow.

How do I link related incidents to a known error for better tracking?

Related incidents are linked to known errors and problem records using MCP and REST endpoints, ensuring all recurring issues, workarounds, and permanent fixes are tracked together.

What is the best way to identify problem candidates from multiple incidents?

Problem candidates are identified by analyzing multiple incidents to group shared patterns, triggering formal root cause analysis when recurring issues require structured documentation and fixes.