What problem does it solve? Teams that start too many tasks at once finish few of them: lead time grows, throughput stays flat, and bottlenecks stay hidden. This Skill turns a Kanban board into a pull system by setting visible Work In Progress limits per column and per person, so work is pulled only when capacity exists. ## Core Features & Use Cases - WIP limit calculation: Sizes limits with Little's Law (WIP = throughput × lead time) or with startup heuristics per column when no flow data exists yet. - Pull system instrumentation: Defines explicit pull signals and a swarming protocol so the team unblocks downstream work instead of starting new work when a limit is reached. - Metric-driven calibration: Reviews and adjusts limits using throughput, lead time, and Cumulative Flow Diagrams. - Use Case: A team whose 'In Development' column holds 12 cards for 4 developers applies this Skill to set a limit of 5, define the pull rule, and watch the QA bottleneck become visible within a week. ## Quick Start Ask the assistant to calculate and apply WIP limits for each column of your Kanban board using Little's Law and your team's throughput data.
