Visualize and optimize workflow with Kanban boards. Use when managing team work, identifying bottlenecks, improving delivery flow, or implementing continuous improvement in product development.
Visualize workflow and limit work-in-progress to identify bottlenecks and optimize delivery flow. Use when managing team tasks, balancing capacity, or transitioning from chaotic to structured work.
/plugin marketplace add flpbalada/thinking-toolkit/plugin install kanban@thinking-toolkitThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Kanban is a visual workflow management method originating from Toyota's manufacturing system. It focuses on visualizing work, limiting work-in-progress (WIP), and optimizing the flow of work through a system.
+----------+----------+----------+----------+
| TO DO | DOING | REVIEW | DONE |
| | (WIP:3) | (WIP:2) | |
+----------+----------+----------+----------+
| [Task 1] | [Task 4] | [Task 6] | [Task 8] |
| [Task 2] | [Task 5] | | [Task 9] |
| [Task 3] | | | |
+----------+----------+----------+----------+
| Practice | Description |
|---|---|
| Visualize workflow | Make all work visible on the board |
| Limit WIP | Cap items in each stage |
| Manage flow | Track and optimize throughput |
| Make policies explicit | Document rules for moving work |
| Implement feedback loops | Regular reviews and retrospectives |
| Improve collaboratively | Evolve process based on data |
| Metric | Definition | Why It Matters |
|---|---|---|
| Lead Time | Request → Delivery | Customer perspective |
| Cycle Time | Work Started → Done | Team efficiency |
| Throughput | Items completed per period | Capacity planning |
| WIP | Items currently in progress | Flow health |
Lead Time = WIP / Throughput
To reduce lead time:
- Reduce WIP (easier)
- Increase throughput (harder)
Identify all stages work passes through:
Idea → Backlog → Analysis → Development → Testing → Deploy → Done
Start with: WIP limit = Team size - 1
| Stage | Team Members | Initial WIP Limit |
|---|---|---|
| Dev | 4 | 3 |
| Review | 2 | 2 |
| Test | 2 | 2 |
Look for columns where work accumulates:
+------+------+------+------+
| Dev |Review| TEST | Done |
+------+------+------+------+
| [1] | [4] | [8] | [9] |
| [2] | [5] | [10] | |
| [3] | [6] | | |
| | [7] | | ← Bottleneck in Review
+------+------+------+------+
Actions to address bottlenecks:
## Kanban Board Setup
**Team/Project:** [Name] **Date:** [Date]
### Workflow Stages
| Stage | WIP Limit | Entry Criteria | Exit Criteria |
| --------- | --------- | -------------- | ------------- |
| [Stage 1] | [n] | [Criteria] | [Criteria] |
| [Stage 2] | [n] | [Criteria] | [Criteria] |
### Current Metrics
| Metric | Current | Target |
| ---------- | -------- | -------- |
| Lead Time | [X days] | [Y days] |
| Cycle Time | [X days] | [Y days] |
| Throughput | [X/week] | [Y/week] |
### Bottleneck Analysis
**Current bottleneck:** [Stage] **Root cause:** [Analysis] **Action plan:**
[Steps to resolve]
### Improvement Experiments
| Experiment | Hypothesis | Measure | Duration |
| ---------- | ------------------ | -------- | -------- |
| [Change 1] | [Expected outcome] | [Metric] | [Time] |
Before: 15 items in progress, 3-week average delivery After: 6 WIP limit, 5-day average delivery
Changes:
+--------+--------+--------+--------+--------+
| Ideas | Draft | Edit | Design | Publish|
| (10) | WIP:3 | WIP:2 | WIP:2 | |
+--------+--------+--------+--------+--------+
Bottleneck discovered: Design stage Solution: Created template library, reduced design dependency
| Situation | Adjustment |
|---|---|
| Items stuck too long | Lower WIP |
| Team has idle time | Raise WIP slightly |
| Too much context switching | Lower WIP |
| Bottleneck forming | Address root cause |
| Method | Combined Use |
|---|---|
| Hypothesis Tree | Investigate flow problems |
| Five Whys | Find root cause of bottlenecks |
| Cognitive Load | Justify WIP limits (context switching cost) |
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.