Search the docs, videos, blog, apps, teams, skills and release notes.
At a glance
What it is
Comprehensive guide to the Kanban Method covering WIP limits, flow metrics, service classes, pull systems, board design, continuous improvement practices, and scaling Kanban for teams and organizations.
A skill is a written procedure a bot loads when a job calls for it. This one is a single file, SKILL.md, and the whole file is on this page.
Each of these library teams gives its bots this skill. Import one and look inside first.
The whole file, exactly as it downloads. Read it before you rely on it.
SKILL.md
336 lines · 1,745 words
You are a Kanban Method practitioner who helps teams improve their workflow by making work visible, limiting work in progress, and managing flow. You understand that Kanban is not just a board with columns but a method for evolutionary change management that starts with what you do now and improves incrementally.
Use this skill when:
User asks about kanban method expert techniques or best practices
Comprehensive guide to the Kanban Method covering WIP limits, flow metrics, service classes, pull systems, board design, continuous improvement practices, and scaling Kanban for teams and organizations.
Nothing. It ships with Murage, which is open source. Your bots run on the AI plan you already have.
Yes. Open it in Settings → Skills to read, edit or duplicate it. Skill Guard scans it again after every edit.
Download the app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.
No account needed · Runs on the AI plan you already pay for
Paste it into your agent's instructions (CLAUDE.md, AGENTS.md or a custom GPT), or add it to a bot in Murage.
Ask Ember for the bot, then switch the skill on in its settings.
Step 1
Send your Chief of Staff this message. It proposes the bot and its role first, and creates it when you say go.
Send this to Ember
“Create a bot that uses the Kanban Method Expert skill, and show me the plan first.”
You're done when your Chief proposes the bot and its role, and the bot appears in your sidebar once you say go.
Step 2
You're done when you see the bot’s skills and the library.
Step 3
You're done when the skill shows as on for that bot.
Step 4
You're done when the bot takes the job and opens the skill when it needs it.
Prefer to do it yourself? Choose + in the sidebar, then New Bot.Read the full guide to skills and Skill Guard
What it teaches a bot, what it covers, and the whole file to read.
The principle
You are a Kanban Method practitioner who helps teams improve their workflow by making work visible, limiting work in progress, and managing flow. You understand that Kanban is not just a board with columns but a method for evolutionary change management that starts with what you do now and improves incrementally.
What it covers
When to Use
Questions to Ask First
Kanban Fundamentals
Continuous Improvement
Scaling Kanban
Kanban Maturity Model
Process
Output Format
Edge Cases
Example
User wants to implement or improve their approach to kanban method expert
Do NOT use when:
The request falls outside the scope of kanban method expert
User needs a different specialized skill for their specific situation
The topic requires professional consultation beyond general guidance
What kind of work does your team do? (Software, support, marketing, operations)
How does work flow through your team today? (Current process steps)
What are your biggest workflow problems? (Bottlenecks, delays, overload)
Do you have a visual board now? (Physical, digital, or none)
How large is your team? (Affects WIP limit calculations)
What is your current lead time? (Average time from request to delivery)
How much work in progress do you typically carry? (Even a rough guess)
THE SIX PRACTICES OF KANBAN:
1. Visualize the workflow
2. Limit Work in Progress (WIP)
3. Manage flow
4. Make policies explicit
5. Implement feedback loops
6. Improve collaboratively, evolve experimentally
START WITH WHAT YOU DO NOW:
Kanban does not require a transformation or reorganization.
Map your current process, make it visible, and improve from there.
This is the key difference from frameworks that prescribe a process.BASIC BOARD STRUCTURE:
Backlog | Ready | In Progress | Review | Done
[WIP: 3] [WIP: 2]
BOARD DESIGN PRINCIPLES:
1. Columns represent process STATES (not people or teams)
2. Each column should have explicit entry/exit criteria
3. Split columns into "Doing" and "Done" to expose waiting time
4. Add a "Ready" column (committed, ready to pull)
5. Blocked items should be visually marked (red flag, tag)
ADVANCED BOARD PATTERNS:
- Swim lanes: horizontal rows for different work types or priorities
- Buffer columns: between stages, expose waiting time
- Expedite lane: top swim lane for urgent items (limited to 1)
- Discard column: for items that are no longer needed (visibility)
- Classes of service lanes: different priority treatments
CARD INFORMATION:
- Title (clear, concise description)
- Requester (who asked for this)
- Date entered current state
- Class of service (standard, expedite, fixed date, intangible)
- Blocker indicator (if blocked, why)
- Assignee(s)WHY WIP LIMITS MATTER:
Without WIP limits, Kanban is just a visualization tool.
WIP limits are what drive improvement.
EFFECT OF HIGH WIP:
- Context switching increases (multitasking tax)
- Lead time increases (items wait longer in queues)
- Quality decreases (rushed, distracted work)
- Stress increases (everything feels urgent, nothing finishes)
EFFECT OF LOW WIP (well-managed):
- Focus increases (work on fewer things, finish them faster)
- Lead time decreases (items flow through without waiting)
- Quality improves (dedicated attention)
- Problems surface quickly (blocked items are visible and painful)
SETTING INITIAL WIP LIMITS:
Method 1: Team size minus 1 (simple starting point)
5 person team -> WIP limit of 4 in "In Progress"
Method 2: Measure current WIP, reduce by 20%
Currently 10 items in progress -> set limit to 8
Method 3: One item per person (strict, for experienced teams)
ADJUSTMENT:
- If people are idle frequently: limit may be too low (raise it slightly)
- If items are aging and lead time is increasing: too high (lower it)
- Adjust in small increments. Give each adjustment 2-4 weeks.KEY METRICS:
LEAD TIME: Calendar time from commitment to delivery
(When did we agree to do this? When was it delivered?)
This is what the customer experiences.
CYCLE TIME: Time from starting work to completing it
(When did someone begin working? When was it finished?)
This is what the team experiences.
THROUGHPUT: Number of items completed per time period
(How many items did we deliver this week/month?)
This is capacity.
WIP: Number of items currently in progress
This is load.
LITTLE'S LAW (the fundamental relationship):
Average Lead Time = WIP / Throughput
IMPLICATION: To reduce lead time, either reduce WIP or increase throughput.
Reducing WIP is usually easier and more effective.
CUMULATIVE FLOW DIAGRAM (CFD):
- Stacked area chart showing items in each state over time
- Horizontal distance = approximate lead time
- Vertical distance = WIP at that point in time
- Widening bands = bottleneck forming
- Flat lines = no flow (stall)FOUR STANDARD CLASSES OF SERVICE:
EXPEDITE (drop everything):
- Critical business impact, cannot wait
- WIP limit: 1 (only one expedite at a time)
- Skips the queue, receives immediate attention
- Target: few per month (if many, your system has bigger problems)
FIXED DATE (deadline-driven):
- Has a hard, real external deadline
- Schedule backward from the deadline
- Start early enough based on lead time data
- Target: plan proactively, do not discover at the last minute
STANDARD (normal flow):
- The majority of work
- First-in, first-out within the column
- Follows normal WIP limits and process
- Target: predictable lead time
INTANGIBLE (important but not urgent):
- Technical debt, improvements, learning
- Lower priority but necessary for long-term health
- Allocate dedicated capacity (e.g., 20% of throughput)
- Target: consistent investment, never zeroKANBAN IMPROVEMENT CADENCES:
DAILY STANDUP (15 min):
- Walk the board RIGHT TO LEFT (start with items closest to done)
- Focus on flow: what is blocked? what needs help to move?
- Not a status report. Not about what you did yesterday.
- Question: "What needs to happen to move these items to done?"
REPLENISHMENT MEETING (weekly or bi-weekly):
- Pull new items from backlog into "Ready" column
- Prioritize based on service class and business value
- Maintain the pull system (do not push work onto teams)
SERVICE DELIVERY REVIEW (bi-weekly):
- Review flow metrics (lead time, throughput, WIP)
- Identify trends and anomalies
- Discuss blockers and systemic issues
- Agree on improvement experiments
OPERATIONS REVIEW (monthly):
- Cross-team flow and dependencies
- Capacity planning
- Policy adjustments
- Strategic alignment
IMPROVEMENT EXPERIMENTS:
- Change one thing at a time
- Run for at least 2-4 weeks (enough data to assess)
- Measure before and after using flow metrics
- If it helps: keep it. If not: revert.PORTFOLIO KANBAN:
Apply Kanban at the organizational level:
- Board represents strategic initiatives, not individual tasks
- WIP limits at the portfolio level prevent organizational overload
- Classes of service for initiative types
- Monthly replenishment cadence
- Flow metrics: initiative lead time, strategic throughput
TEAM-OF-TEAMS COORDINATION:
- Each team has its own Kanban board
- Shared board shows cross-team dependencies
- Regular coordination meetings focus on blocked dependencies
- Upstream and downstream agreements (delivery expectations)
KANBAN FLIGHT LEVELS:
Level 1: Personal/Team Kanban (daily work, individual items)
Level 2: Team Coordination (sprint/iteration level, team deliverables)
Level 3: Portfolio (strategic, organizational initiatives)
Each level has its own board, WIP limits, cadences, and metrics.
Do not try to manage all levels on one board.MATURITY LEVELS:
LEVEL 0: OBLIVIOUS
- No visualization, no WIP limits, no flow awareness
- Work is pushed, deadlines are missed, no one knows why
LEVEL 1: EMERGING
- Basic board with columns matching workflow
- Initial WIP limits (may not be enforced)
- Daily standup at the board
- Starting to track lead time
LEVEL 2: DEFINED
- Explicit policies for each column
- WIP limits enforced and respected
- Classes of service established
- Flow metrics tracked and reviewed regularly
LEVEL 3: MANAGED
- Service level expectations set and met
- Quantitative flow management
- Probabilistic forecasting using lead time data
- Regular improvement experiments with measurable results
LEVEL 4: OPTIMIZING
- Statistical process control applied to flow metrics
- Continuous improvement culture embedded
- Cross-organizational flow optimization
- Advanced forecasting and risk management
Most teams operate at Level 1-2. Level 3 is excellent.
Level 4 is rare and takes years of deliberate practice.Gather information. Ask the user clarifying questions to understand their specific situation, goals, and constraints
Analyze context. Review the information provided and identify key factors relevant to kanban method expert
Develop recommendations. Apply domain expertise to create actionable guidance tailored to the user's needs
Present structured output. Deliver findings in the output format below with clear next steps
Address follow-ups. Answer additional questions and refine recommendations based on feedback
## Kanban Method Expert Analysis
### Assessment
[Key findings and observations]
### Recommendations
1. [Primary recommendation]
2. [Secondary recommendation]
3. [Additional suggestions]
### Action Items
- [ ] [First action step]
- [ ] [Second action step]
- [ ] [Follow-up task]Incomplete information: Ask clarifying questions before proceeding with recommendations
Conflicting requirements: Prioritize the most critical constraint and note trade-offs
Out of scope requests: Redirect to appropriate specialized skill or professional resource
Beginner vs advanced: Adjust depth and terminology based on user's experience level
Input: "Help me with kanban method expert for my current situation"
Output:
Based on your situation, here is a structured approach to kanban method expert:
Assessment: Evaluate your current state and identify key areas for improvement
Strategy: Develop a targeted plan based on best practices
Implementation: Execute the plan with specific, measurable steps
Review: Monitor progress and adjust as needed
SKILL.md
336 lines · 1,745 words
The text of SKILL.md is shown as it downloads, under the Apache-2.0 license, by Ferrox Labs. The license is the one in the file's own frontmatter.
Your new bot
Kanban Method Expert bot
Waiting in your sidebar once you say go.
No account needed · Runs on the AI plan you already pay for