backlog-triage

Triage GitHub project board Inbox issues into prioritized Backlog entries.

1|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/jpalczewski/kajet-turbo --skill backlog-triage-jpalczewski
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backlog-triage
Source: https://github.com/jpalczewski/kajet-turbo/tree/main/.claude/skills/backlog-triage
Command: npx skills add https://github.com/jpalczewski/kajet-turbo --skill backlog-triage-jpalczewski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project boards accumulate untriaged Inbox issues whose premises go stale as code evolves, making it hard to decide what deserves attention and at what priority. ## Core Features & Use Cases - Staleness Verification: Checks every Inbox issue's cited symbols and paths against origin/main to detect already-fixed issues, deleted premises, and work covered by open PRs. - Priority Proposal: Assigns P0–P3 priorities grouped by theme with one-line justifications drawn from each issue's Impact section, following a documented calibration scale. - Approval-Gated Application: Changes nothing on the board until the user approves the full table, then applies statuses, priorities, epic ticks, and closures via board.py and gh. - Use Case: After a large refactor spawns dozens of code-review follow-up issues, run triage to verify which are still valid, propose priorities per theme, and move the approved set from Inbox to Backlog. ## Quick Start Ask the assistant to triage the project board's Inbox and propose priorities for each issue before moving them to Backlog.

Frequently Asked Questions about backlog-triage

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

FAQPage Schema
How do I triage GitHub project board issues into a backlog?▼

List Inbox issues with board.py, read every issue body in full, verify each against origin/main, then propose P0–P3 priorities grouped by theme. Apply changes only after the user approves the complete table.

How to detect stale issues after a code refactor?▼

Grep each issue's cited symbols and paths on origin/main and classify them as valid, moved, already fixed, premise gone, or covered by an open PR. Mechanical stale reports alone miss these cases.

What priority scale does this triage workflow use?▼

It uses P0 through P3: production-observed rule violations are P0/P1, dev-loop pain and confirmed bug classes are P1, latent risks and feature gaps are P2, and cosmetic items are P3. Epics receive no priority.

Does the triage skill modify the board automatically?▼

No. Nothing changes until the user approves the proposed table. After approval, it applies statuses and priorities via board.py and handles closures through gh with explanatory comments.

When should I not use backlog triage?▼

Do not use it for filing new issues, which belongs to issue-filing, or for choosing what enters the Next column, which belongs to next-selection. Triage only covers Inbox-to-Backlog prioritization.