make-work-visible

Diagnose workflow problems using the Five Thieves of Time and kanban board design.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/vnovakovits/claude-skills --skill make-work-visible-vnovakovits
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: make-work-visible
Source: https://github.com/vnovakovits/claude-skills/tree/main/plugins/engineering-practices/skills/make-work-visible
Command: npx skills add https://github.com/vnovakovits/claude-skills --skill make-work-visible-vnovakovits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams and individuals are often busy but not shipping because work is invisible, WIP is uncontrolled, and time is silently stolen by unplanned work, dependencies, and conflicting priorities. This Skill surfaces hidden work and provides concrete countermeasures. ## Core Features & Use Cases - Five Thieves Diagnosis: Maps flow problems to too much WIP, unknown dependencies, unplanned work, conflicting priorities, or neglected work before suggesting interventions. - Board and Card Design: Provides Personal Kanban and team board layouts, per-column WIP limit heuristics, card design standards, and classes of service. - Demand Analysis and Rituals: Categorizes work into business projects, maintenance, ad hoc, and intangible demand, and defines standup, replenishment, and operations review rituals. - Use Case: A team lead notices every sprint plan disintegrates by Wednesday. Use this Skill to measure unplanned work as a percentage of total, set starting WIP limits, and redesign the daily standup to walk the board right-to-left. ## Quick Start Ask Claude to diagnose why your team is busy but not shipping and design a kanban board with WIP limits for your workflow.

Frequently Asked Questions about make-work-visible

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

FAQPage Schema
How do I set WIP limits for a kanban board?▼

Start with WIP of 2 or less per person and team size times 1.5 per team, so a team of four gets six cards in Doing. Post limits on column headers, enforce them strictly, and adjust empirically: lower until flow improves, raise only if the team starves.

What are the Five Thieves of Time in Making Work Visible?▼

The Five Thieves are too much WIP, unknown dependencies, unplanned work, conflicting priorities, and neglected work. Each has distinct symptoms and countermeasures, such as WIP limits for overload and age tracking with forced finish-kill-escalate decisions for neglected cards.

How do I run a kanban daily standup that is not a status report?▼

Walk the board right to left, starting closest to Done, and ask three questions per card: what is blocking it, what is needed to move it, and has it aged. Skip the per-person yesterday-today round-robin since the board already shows status.

When should I use this skill instead of a full Kanban Method guide?▼

Use this skill when you need operational, diagnostic guidance by Friday: thief diagnosis, demand mix analysis, Personal Kanban, and ritual design. Choose the broader kanban skill for CFDs, Little's Law, and foundational method principles.

Why does keeping everyone 100 percent busy slow a team down?▼

Maximizing individual utilization creates queues and context-switching costs, with roughly 20 percent productivity lost per concurrent project. Flow improves when WIP is limited and people help where the bottleneck is rather than starting new work.