Product Development Flow
Apply Don Reinertsen's "The Principles of Product Development Flow" (Celeritas, 2009), the quantitative case for flow in product work. Covers its 175 principles across eight areas (economics, queues, variability, batch size, WIP constraints, flow control under uncertainty, fast feedback, decentralised control) with verified codes; cost of delay and the SJF, HDCF and WSJF (CD3) sequencing rules; utilisation, Little's formula and why you control queue size rather than cycle time; the batch-size U-curve; congestion collapse; cadence; pooled versus dedicated capacity; and how to handle interrupt,
Install
/plugin marketplace add vnovakovits/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add vnovakovits/claude-skills --skill product-development-flowgit clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/product-development-flow ~/.claude/skills/product-development-flowPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Principles of Product Development Flow (Don Reinertsen) Use this skill when a product-development decision needs economic and queueing reasoning: what to do next, how big a batch should be, how much work to allow in progress, how busy people should be, how to handle interruptions, and who should decide. The book has nine chapters. Chapter 1 sets out the problem; chapters 2–9 hold **175 numbered principles** in eight areas. The full index, with codes, names and a paraphrased gist of each, is in [references/principle-index.md](references/principle-index.md). Codes in this skill follow that index. They come from a study transcription whose counts match the book, so check the book before quoting a code formally. ## Core ideas 1. **Decide in money.** Most process decisions are made on proxies such as utilisation, conformance or "busy". Reinertsen wants them made on economics, and says that if you quantify only one thing, it should be cost of delay (E1, E3). 2. **Queues are the main waste, and they are invisible.** Development inventory is information, so it doesn't show on a shop floor or a balance sheet (Q1, Q2). Queues lengthen cycle time and add risk, variability, overhead and quality problems, and they sap motivation. 3. **High utilisation creates queues.** As utilisation approaches 100%, queues grow sharply, and past a point output collapses (Q3, F1). Spare capacity is an economic choice, not idleness.
Details
- Skill name
product-development-flow- Repository
- vnovakovits/claude-skills
- Path
plugins/engineering-practices/skills/product-development-flow/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Product Development Flow skill do?
Apply Don Reinertsen's "The Principles of Product Development Flow" (Celeritas, 2009), the quantitative case for flow in product work. Covers its 175 principles across eight areas (economics, queues, variability, batch size, WIP constraints, flow control under uncertainty, fast feedback, decentralised control) with verified codes; cost of delay and the SJF, HDCF and WSJF (CD3) sequencing rules; utilisation, Little's formula and why you control queue size rather than cycle time; the batch-size U-curve; congestion collapse; cadence; pooled versus dedicated capacity; and how to handle interrupt,
How do I install the Product Development Flow skill?
Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Product Development Flow popular?
It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.
Related skills
Accidental Cio
5vnovakovits/claude-skills
Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to
Agent Retro
5vnovakovits/claude-skills
Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee
API Design
5vnovakovits/claude-skills
Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.
QA Debugging
8Freddy-CHEN-ux/00_claude_skills
Systematic debugging methodologies, troubleshooting workflows, logging strategies, error tracking, performance profiling, stack trace analysis, and debugging tools across languages and environments. Covers local debugging, distributed systems, production issues, and root cause analysis.
Pre Commit Hooks
8Freddy-CHEN-ux/00_claude_skills
MANDATORY setup for all projects. Automated code quality enforcement before commits. Prevents bad code from entering repository.
Refactoring
5vnovakovits/claude-skills
Apply Martin Fowler's refactoring discipline — changing the internal structure of code without changing its observable behavior — using the named refactorings catalog (Extract Function, Move Method, Replace Conditional with Polymorphism, etc.) and the code-smells catalog (Long Method, Feature Envy, Primitive Obsession, etc.). Use when cleaning code under a test safety net, responding to a code smell, preparing code for a new feature, or as the third step of every TDD cycle.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.