triage

Triage GitHub issues through a label-driven state machine with agent briefs.

2|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/brandtam/rubber-ducky-legacy --skill triage-brandtam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/brandtam/rubber-ducky-legacy/tree/main/.agents/skills/triage
Command: npx skills add https://github.com/brandtam/rubber-ducky-legacy --skill triage-brandtam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers drown in untriaged issues: bugs without reproductions, feature requests without specs, and no durable record of why features were rejected. This Skill moves issues through a consistent state machine so every issue ends up classified, specified, and routed to the right owner. ## Core Features & Use Cases - State machine triage: Routes issues through needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix states, each paired with a bug or enhancement category. - Agent brief generation: Writes durable, behavior-focused agent briefs with acceptance criteria so AFK agents can implement issues without re-reading stale context. - Out-of-scope knowledge base: Records rejected feature requests in .out-of-scope/ files and surfaces prior rejections when similar requests reappear. - Use Case: A maintainer says "show me anything that needs my attention" and gets three buckets — unlabeled, needs-triage, and needs-info with new reporter activity — then picks an issue, reproduces the bug, and posts an agent brief moving it to ready-for-agent. ## Quick Start Ask the assistant to triage issue number 42 and recommend a category and state with reasoning.

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 with an AI assistant?▼

Invoke the triage skill and describe what you want in natural language, such as "show me anything that needs my attention" or "let's look at #42". The skill reads the full issue, recommends a category and state, and applies labels and comments after your confirmation.

What is an agent brief for GitHub issues?▼

An agent brief is a structured comment posted when an issue moves to ready-for-agent. It describes current and desired behavior, key interfaces, testable acceptance criteria, and explicit out-of-scope boundaries so an autonomous agent can implement it without stale file references.

How do I track rejected feature requests in a repository?▼

Rejected enhancements are recorded as markdown files in a `.out-of-scope/` directory, one file per concept, capturing the decision, reasoning, and links to prior requests. During triage, new issues are matched against these files to surface previous rejections.

Can I override the triage state machine directly?▼

Yes. Saying something like "move #42 to ready-for-agent" applies the role directly after a confirmation of the role changes, comments, and closures. Grilling is skipped, though the skill asks whether you want an agent brief written.

What happens when a bug report lacks enough detail to triage?▼

The skill attempts reproduction first by tracing code and running tests. If detail is insufficient, it posts triage notes listing what is established and specific actionable questions for the reporter, then applies the needs-info state.