triage

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

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/The-Focus-AI/walking-thoughts --skill triage-the-focus-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/The-Focus-AI/walking-thoughts/tree/main/.agents/skills/triage
Command: npx skills add https://github.com/The-Focus-AI/walking-thoughts --skill triage-the-focus-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers drown in unlabeled issues and half-specified requests. This Skill runs a structured triage workflow that categorizes issues and external PRs, verifies claims against the codebase, grills reporters for missing detail, and produces durable agent-ready briefs so work can be delegated without re-litigating decisions. ## Core Features & Use Cases - State machine triage: Apply category roles (bug, enhancement) and state roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) to issues and external PRs, with conflict detection and maintainer overrides. - Codebase verification: Reproduce reported bugs, check out PR diffs to confirm they do what they claim, and detect already-implemented requests or prior rejections recorded in .out-of-scope/ files. - Agent brief authoring: Write durable, behavioral agent briefs with acceptance criteria and explicit scope boundaries, following the AGENT-BRIEF.md reference guide. - Use Case: A maintainer says "Let's look at #42". The Skill reads the issue, checks the codebase for existing implementations and prior rejections, verifies the claim, grills the reporter if details are missing, then posts a triage-notes comment or a full agent brief and applies the right labels. ## Quick Start Ask the assistant to triage issue #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 workflow with a natural-language request like "show me anything that needs my attention" or "let's look at #42". The assistant gathers issue context, checks the codebase for existing implementations, recommends a category and state, and applies labels with a comment 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, serving as the authoritative spec for an autonomous coding agent. It describes current and desired behavior, key interfaces, testable acceptance criteria, and explicit out-of-scope boundaries without referencing fragile file paths or line numbers.

Can triage handle external pull requests as well as issues?

Yes, when the issue-tracker config treats external PRs as a request surface, a PR is triaged as an issue with attached code using the same roles and states. The workflow additionally checks out the diff and runs relevant tests to verify the PR does what it claims.

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

Rejected enhancement requests are recorded as concept files in a .out-of-scope/ directory with the decision, reasoning, and links to prior issues. During triage, new requests 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.