triage

Move GitHub issues and external PRs through a triage state machine with agent-ready briefs.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/MSC72m/DevForge --skill triage-msc72m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/MSC72m/DevForge/tree/main/skills/triage
Command: npx skills add https://github.com/MSC72m/DevForge --skill triage-msc72m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers drown in unlabeled issues and external PRs with no consistent process for categorizing, verifying, and specifying work. This Skill enforces a structured triage workflow that turns raw reports into verified, agent-ready specifications. ## Core Features & Use Cases - State machine triage: Move issues and PRs through canonical roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) with exactly one category and one state per item. - Verification and grilling: Reproduce bugs, check out PR diffs to confirm claims, and run structured question rounds to flesh out vague requests before assignment. - Agent brief generation: Write durable, behavioral agent briefs with acceptance criteria and scope boundaries, plus an .out-of-scope/ knowledge base that records rejected feature requests to prevent re-litigation. - Use Case: A maintainer runs triage on a backlog of 30 unlabeled issues; the Skill buckets them by attention needed, verifies each bug against the codebase, and posts agent briefs so AFK coding agents can pick up ready work immediately. ## Quick Start Ask the assistant to triage issue #42 and move it through the appropriate triage state with an agent brief.

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 agent?▼

Invoke the triage workflow in natural language, such as asking to look at a specific issue or show what needs attention. The Skill reads the full issue, verifies claims against the codebase, recommends a category and state, and posts triage notes or an agent brief.

What is an agent brief for GitHub issues?▼

An agent brief is a structured comment posted when an issue reaches ready-for-agent state. It describes desired behavior, key interfaces, testable acceptance criteria, and explicit out-of-scope boundaries so an autonomous coding agent can implement the change without further clarification.

Can triage handle external pull requests as well as issues?▼

Yes, external PRs are treated as issues with attached code and move through the same states. The Skill additionally checks out the diff and runs relevant tests to confirm the PR does what it claims before recommending a state.

How does the out-of-scope knowledge base prevent duplicate feature requests?▼

Rejected enhancement requests are recorded as concept files in an .out-of-scope/ directory with the decision, reasoning, and prior issue links. During triage, new issues are matched against these files by concept similarity so prior rejections are surfaced instead of re-litigated.

When should an issue go to ready-for-human instead of ready-for-agent?▼

Use ready-for-human when the work requires judgment calls, external access, design decisions, or manual testing that an autonomous agent cannot perform. The brief follows the same structure but notes why delegation is not possible.