problem-record-creation

Create ITSM Problem Records from incident reports with root causes and remediation plans.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/DaBigHomie/ugwtf --skill problem-record-creation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-record-creation
Source: https://github.com/DaBigHomie/ugwtf/tree/main/.claude/skills/problem-record-creation
Command: npx skills add https://github.com/DaBigHomie/ugwtf --skill problem-record-creation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires cortex-api, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of ITSM Problem Records (PRMs) for recurring issues, ensuring that underlying causes are captured and addressed to prevent future incidents.

Core Features & Use Cases

  • Automated PRM Creation: Automatically generate PRMs from incident reports, capturing root causes and remediation plans.
  • Root Cause Analysis: Facilitates root cause analysis through the 5-whys method and identifies known errors.
  • Remediation Routing: Routes remediation tasks to appropriate owners and clusters for efficient resolution.
  • Framework Mapping: Maps PRMs to relevant frameworks like COBIT 2019, ISO 27001, and ISO 42001 for compliance.
  • Lifecycle Tracking: Tracks PRM lifecycle from open to closed, ensuring issues are resolved and documented.
  • Use Case: When an incident occurs that requires a deeper investigation and analysis to prevent recurrence, use this Skill to create a PRM that captures all necessary details and actions.

Quick Start

Create a Problem Record for the recent outage by running the command: 'create-prm "Outage on Dec 1st" --root-cause "Hardware failure" --remediation "Replace server"'

Frequently Asked Questions about problem-record-creation

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

FAQPage Schema
How do I automate ITSM Problem Record creation from incident reports?

Automating ITSM Problem Record creation involves parsing incident reports to capture root causes and remediation plans, then validating and persisting them via the Cortex API. This Skill uses scripts to generate PRMs for recurring issues.

What is the best way to document root cause analysis for recurring IT operations issues?

Documenting root cause analysis for recurring issues uses the 5-whys method to identify known errors and generate a Problem Record. This process captures underlying causes and maps remediation plans to appropriate owners.

Can I map ITSM Problem Records to compliance frameworks like COBIT 2019 and ISO 27001?

Yes, you can map Problem Records to compliance frameworks like COBIT 2019, ISO 27001, and ISO 42001. This ensures recurring issues and their remediation plans align with required governance and security standards.

Do I need the Cortex API to create and track Problem Records for incident remediation?

Yes, the Cortex API is required to create and track Problem Records. It provides the necessary interface for running validation scripts, routing remediation tasks, and persisting PRM lifecycle data from open to closed.

How do I route remediation tasks to the correct owners after identifying a known error?

Routing remediation tasks after identifying a known error involves clustering Problem Records and assigning them to appropriate owners. The Skill analyzes the PRM details to direct resolution actions to the correct teams.

What are the limitations of using scripts for Problem Record lifecycle tracking in ITSM?

Problem Record lifecycle tracking via scripts is limited by its dependency on the Cortex API for persistence and validation. It requires structured incident report inputs to successfully route remediation and map to compliance frameworks.