skills.rest
Soham407
Soham407COMMUNITY
Explore all skills by this author →
GitHub

triage

Convert GitHub issue discussions into structured triage outcomes with category and state labels.

1|Updated May 7, 2026
Search Tags:#github issues#state machine#out-of-scope#triage workflow#label management#agent briefs
One-click install
npx skills add https://github.com/Soham407/studio-kickstart --skill triage-soham407
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/Soham407/studio-kickstart/tree/main/architecture/matt-pocock-triage
Command: npx skills add https://github.com/Soham407/studio-kickstart --skill triage-soham407

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams triage GitHub issues reliably by moving them through a clearly defined state machine so the right work happens at the right time.

Core Features & Use Cases

  • Issue State Machine: Enforces a consistent set of category and state roles for every triaged issue, reducing ambiguity and rework.
  • Durable Agent Briefs: Produces AFK-ready agent briefs based on durable contracts (interfaces, behavior, acceptance criteria) rather than brittle implementation details.
  • Out-of-Scope Knowledge Base: Supports documenting rejected enhancements in an .out-of-scope/ concept library to prevent re-litigating the same decisions.

Quick Start

Tell an AI to triage a GitHub issue by moving it to the appropriate label state and, if needed, generate an agent brief with acceptance criteria and clear scope boundaries.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I triage GitHub issues into a structured workflow?▼

Triage GitHub issues by moving them through a state machine that assigns exactly one category label (bug or enhancement) and one state label, reducing ambiguity and ensuring consistent evaluation outcomes.

What is a state machine for GitHub issue label management?▼

A GitHub issue label management state machine enforces consistent category and state roles for every triaged issue, reducing ambiguity and rework by standardizing evaluation and handoff procedures.

How do I generate an agent brief for a bug reproduction?▼

Generate an agent brief by creating durable contracts based on interfaces, behavior, and acceptance criteria. The triage workflow supports optional bug reproduction and formats briefs for AFK agent handoff.

How do I document out-of-scope enhancements to prevent re-litigating decisions?▼

Document out-of-scope enhancements in an `.out-of-scope/` concept library. This knowledge base prevents teams from re-litigating the same wontfix decisions during future issue triage.

Can I use this triage workflow for human-only escalation of GitHub issues?▼

Yes, the triage workflow applies to human-only escalation and wontfix decisions alongside standard evaluation, clarification, and agent handoff, ensuring issues reach the appropriate resolution path.

When should I not use automated issue triage for GitHub issues?▼

Avoid automated issue triage when issues lack sufficient discussion for category assignment, or when durable agent brief formatting and OUT-OF-SCOPE.md integration cannot be applied to the workflow.

Related Skills

Explore More Product & Management Skills→
Davie521Davie521
7

triage

Generate structured agent briefs from GitHub and GitLab issue discussions.

Community
Advanced
shushuznshushuzn
4

triage

Triage GitHub issues through a state machine enforcing category and state role rules.

Community
Advanced
rnaarlarnaarla

triage

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

Community
Advanced
haryelramalhoharyelramalho

triage

Organize GitHub issues into triage states with next steps.

Community
Advanced