Value Stream Mapping
Map how a request flows from ask to value — Mike Rother & John Shook's "Learning to See" (1999) and Karen Martin & Mike Osterling's "Value Stream Mapping" (2013), adapted to software and knowledge work. Covers scoping one value stream, the map grammar (process boxes with lead time, process time and %C&A, queue triangles, push and pull arrows, information flow, the timeline ladder, kaizen bursts), collecting real numbers from tracker state history instead of opinions, the summary metrics (total lead time, process time, flow efficiency or activity ratio, rolled %C&A), the future-state questions,
Install
/plugin marketplace add vnovakovits/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add vnovakovits/claude-skills --skill value-stream-mappinggit clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/value-stream-mapping ~/.claude/skills/value-stream-mappingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Value Stream Mapping A value stream is every step, value-adding or not, that one request goes through from the moment someone asks to the moment they get value. Mapping it makes the waiting visible. In knowledge work most of a request's life is waiting, and nobody sees it, because every person is busy with their own step. Rother and Shook wrote the method for manufacturing (*Learning to See*, 1999). Martin and Osterling generalised it to office, service and knowledge work (*Value Stream Mapping*, 2013) and added the metric that matters most there: percent complete and accurate. Use their version for software. Companion skills: `flow-efficiency` (why waiting dominates, Little's law, Kingman), `kanban` (managing the flow the map reveals), `toyota-way`, `make-work-visible`. ## When a map is worth drawing - A request takes weeks or months, and nobody can say where the time goes. - A process or ways-of-working document is being reviewed or redesigned: map today, then map the proposal. - Teams are fully busy, yet delivery is slow (the efficiency paradox). - Handoffs between roles or departments are frequent and painful. Skip it for a process with one step and one person, or when the question is about a single team's internal practice (use a Kanban board instead). ## 1. Scope one stream - **One kind of request**, named concretely: "a feature initiative from intake form to outcome review", not "how we work".
Details
- Skill name
value-stream-mapping- Repository
- vnovakovits/claude-skills
- Path
plugins/engineering-practices/skills/value-stream-mapping/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Value Stream Mapping skill do?
Map how a request flows from ask to value — Mike Rother & John Shook's "Learning to See" (1999) and Karen Martin & Mike Osterling's "Value Stream Mapping" (2013), adapted to software and knowledge work. Covers scoping one value stream, the map grammar (process boxes with lead time, process time and %C&A, queue triangles, push and pull arrows, information flow, the timeline ladder, kaizen bursts), collecting real numbers from tracker state history instead of opinions, the summary metrics (total lead time, process time, flow efficiency or activity ratio, rolled %C&A), the future-state questions,
How do I install the Value Stream Mapping skill?
Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Value Stream Mapping popular?
It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.
Related skills
Accidental Cio
5vnovakovits/claude-skills
Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to
Agent Retro
5vnovakovits/claude-skills
Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee
API Design
5vnovakovits/claude-skills
Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.
Writing Plans
8Freddy-CHEN-ux/00_claude_skills
Use after brainstorming, before implementation. Breaks work into discrete, actionable tasks with clear verification points.
Validate Docs Implementation
8Freddy-CHEN-ux/00_claude_skills
Load when user says "validate docs", "check documentation consistency", "docs vs implementation", or "find documentation mismatches". Systematically compares implementation code against documentation to identify and fix inconsistencies.
Writing Skills
8Freddy-CHEN-ux/00_claude_skills
Use when creating reusable process documentation. Apply TDD: baseline without skill → document failures → write skill → test → iterate. Four types: Discipline, Technique, Pattern, Reference. Iron Law: No skill without failing test first.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.