triage

Automate issue triage with state-machine roles and artifact generation.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/rnaarla/agent_skills --skill triage-rnaarla
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/rnaarla/agent_skills/tree/main/skills/engineering/triage
Command: npx skills add https://github.com/rnaarla/agent_skills --skill triage-rnaarla

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage organizes issue evaluation by applying a defined state-machine of roles, ensuring consistent categorization and routing while surfacing relevant context for agents and humans.

Core Features & Use Cases

  • Canonical category and state roles to guide triage decisions.
  • Generates and references artifacts (AGENT-BRIEF.md, OUT-OF-SCOPE.md) to document decisions and rationale.
  • Integrates with trackers to surface context from .out-of-scope/ and related references during evaluation.
  • Supports transitions between needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix to maintain process discipline.

Quick Start

Provide the issue details and run /triage to start triage.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I automate issue triage for my GitHub workflow?

Automate issue triage by applying a defined state-machine of roles to classify and route work. This ensures consistent context, grading, and artifact generation across trackers like GitHub.

What is a state-machine approach for issue tracking and categorization?

A state-machine approach for issue tracking enforces canonical category and state transitions. It routes work through defined roles, maintaining process discipline during evaluation.

How do I transition issues between needs-info and ready-for-agent states?

Transition issues between needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix states to maintain process discipline. The state-machine enforces these canonical state transitions.

Can I use triage automation to generate agent briefs for issues?

Yes, triage automation triggers artifact updates to generate AGENT-BRIEF.md or OUT-OF-SCOPE.md when needed. These artifacts document decisions and rationale during evaluation.

Does the triage workflow support referencing out-of-scope issues during evaluation?

Yes, the triage workflow integrates with trackers to surface context from .out-of-scope/ and related references. This ensures relevant context is available for agents and humans during evaluation.

What's the best way to enforce consistent categorization across issue trackers?

Enforce consistent categorization by applying canonical category and state roles through a state-machine. This organizes issue evaluation and surfaces relevant context for work routing.