triage

Apply state-machine transitions to triage issues on a tracker.

Updated May 11, 2026
One-click install
npx skills add https://github.com/cloudofgeorge/AI-hands --skill triage-cloudofgeorge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/cloudofgeorge/AI-hands/tree/main/skills/engineering/triage
Command: npx skills add https://github.com/cloudofgeorge/AI-hands --skill triage-cloudofgeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage issues on a project issue tracker through a state-machine driven workflow, providing deterministic roles and transitions to reduce ambiguity and manual back-and-forth.

Core Features & Use Cases

  • State-machine guided triage with canonical roles and transitions (needs-triage -> needs-info -> ready-for-agent/ready-for-human -> wontfix)
  • Automatic generation of agent briefs when an issue is ready for an agent
  • Reference to prior rejections via the .out-of-scope knowledge base during triage to prevent duplication

Quick Start

Describe a triage scenario and issue to begin the guided triage process.

Frequently Asked Questions about triage

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

FAQPage Schema
What is state-machine driven issue triage and how does it standardize project workflows?

State-machine driven issue triage applies deterministic roles and transitions, such as needs-triage to ready-for-agent, to project trackers. This standardizes bug and enhancement handling by reducing manual back-and-forth and ensuring decisions are traceable.

How do I use a state machine to triage GitHub issues and generate agent briefs?

To triage GitHub issues, describe a triage scenario and the specific issue to initiate the guided process. The workflow transitions issues through canonical states and automatically generates an agent brief when an issue becomes ready-for-agent.

Can I prevent duplicate issue triage outcomes for previously rejected enhancements?

Yes, the triage process references prior rejections via an out-of-scope knowledge base during the workflow. This prevents duplication by checking previously rejected bugs and enhancements before making new triage decisions.

Does this triage workflow support distinguishing between tasks for human review and automated agents?

Yes, the state-machine workflow explicitly separates outcomes into ready-for-agent and ready-for-human states. This canonical transition structure ensures issues are routed to the correct handler based on their triage requirements.

What are the limitations of using canonical state transitions for issue tracker workflows?

The workflow limits issue tracking to predefined canonical states like needs-info and wontfix. Issues requiring custom workflow statuses outside this state-machine driven triage process may not fit the standardized transition model.