issue-triage

Name: issue-triage
Availability: InStock
Author: xtrm-dev

Reorganize flat issue backlogs into structured dependency graphs.

4|1|Updated Nov 1, 2025

Search Tags:#workflow #beads #backlog #issue-triage #dependency-graph #duplicate-detection

Ready to run

npx skills add https://github.com/xtrm-dev/specialists --skill issue-triage-xtrm-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-triage
Source: https://github.com/xtrm-dev/specialists/tree/main/.xtrm/skills/default/issue-triage
Command: npx skills add https://github.com/xtrm-dev/specialists --skill issue-triage-xtrm-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a messy open-issue board into an ordered, reviewable plan so teams can spot duplicates, understand blockers, and decide what to do next.

Core Features & Use Cases

Snapshot and analyze the board: Captures open issues, cycles, stale items, and graph structure before any changes.
Find duplicates and clusters: Combines mechanical duplicate checks, graph signals, and specialist reasoning to group related work.
Rewire dependencies safely: Recommends relationship types like blocks, tracks, parent-child, or supersedes and asks for confirmation before applying them.
Example: Use it when a backlog has overlapping issues and no obvious next task, and you need a cleaned-up dependency map plus a next-session pickup.

Quick Start

Ask the skill to triage the board, identify duplicates and clusters, and propose safe dependency rewires for confirmation.

Frequently Asked Questions about issue-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I organize a flat issue backlog with duplicates and unclear priorities?▼

To organize a flat issue backlog, you can reorganize it into a structured dependency graph that applies duplicate detection, cluster synthesis, and safe dependency rewires to clarify priorities and identify blockers.

What is the best way to find duplicate issues in a project board?▼

The best way to find duplicate issues in a project board combines mechanical duplicate checks, graph signals, and specialist reasoning to group overlapping reports and related work into identifiable clusters.

How do I map out blockers and dependencies for open issues?▼

Mapping out blockers and dependencies for open issues is done by rewiring relationships safely, recommending types like blocks, tracks, parent-child, or supersedes, and asking for confirmation before applying them.

Can I reorganize a backlog with fewer than fifteen open issues?▼

Reorganizing a backlog with fewer than fifteen open issues is not the intended use case; this dependency graph restructuring applies to boards with duplicate reports, overlapping work, and more than fifteen open issues.

Does backlog triage generate an audit trail for applied changes?▼

Backlog triage does generate an audit trail by creating an apply.sh script that records per-change confirmations, ensuring all dependency rewires and board modifications are fully reviewable.

How do I capture the current state of a project board before restructuring?▼

To capture the current state of a project board before restructuring, take a snapshot that records open issues, cycles, stale items, and graph structure prior to making any dependency changes.