🎯

kanban

🎯Skill

from flpbalada/my-opencode-config

What it does

Visualize and optimize team workflow by creating Kanban boards that track tasks, limit work-in-progress, and improve delivery efficiency.

📦

Part of

flpbalada/my-opencode-config(40 items)

kanban

Installation

📋 No install commands found in docs. Showing default command. Check GitHub for actual instructions.

Quick InstallInstall with npx

npx skills add flpbalada/my-opencode-config --skill kanban

Need more details? View full documentation on GitHub →

1Installs

AddedFeb 4, 2026

View on GitHub Back to Skills

Skill Details

SKILL.md

Overview

# Kanban - Visualize Work, Limit WIP, Optimize Flow

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.

When to Use This Skill

Managing team workflow and task prioritization
Identifying and resolving bottlenecks
Improving delivery predictability
Balancing team capacity with demand
Implementing continuous improvement
Transitioning from chaotic to structured work

Core Concepts

The Kanban Board

```

+----------+----------+----------+----------+

| | (WIP:3) | (WIP:2) | |

+----------+----------+----------+----------+

+----------+----------+----------+----------+

```

Six Core Practices

| 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 |

Key Metrics

| 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 |

Little's Law

```

Lead Time = WIP / Throughput

To reduce lead time:

Reduce WIP (easier)
Increase throughput (harder)

```

Analysis Framework

Step 1: Map Current Workflow

Identify all stages work passes through:

```

Idea → Backlog → Analysis → Development → Testing → Deploy → Done

```

Step 2: Set WIP Limits

Start with: WIP limit = Team size - 1

| Stage | Team Members | Initial WIP Limit |

| ------ | ------------ | ----------------- |

| Dev | 4 | 3 |

| Review | 2 | 2 |

| Test | 2 | 2 |

Step 3: Identify Bottlenecks

Look for columns where work accumulates:

```

+------+------+------+------+

+------+------+------+------+

| [1] | [4] | [8] | [9] |

| [2] | [5] | [10] | |

| [3] | [6] | | |

| | [7] | | ← Bottleneck in Review

+------+------+------+------+

```

Step 4: Optimize Flow

Actions to address bottlenecks:

Add capacity to bottleneck stage
Reduce WIP in preceding stages
Improve efficiency at bottleneck
Change policies (batch size, etc.)

Output Template

```markdown

Kanban Board Setup

Team/Project: [Name] Date: [Date]

Workflow Stages

| --------- | --------- | -------------- | ------------- |

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

| ---------- | ------------------ | -------- | -------- |

```

Real-World Examples

Example 1: Software Development Team

Before: 15 items in progress, 3-week average delivery After: 6 WIP

limit, 5-day average delivery

Changes:

Visualized all work (including hidden tasks)
Set WIP limits (forced focus)
Daily standups at the board
Swarming on blocked items

Example 2: Content Marketing Team

```

+--------+--------+--------+--------+--------+

| (10) | WIP:3 | WIP:2 | WIP:2 | |

+--------+--------+--------+--------+--------+

```

Bottleneck discovered: Design stage Solution: Created template library, reduced

design dependency

Best Practices

Do

Start with current process, evolve gradually
Make WIP limits visible and enforced
Track metrics consistently
Review board in daily standups
Celebrate flow improvements

Avoid

Treating Kanban as just a task board
Setting WIP limits too high (defeats purpose)
Ignoring blocked items
Skipping retrospectives
Comparing team throughput to others

WIP Limit Guidelines

| 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 |

Integration with Other Methods

| Method | Combined Use |

| ------------------- | ------------------------------------------- |

| Hypothesis Tree | Investigate flow problems |

| Five Whys | Find root cause of bottlenecks |

| Cognitive Load | Justify WIP limits (context switching cost) |

Resources

[Kanban - David J. Anderson](https://www.amazon.com/Kanban-Successful-Evolutionary-Technology-Business/dp/0984521402)
[Making Work Visible - Dominica DeGrandis](https://www.amazon.com/Making-Work-Visible-Exposing-Optimize/dp/1942788150)

More from this repository10

🎯

five-whys🎯Skill

Systematically uncovers root causes of problems through iterative questioning, revealing underlying issues beyond surface-level symptoms.

🎯

social-proof-psychology🎯Skill

Optimizes user trust and conversion by strategically displaying social validation through testimonials, user stats, and expert endorsements.

🎯

cognitive-fluency-psychology🎯Skill

Enhances user comprehension and engagement by applying cognitive fluency principles to simplify information processing across content and interfaces.

🎯

hooked-model🎯Skill

Designs habit-forming products by mapping user triggers, actions, rewards, and investments to create engaging, addictive product experiences.

🎯

cognitive-biases🎯Skill

Applies cognitive bias insights to optimize product design, user experiences, and decision-making strategies by leveraging psychological principles.

🎯

typescript-satisfies-operator🎯Skill

Validates TypeScript object types while preserving precise literal types, preventing type widening and catching type-related errors early.

🎯

typescript-best-practices🎯Skill

Enforces TypeScript best practices and coding standards through comprehensive linting and configuration rules for consistent, high-quality code.

🎯

status-quo-bias🎯Skill

Helps design product changes and migrations by understanding users' psychological resistance to change and creating strategies to overcome status quo bias.

🎯

typescript-interface-vs-type🎯Skill

Guides developers on choosing between TypeScript interfaces and type aliases based on specific use cases and performance considerations.

🎯

theme-epic-story🎯Skill

I apologize, but I cannot generate a description without seeing the actual content or context of the "theme-epic-story" skill from the repository. Could you provide more details about what this spe...