triage

Manages issue lifecycles through a state machine and triage roles.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the chaos of unmanaged issue trackers by providing a structured state machine for triaging bugs and feature requests, ensuring every issue is clearly defined and actionable.

Core Features & Use Cases

  • State Machine Workflow: Enforces consistent lifecycle management for issues from initial triage to agent-ready status.
  • Deduplication & Knowledge Base: Integrates with an out-of-scope knowledge base to prevent re-litigating previously rejected feature requests.
  • Agent Brief Generation: Standardizes the creation of authoritative specifications for AFK agents, ensuring work is durable and context-aware.

Quick Start

Run the triage skill to analyze the current issue tracker and identify items that require immediate maintainer attention.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I automate GitHub issue triage with a state machine workflow?

Automating GitHub issue triage involves enforcing a defined state machine to transition issues from initial reporting to agent-ready specifications. This Skill standardizes lifecycle management, ensuring every bug and feature request is clearly defined and actionable.

How can I prevent duplicate feature requests in my issue tracker?

Preventing duplicate feature requests requires integrating an out-of-scope knowledge base that maintains a persistent record of rejected features. This stops the continuous re-litigation of previously closed or declined enhancements.

What is the best way to generate agent-ready specifications from GitHub issues?

Generating agent-ready specifications requires standardizing documentation practices for bug reproduction and enhancement scoping. This creates authoritative, context-aware agent briefs for AFK workflows, ensuring work remains durable and consistently defined.

How does issue tracking workflow automation handle unmanaged project backlogs?

Issue tracking workflow automation handles unmanaged backlogs by applying a structured triage role system to analyze the issue tracker. It identifies items requiring immediate maintainer attention and transitions them into actionable states.

Can I use this triage workflow for both bug reproduction and enhancement scoping?

Yes, this triage workflow supports both bug reproduction and enhancement scoping by implementing standardized documentation practices. It manages the entire software project issue lifecycle, ensuring consistent engineering workflows for both types.

What are the limitations of using a state machine for issue lifecycle management?

State machine issue lifecycle management requires strict adherence to defined state transitions and triage roles. Issues remain unmanaged if maintainers bypass the standardized documentation practices required to reach agent-ready status.