Slash Command

/triage

Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.

Install

npx claudepluginhub kylburns89/servicenow-claude-plugins --plugin plugin

Details

Argument[INC number, priority filter, or description]

Allowed Tools

mcp__plugin_servicenow_servicenow__list_recordsmcp__plugin_servicenow_servicenow__get_recordmcp__plugin_servicenow_servicenow__create_recordmcp__plugin_servicenow_servicenow__update_recordmcp__plugin_servicenow_servicenow__list_cimcp__plugin_servicenow_servicenow__get_cimcp__plugin_servicenow_servicenow__get_ci_relationshipsmcp__plugin_servicenow_servicenow__get_table_schema

Prompt Preview

# /servicenow:triage

Route based on `$ARGUMENTS`:

## No arguments or general request
If `$ARGUMENTS` is empty, contains "what's on fire", "open", "recent", or "list":
- Run the **List Recent Incidents** workflow from the `triaging-incidents` skill.
- Show open incidents sorted by priority, highlight any P1/P2.

## Specific INC number
If `$ARGUMENTS` contains an INC number (e.g., "INC0010001"):
1. Find the incident: `list_records(table_name="incident", query="number=$ARGUMENTS", limit=1)`
2. Run the **Investigate an Incident** workflow — get full details, check CI dependencies, find simila...

Command Content

Other plugins with /triage

/triage

Decomposes a large feature into multiple dependency-aware specs with graphs and interface contracts. Manages git branches, active epics, and delegates to subagents. Accepts epic-name and goal.

ralph-specum

268

/triage

Investigates a bug from provided description or error, determines root cause, and files GitHub issue with TDD fix plan.

ReadGlobGrep+3

agentic-dev-team

/triage

Triages findings from code reviews, audits, or analysis by presenting each for categorization by severity, category, effort, then creates or updates ready todo files in todos/ directory on user approval.

compound-engineering

/triage

Triages open tasks: fetches list and action history via tq task list, determines phase (unstarted, implementing, review/stalled/blocked/done-ish), summarizes per project in tables, proposes organization actions for approval.

/triage

Analyze issue to determine optimal workflow path

jira-orchestrator

/triage

Reviews git state across worktrees, stashes, and branches to inventory work in progress.

git

Stats

Stars7

Forks4

Last CommitMar 1, 2026

Actions

View Source View Plugin View on GitHub View README

/servicenow:triage

Route based on $ARGUMENTS:

No arguments or general request

If $ARGUMENTS is empty, contains "what's on fire", "open", "recent", or "list":

Run the List Recent Incidents workflow from the triaging-incidents skill.
Show open incidents sorted by priority, highlight any P1/P2.

Specific INC number

If $ARGUMENTS contains an INC number (e.g., "INC0010001"):

Find the incident: list_records(table_name="incident", query="number=$ARGUMENTS", limit=1)
Run the Investigate an Incident workflow — get full details, check CI dependencies, find similar incidents, check related problems/changes.
Present findings with recommended actions.

Priority filter

If $ARGUMENTS contains "P1", "P2", "critical", or "high priority":

Filter incidents by the specified priority level.
Run the List Recent Incidents workflow with the appropriate priority filter.

Triage request

If $ARGUMENTS contains "triage", "assess", or "new":

Run the Triage a New Incident workflow — assess impact/urgency, check CI blast radius, suggest priority and assignment.

Trend analysis

If $ARGUMENTS contains "trends", "analysis", "bulk", or "SLA":

Run the Bulk Analysis workflow — top categories, repeat CIs, SLA breaches.

Fallback

For any other input, treat $ARGUMENTS as a search term:

list_records(table_name="incident", query="short_descriptionLIKE$ARGUMENTS^active=true", limit=10)
Present matching incidents and offer to investigate any of them.