skills.rest
opensage-agent
opensage-agentOFFICIAL
Explore all skills by this author →
GitHub

triage

Manage GitHub issue lifecycle through state machine and role-based classification.

113|23|Updated Mar 23, 2026
Search Tags:#automation#github#triage#issue-tracking#project-management#agent-workflow
One-click install
npx skills add https://github.com/opensage-agent/opensage-adk --skill triage-opensage-agent
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/opensage-agent/opensage-adk/tree/main/src/opensage/bash_tools/triage
Command: npx skills add https://github.com/opensage-agent/opensage-adk --skill triage-opensage-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the bottleneck of manual issue tracking by providing a structured, state-machine-driven workflow that ensures every bug or feature request is properly categorized, evaluated, and prepared for agent-led implementation.

Core Features & Use Cases

  • State Machine Workflow: Automatically manages issue lifecycle roles like needs-triage, ready-for-agent, and wontfix.
  • Agent Brief Generation: Standardizes the creation of authoritative specifications for AFK agents to ensure high-quality, durable implementation.
  • Institutional Memory: Integrates with an out-of-scope knowledge base to prevent re-litigating previously rejected feature requests.

Quick Start

Invoke the triage skill to review all unlabeled issues and provide a summary of those requiring immediate 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 applying a state machine to manage the lifecycle of project issues, automatically categorizing and transitioning tasks from initial reporting to agent-ready specifications.

How do I generate standardized agent briefs from GitHub issues?▼

Generating standardized agent briefs requires transitioning evaluated GitHub issues into ready-for-agent states, producing authoritative specifications that ensure high-quality, durable implementation by AFK agents.

How can I prevent re-litigating rejected feature requests in issue tracking?▼

Preventing re-litigated feature requests requires maintaining institutional memory through an out-of-scope knowledge base that records wontfix decisions, ensuring previously rejected features are not re-evaluated.

Does automated issue triage require integration with GitHub issue trackers?▼

Automated issue triage requires integration with GitHub issue trackers to review unlabeled issues, apply role-based classification, and manage task transitions through the defined state machine workflow.

What is the best way to prepare software issues for agent-led implementation?▼

The best way to prepare issues for agent-led implementation is to use a structured triage workflow that evaluates bug or feature requests and generates standardized agent brief documentation.

When should I not use automated state machine workflows for project management?▼

Automated state machine workflows for project management are not suitable when issues require ad-hoc evaluation outside standardized lifecycle roles, or when GitHub issue tracker integration is unavailable.

Related Skills

Explore More Software Engineering Skills→
jonkraatzjonkraatz

triage

Automate issue categorization and workflow management through a defined state machine.

Community
Intermediate
ThorStarlordThorStarlord
1

triage

Assign category and state roles to GitHub issues for consistent routing.

Community
Advanced
felipeganamefelipeganame
2

github-project-management

Manage GitHub issues, project boards, and sprints via API.

Community
Advanced
MichaelSolatiMichaelSolati

triage

Enforce a GitHub issue triage state machine with consistent labeling and agent briefs.

Community
Intermediate