kanban-queue-management

Prioritize the Kanban input queue using cost of delay, WSJF, and classes of service.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/NestorMonroy/thyrox --skill kanban-queue-management-nestormonroy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kanban-queue-management
Source: https://github.com/NestorMonroy/thyrox/tree/main/.claude/skills/kanban-queue-management
Command: npx skills add https://github.com/NestorMonroy/thyrox --skill kanban-queue-management-nestormonroy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When demand exceeds capacity, teams often pull work in FIFO order or by whoever shouts loudest, leaving high-value items stuck behind trivial ones. This Skill governs the Kanban input queue so that what enters the system, and in what order, is decided by economic criteria rather than arrival order. ## Core Features & Use Cases - Cost of Delay & WSJF Prioritization: Estimate cost of delay from user value, time criticality, and risk reduction, then order the queue by WSJF (CoD / job size) to minimize total delay cost. - Classes of Service: Assign expedite, fixed date, standard, or intangible policies per item, with a hard limit of one expedite item and reserved capacity for intangible work like technical debt. - Cadenced Replenishment: Define a fixed replenishment meeting cadence that commits a prioritized batch up to the queue limit instead of reactive drip-feeding. - Use Case: A product team faces 40 backlog requests and capacity for 8. Use this Skill to triage the requests, score cost of delay, order by WSJF, assign classes of service, and produce a kanban-queue.md artifact with the replenishment policy. ## Quick Start Ask the AI to prioritize your Kanban input queue by estimating cost of delay and WSJF for each backlog item, assigning classes of service, and defining a weekly replenishment policy.

Frequently Asked Questions about kanban-queue-management

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

FAQPage Schema
How do I prioritize a Kanban backlog with WSJF?▼

WSJF divides cost of delay by job duration, so you pull the highest-value, shortest items first. Estimate cost of delay by scoring user value, time criticality, and risk reduction on a relative scale, then divide by the item's estimated size.

What are classes of service in Kanban?▼

Classes of service are selection policies based on how an item's cost of delay grows over time: expedite, fixed date, standard, and intangible. Each class gets its own queue policy, such as a limit of one expedite item and reserved capacity for intangible work.

When should I not use cost of delay prioritization?▼

Avoid it when there is no clear commitment point on the board, since there is no queue boundary to manage. It also does not replace upstream product value analysis, and it should not be used to re-sequence work continuously instead of on a replenishment cadence.

Why does an expedite lane need a WIP limit?▼

Without a limit, everything gets marked urgent and the expedite lane stops meaning anything, permanently breaking flow. This Skill caps the expedite lane at one item at a time so genuine emergencies can be absorbed without chaos.

What are the limitations of WSJF prioritization?▼

WSJF depends on rough estimates of cost of delay and size, so the resulting order is only approximate. It can also starve low-CoD items permanently, which class-of-service capacity reservations mitigate but do not eliminate.