triage-backlog

Verifies backlog items against the current codebase and rules each keep, delivered, duplicate, or retired.

Updated May 25, 2026
One-click install
npx skills add https://github.com/DATA-AI-XYZ/Tandem --skill triage-backlog-data-ai-xyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-backlog
Source: https://github.com/DATA-AI-XYZ/Tandem/tree/main/skills/triage-backlog
Command: npx skills add https://github.com/DATA-AI-XYZ/Tandem --skill triage-backlog-data-ai-xyz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Backlogs accumulate stale items: work silently completed by later epics, duplicates of other items, and entries whose premise no longer exists. This Skill audits each BACKLOG item's claim against the actual repository state so only genuinely valid work survives to refinement. ## Core Features & Use Cases - Evidence-based verdicts: Checks each item's testable claim against the tree at HEAD, git history, and ADRs, then rules STILL-VALID, ALREADY-DELIVERED, PARTIAL, DUPLICATE, OBSOLETE, DECISION-ONLY, TRIGGER-GATED, or PRODUCT-BET with one line of evidence per verdict. - Gated status flips: Terminal status changes (done, duplicate, wontfix, archived) require evidence plus operator confirmation, while annotations and partial-delivery notes are written directly into item files. - Audit report generation: Writes a dated triage report with verdict summary, merge groups, decisions owed, and a refinement shortlist with DoR gaps. - Use Case: Run a full-corpus triage of all not-started backlog items before a planning cycle to retire stale entries, merge duplicates, and produce a shortlist ready for refinement. ## Quick Start Triage every not-started item in the backlog and tell me which ones are still valid, already delivered, or should be retired.

Frequently Asked Questions about triage-backlog

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

FAQPage Schema
How do I check whether backlog items are still valid?

Run a backlog triage that extracts each item's testable claim and verifies it against the current tree at HEAD, git history, and ADRs. Each item receives an evidence-backed verdict such as STILL-VALID, ALREADY-DELIVERED, DUPLICATE, or OBSOLETE.

What is the difference between backlog triage and backlog refinement?

Triage judges whether an item is still valid or required by checking it against the codebase and history. Refinement judges whether a surviving item is ready to work by running a Definition of Ready checklist. Triage always runs first and never promotes items to ready.

Can triage mark a backlog item as done automatically?

Terminal status flips to done, duplicate, wontfix, or archived are evidence-gated and require operator confirmation from the verdict table. Annotations like partial-delivery notes may be written directly, but terminal flips never happen silently.

How are duplicate backlog items detected and handled?

Each item is compared against sibling backlog items for overlapping claims. Duplicates are proposed with the superseding artefact named in the item body, and groups of items sharing a root cause are recorded as one merge group rather than separate stories.

When should a backlog item be retired instead of kept?

Items whose premise no longer exists, or not-started items older than 90 days with no movement and no live trigger, are proposed for retirement under the sunset rule. Retirement is recorded as wontfix or archived with supporting evidence.