What problem does it solve? Product development teams make decisions about batch sizes, WIP limits, backlog priorities, and control structures using gut feel or proxy metrics like utilization, leading to invisible queues, long cycle times, and wasted capacity. This Skill provides Don Reinertsen's quantitative economic framework so these decisions can be made with explicit cost-of-delay and queueing-theory reasoning. ## Core Features & Use Cases - Economic Prioritization: Compute Cost of Delay and CD3/WSJF to rank backlogs by economic value rather than intuition. - Queue and Batch Analysis: Identify hidden queues (review, QA, deployment, decision queues), apply Little's Law, and find optimal batch sizes using U-curve reasoning. - Control Structure Design: Decide which decisions to centralize or decentralize using mission command (auftragstaktik) criteria. - Use Case: A team debating whether to enforce smaller PRs can analyze the review queue, transaction costs of CI runs, and feedback latency to reach a justified decision instead of citing generic best practices. ## Quick Start Ask Claude to prioritize your backlog using cost of delay and WSJF, or to analyze whether your team's batch sizes and WIP limits are economically justified.
