Back to Skills

value-stream-mapping

verified

Lean value stream mapping for identifying waste and optimization opportunities. Creates current/future state maps with cycle time analysis and improvement recommendations.

View on GitHub

Marketplace

melodic-software

melodic-software/claude-code-plugins

Plugin

business-analysis

Repository
Verified Org

melodic-software/claude-code-plugins
13stars

plugins/business-analysis/skills/value-stream-mapping/SKILL.md

Last Verified

January 21, 2026

Install Skill

Select agents to install to:

Scope:
npx add-skill https://github.com/melodic-software/claude-code-plugins/blob/main/plugins/business-analysis/skills/value-stream-mapping/SKILL.md -a claude-code --skill value-stream-mapping

Installation paths:

Claude
.claude/skills/value-stream-mapping/
Powered by add-skill CLI

Instructions

# Value Stream Mapping

Create Lean value stream maps to visualize flow, identify waste, and design improvement opportunities. Based on Lean manufacturing principles adapted for knowledge work.

## What is a Value Stream?

A **value stream** is the sequence of activities required to deliver value to a customer, from request to delivery. Value stream mapping (VSM) visualizes this flow to identify:

- **Value-adding activities** - Steps that directly create customer value
- **Waste (Muda)** - Steps that consume resources without adding value
- **Flow problems** - Bottlenecks, delays, and inefficiencies

## The 8 Wastes (TIMWOODS)

| Waste | Description | Examples in Knowledge Work |
|-------|-------------|---------------------------|
| **T**ransportation | Moving work between locations | Handoffs between teams, tool switching |
| **I**nventory | Unfinished work waiting | Backlog, WIP, queued requests |
| **M**otion | Unnecessary movement | Context switching, searching for info |
| **W**aiting | Idle time | Approvals, blocked work, dependencies |
| **O**verproduction | Making more than needed | Unused features, premature optimization |
| **O**verprocessing | Doing more than required | Gold plating, excessive documentation |
| **D**efects | Errors requiring rework | Bugs, miscommunication, rework |
| **S**kills | Underutilized talent | Manual work that could be automated |

## Workflow

### Phase 1: Define Scope

#### Step 1: Identify the Value Stream

| Question | Answer |
|----------|--------|
| What value are we delivering? | [Customer outcome] |
| Who is the customer? | [Internal/External customer] |
| Where does the stream start? | [Trigger/Request] |
| Where does it end? | [Value delivered] |

#### Step 2: Set Boundaries

```markdown
## Value Stream Definition

**Name:** Customer Order Fulfillment
**Trigger:** Customer places order
**End State:** Customer receives product
**Scope:** Order entry → Shipping (excludes manufacturing)
**Customer:** External retail cust

Validation Details

Front Matter
Required Fields
Valid Name Format
Valid Description
Has Sections
Allowed Tools
Instruction Length:
10792 chars