Kanban
Apply Kanban as a method for managing knowledge work, based on Marcus Hammarberg & Joakim Sundén's "Kanban in Action" (Manning, 2014) with David J. Anderson's foundational Kanban Method ("Kanban", 2010) and Klaus Leopold's "Practical Kanban" (2017). Covers the four foundational principles, six core practices (visualize, limit WIP, manage flow, make policies explicit, implement feedback loops, improve collaboratively), Kanban-board design, WIP limits and how to set them, flow metrics (lead time, cycle time, throughput, CFD), Little's Law, classes of service, cadences (daily standup, replenishme
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 kanbangit 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/kanban ~/.claude/skills/kanbanPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Kanban (Hammarberg & Sundén) Apply this skill when designing or improving a team's workflow, when an existing process is producing erratic delivery or visible bottlenecks, when work-in-progress is undefined or unbounded, when choosing between Kanban / Scrum / Scrumban, or when running a Kanban-style improvement cadence. ## Core Philosophy **Kanban is a method for managing and improving service delivery, evolutionarily.** It is not a software development lifecycle. It is not a replacement for Scrum. It is a system of principles and practices applied on top of whatever process you already have. **Start with what you do now.** The first Kanban act is not to redesign the process; it is to **visualize the existing one** and start measuring it. Change comes from the team observing reality, not from imposing a new methodology. **Stop starting; start finishing.** The most common dysfunction in knowledge work is having too many things in flight. Kanban's mechanism — WIP limits — physically prevents this by making "start another item" impossible until existing items finish. **Flow over utilization.** Maximizing individual utilization (everyone busy 100% of the time) is the enemy of system throughput. Some slack is required for work to flow without queuing. **Pull, not push.** Work moves through the system because the next stage pulls it when it has capacity, not because the prior stage pushes it. This is the inversion that makes WIP limits work. ---
Details
- Skill name
kanban- Repository
- vnovakovits/claude-skills
- Path
plugins/engineering-practices/skills/kanban/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Kanban skill do?
Apply Kanban as a method for managing knowledge work, based on Marcus Hammarberg & Joakim Sundén's "Kanban in Action" (Manning, 2014) with David J. Anderson's foundational Kanban Method ("Kanban", 2010) and Klaus Leopold's "Practical Kanban" (2017). Covers the four foundational principles, six core practices (visualize, limit WIP, manage flow, make policies explicit, implement feedback loops, improve collaboratively), Kanban-board design, WIP limits and how to set them, flow metrics (lead time, cycle time, throughput, CFD), Little's Law, classes of service, cadences (daily standup, replenishme
How do I install the Kanban 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 Kanban 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.
Make Work Visible
5vnovakovits/claude-skills
Apply Dominica DeGrandis's "Making Work Visible — Exposing Time Theft to Optimize Work & Flow" (IT Revolution, 2017; 2nd ed. 2022). Covers the five thieves of time (too much WIP, unknown dependencies, unplanned work, conflicting priorities, neglected work), how to expose and counter each, the book's own exercises (demand analysis, work item types, card design, workflow mapping, the five reasons we take on more WIP, the "Oh, By the Way" dependency matrix, the interruption reduction experiment, visualise priorities, the aging report), board design, line of commitment, flow metrics, the Time Thie
Data Analytics Engineering
8Freddy-CHEN-ux/00_claude_skills
Analytics engineering for reliable metrics and BI readiness. Build transformation layers, dimensional models, semantic metrics, data quality tests, and documentation. Use when you need dbt or SQL transformation strategy, metrics definition, or analytics data modeling.
Product Analytics
8Freddy-CHEN-ux/00_claude_skills
Framework for analyzing product usage data and identifying patterns. Use when performing deep analysis of user behavior and engagement metrics.
Browse the most popular Claude skills, all data & analytics skills, or write your own with the skills generator.