triage

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

Updated Jul 22, 2025
One-click install
npx skills add https://github.com/MichaelSolati/mkai --skill triage-michaelsolati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/MichaelSolati/mkai/tree/main/profiles/productivity/skills/triage
Command: npx skills add https://github.com/MichaelSolati/mkai --skill triage-michaelsolati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unstructured GitHub issue triage leads to inconsistent labeling, duplicated work, and issues stuck in limbo without clear ownership or next steps, wasting maintainer time and delaying project progress.

Core Features & Use Cases

  • Standardized State Machine Triage: Enforce consistent bug/enhancement categorization and state progression (needs-triage, ready-for-agent, wontfix, etc.) across all project issues.
  • Durable Agent Brief Generation: Create implementation-agnostic, context-rich specs for AFK agents that remain useful even as the codebase evolves.
  • Out-of-Scope Knowledge Base: Track rejected feature requests with decision reasoning to prevent duplicate re-litigation and preserve institutional memory.
  • Use Case: A maintainer handling 50+ monthly GitHub issues can use this skill to automate triage workflows, ensure consistent labeling, prepare clear handoff specs for autonomous agents, and avoid rehashing previously rejected feature requests.

Quick Start

Use the triage skill to review all unlabeled and needs-triage GitHub issues and generate a prioritized list of items requiring your 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 for bug reports and feature requests?

Automate GitHub issue triage using an enforced state machine to standardize bug and enhancement categorization, ensuring consistent labeling and clear progression steps for project maintainers.

What is the best way to hand off implementation-ready issues to autonomous coding agents?

Hand off implementation-ready issues by generating durable, implementation-agnostic agent briefs that provide context-rich specifications, ensuring autonomous coding agents receive clear and persistent tracking data.

How can I track rejected feature requests to prevent duplicate work on GitHub?

Track rejected feature requests in an out-of-scope knowledge base that preserves institutional decision context and reasoning, preventing duplicate re-litigation and reducing maintainer work.

Can I use a state machine to enforce consistent issue labeling across a large GitHub project?

Yes, you can enforce consistent issue labeling across large projects using a standardized state machine that manages state progression like needs-triage, ready-for-agent, and wontfix.

Why do GitHub issues get stuck in limbo without clear ownership during project maintenance?

Issues get stuck during project maintenance due to unstructured triage workflows that lack enforced state progression, resulting in inconsistent categorization and delayed handoff to autonomous agents.

Does this triage workflow generate agent briefs that remain useful as the codebase evolves?

Yes, the triage workflow generates implementation-agnostic agent briefs designed to remain context-rich and durable, preserving their utility for autonomous agents even as the codebase evolves.