triage

Move issues and external PRs through a label-driven triage state machine on the issue tracker.

2|Updated Jul 25, 2026
One-click install
npx skills add https://github.com/ankaboot-source/boucle --skill triage-ankaboot-source
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/ankaboot-source/boucle/tree/main/.jcode/skills/triage
Command: npx skills add https://github.com/ankaboot-source/boucle --skill triage-ankaboot-source

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers drown in unlabeled issues and external PRs with no consistent process for categorizing, verifying, and routing them. This Skill enforces a structured triage workflow that turns raw reports into agent-ready briefs, human-ready tasks, or documented rejections. ## 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) with conflict resolution and precedence rules. - Verification and grilling: Reproduce reported bugs, check out PR diffs to confirm claims, and run structured questioning to flesh out vague requests before routing them. - Agent brief generation: Write durable, behavior-focused agent briefs with acceptance criteria and scope boundaries, following the AGENT-BRIEF.md reference. - Out-of-scope knowledge base: Record rejected enhancements in .out-of-scope/ files and deduplicate repeat requests against prior decisions. - Use Case: A maintainer runs triage on a backlog of 30 unlabeled GitHub issues; the Skill buckets them by attention needed, verifies each bug claim against the codebase, and posts agent-ready briefs for the ones that are fully specified. ## Quick Start Ask the assistant to triage issue #42 or show everything on the tracker that needs attention.

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 such as looking at a specific issue number or showing everything needing attention. The assistant reads the issue, verifies claims against the codebase, and applies category and state labels with triage notes.

How do I write a good agent brief for a GitHub issue?

Describe desired behavior rather than implementation steps, avoid file paths and line numbers that go stale, and include concrete acceptance criteria plus explicit out-of-scope boundaries. The AGENT-BRIEF.md reference provides a full template with bug, enhancement, and PR examples.

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 state machine. The assistant additionally checks out the diff and runs relevant tests to confirm the PR does what it claims before routing it.

What happens when a feature request is rejected during triage?

Rejected enhancements are recorded in a .out-of-scope/ directory with the decision, reasoning, and links to prior requests. Future matching issues are deduplicated against these files and closed as wontfix unless new evidence changes the decision.

When should an issue go to ready-for-agent versus ready-for-human?

Issues with fully specified, verifiable acceptance criteria go to ready-for-agent with an agent brief attached. Work requiring judgment calls, external access, design decisions, or manual testing goes to ready-for-human with a note explaining why it cannot be delegated.