triage

Assesses issue tickets and assigns status, priority, and tags per project contract.

2|Updated May 24, 2026
One-click install
npx skills add https://github.com/CivicActions/ai-runbook-jh --skill triage-civicactions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/CivicActions/ai-runbook-jh/tree/main/skills/triage
Command: npx skills add https://github.com/CivicActions/ai-runbook-jh --skill triage-civicactions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the bottleneck of unorganized ticket backlogs by providing a consistent, repeatable framework for initial assessment, ensuring every issue is evaluated, prioritized, and tagged without manual overhead.

Core Features & Use Cases

  • Standardized Assessment: Applies a uniform decision-making process (Keep/Defer/Decline) to all incoming tickets.
  • Project-Specific Integration: Dynamically pulls tracker fields, priority guides, and review markers from your project contract.
  • Use Case: Use this when a new bug report or feature request arrives to quickly determine if it is actionable, set its initial priority, and flag it for the next stage of refinement.

Quick Start

Run the triage skill on the provided ticket content to assess its validity and set the initial project priority.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I automatically prioritize and tag new issue tickets?

To automatically prioritize and tag new issue tickets, you can use a first-touch assessment process that evaluates incoming bug reports and feature requests against project-specific contracts, determining their status and setting initial priority levels for refinement.

What is the best way to organize an unorganized ticket backlog?

The best way to organize an unorganized ticket backlog is to apply a standardized assessment framework that evaluates every issue with a uniform decision-making process, ensuring each item is categorized, tagged, and prioritized without manual overhead.

Do I need a project contract file to perform ticket intake and backlog grooming?

Yes, you need a project contract file to perform ticket intake and backlog grooming, as it dynamically defines tracker fields, priority guides, and review markers required to correctly categorize and tag actionable items.

How does first-touch ticket assessment work for new bug intake?

First-touch ticket assessment works by applying a uniform Keep, Defer, or Decline decision-making process to new bug intake, evaluating each issue's validity and setting its initial project priority based on predefined tracker fields.

Can I use this standardized assessment for feature requests as well as bug reports?

Yes, you can use this standardized assessment for feature requests as well as bug reports, applying the same prioritization and tagging framework to quickly determine if any incoming issue is actionable and flag it for refinement.

When should I not use an automated prioritization workflow for issue tracking?

You should not use an automated prioritization workflow for issue tracking if your project lacks a defined contract file specifying tracker fields and priority levels, as the assessment relies on these to categorize and tag items correctly.