kanban-queue-management

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

Updated May 13, 2026
One-click install
npx skills add https://github.com/jcg-admin/kaupamex-api --skill kanban-queue-management-jcg-admin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kanban-queue-management
Source: https://github.com/jcg-admin/kaupamex-api/tree/main/.claude/skills/kanban-queue-management
Command: npx skills add https://github.com/jcg-admin/kaupamex-api --skill kanban-queue-management-jcg-admin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams with more demand than capacity often pull work in FIFO order or by whoever asks loudest, leaving high-value items stuck behind trivial requests. This Skill governs the Kanban input queue so the highest-value work enters the system first, minimizing lead time where it matters most. ## Core Features & Use Cases - Cost of Delay & WSJF Prioritization: Score items by user value, time criticality, and risk reduction, then order the queue by WSJF (CoD divided by job size) instead of arrival order. - Classes of Service: Assign expedite, fixed-date, standard, or intangible classes with explicit policies, including a limit of one expedite item and reserved capacity for intangible work like technical debt. - Cadenced Replenishment: Define a fixed replenishment meeting cadence that decides when, how much, and what enters the committed queue. - Use Case: A product team drowning in requests uses this Skill to triage the backlog, score each item's cost of delay, assign service classes, and produce a prioritized queue with a weekly replenishment policy in plan-execution/kanban-queue.md. ## 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 size, so valuable and short items go 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 and sort descending.

What are classes of service in Kanban?▼

Classes of service are policies that match how an item's cost of delay grows over time: expedite for immediate high cost, fixed date for deadline-driven work, standard for linear cost, and intangible for deferred-value work like technical debt.

How do I handle urgent requests without breaking Kanban flow?▼

Use an expedite class of service with a strict limit of one item at a time and its own lane. Without that cap, everything becomes urgent and the expedite lane stops meaning anything, permanently disrupting flow.

When should I not use cost of delay prioritization?▼

Avoid it without a clear commitment point, since there is no queue boundary to govern. It also does not replace upstream product decisions about what to build, and it cannot fix a slow system with a downstream bottleneck.

Why does technical debt never get scheduled in Kanban?▼

Technical debt has low immediate cost of delay, so it always loses to urgent work in WSJF ordering. The fix is reserving fixed capacity for the intangible class of service so it cannot be perpetually displaced.