kanban-flow-stinger

Designs Kanban boards, WIP limits, and flow-metric diagnostics for software delivery teams.

84|37|Updated May 23, 2026
One-click install
npx skills add https://github.com/legioncodeinc/vibe-coding-tools --skill kanban-flow-stinger-legioncodeinc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kanban-flow-stinger
Source: https://github.com/legioncodeinc/vibe-coding-tools/tree/main/src/skills/kanban-flow-stinger
Command: npx skills add https://github.com/legioncodeinc/vibe-coding-tools --skill kanban-flow-stinger-legioncodeinc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams struggle with unpredictable delivery, bloated work-in-progress, and unclear flow metrics. This Skill provides Kanban Method expertise to set data-driven WIP limits, calculate cycle time and throughput, apply Little's Law, and configure boards in Linear, Jira, and GitHub Projects. ## Core Features & Use Cases - WIP Limit Design: Derives WIP limits from throughput data, team capacity, or empirical quickstart methods, with enforcement models per tool. - Flow Metrics & Little's Law: Computes cycle time, lead time, throughput, and flow efficiency, and applies L = λW diagnostics with steady-state checks. - Tool Implementation: Gives exact configuration steps and known limitations for Linear (no native WIP limits), Jira (swimlane WIP count bug), and GitHub Projects (visual-only limits). - Use Case: A team whose cycle time keeps growing asks for help. The Skill diagnoses the issue via cumulative-flow-diagram anti-patterns, derives a throughput-based WIP limit, and produces a board design spec with class-of-service swimlanes. ## Quick Start Ask the assistant to calculate our team's cycle time and recommend WIP limits for our Jira Kanban board based on the last four weeks of throughput.

Frequently Asked Questions about kanban-flow-stinger

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

FAQPage Schema
How do I set WIP limits on a Kanban board?▼

Derive WIP limits from data using one of three methods: throughput times target cycle time, team size times 1.5 for active columns, or current average WIP minus one as an empirical quickstart. Never set arbitrary limits without baseline data.

What is the difference between cycle time and lead time?▼

Cycle time measures from when work actively starts to completion, while lead time measures from when the request enters the system to completion. Lead time is always greater than or equal to cycle time because it includes queue wait.

Does Linear support native WIP limits?▼

No, Linear has no native WIP limit enforcement as of 2026. Teams must use soft enforcement via naming conventions, team agreements, or GraphQL API automation to check in-progress counts.

When should I choose Kanban vs Scrum for my team?▼

Choose Kanban for operational, interrupt-driven work with unpredictable arrival; choose Scrum for new teams doing feature development needing structure. About 45% of Scrum teams migrate to a Scrumban hybrid after two to three years.

Why does Jira show wrong WIP counts with swimlanes?▼

Jira has a known bug where column WIP limits count total items across all swimlanes rather than per swimlane. Use flat boards when WIP accuracy matters, or organize with labels instead of swimlanes.

When should Little's Law not be applied to a Kanban board?▼

Do not apply Little's Law when more than 20% of WIP is blocked, an expedite lane holds two or more items, WIP was recently reduced, or team size changed within four weeks. These conditions violate the steady-state assumption.