Lean Software Development
Apply Mary & Tom Poppendieck's seven principles of Lean Software Development from "Lean Software Development — An Agile Toolkit" (2003) and "Implementing Lean Software Development" (2006). Covers the seven principles (eliminate waste, amplify learning, decide as late as possible, deliver as fast as possible, empower the team, build integrity in, see the whole), the seven wastes of software (partially-done work, extra features, relearning, handoffs, task switching, delays, defects), value-stream mapping, set-based design, Real Options thinking, and the leadership mindset shift required for lean
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 lean-software-developmentgit 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/lean-software-development ~/.claude/skills/lean-software-developmentPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Lean Software Development (Poppendieck) Apply this skill when a team or organization needs the broader operational philosophy of lean — not just the tools (Kanban, value-stream maps, Kaizen events) but the *mindset* behind them. The Poppendiecks translated Taiichi Ohno's Toyota Production System into seven principles for software, with concrete tools and a leadership perspective. ## Core Philosophy **Lean is a way of thinking, not a set of practices.** The principles are the substance; the tools are downstream. Teams that adopt the tools without the mindset get cargo-cult lean. **Customer value is the measure.** Every activity is judged by whether it produces value for the customer. Activities that don't — even ones that feel productive — are waste. **Optimize the whole, not the parts.** Local optimization (a single department working faster) often degrades global performance. Lean thinking is systemic. **Defer commitment until the last responsible moment.** Decisions made too early lock in assumptions that turn out to be wrong. Decisions made too late miss windows. Find the last responsible moment. **Build quality in.** Quality is a property of the *process*, not an inspection step at the end. Test-driven development, refactoring, pairing, and short cycles are quality-building mechanisms. --- ## The Seven Principles The book's spine. Each principle has a chapter; each has associated tools. ### 1. Eliminate Waste
Details
- Skill name
lean-software-development- Repository
- vnovakovits/claude-skills
- Path
plugins/engineering-practices/skills/lean-software-development/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Lean Software Development skill do?
Apply Mary & Tom Poppendieck's seven principles of Lean Software Development from "Lean Software Development — An Agile Toolkit" (2003) and "Implementing Lean Software Development" (2006). Covers the seven principles (eliminate waste, amplify learning, decide as late as possible, deliver as fast as possible, empower the team, build integrity in, see the whole), the seven wastes of software (partially-done work, extra features, relearning, handoffs, task switching, delays, defects), value-stream mapping, set-based design, Real Options thinking, and the leadership mindset shift required for lean
How do I install the Lean Software Development 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 Lean Software Development 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.
Linear Manager
8Freddy-CHEN-ux/00_claude_skills
Create, update, search, and comment on Linear issues. Use for project management and issue tracking during development.
Language Ext Csharp
5vnovakovits/claude-skills
Apply the LanguageExt functional library for C# in its 4.x form (the Aff and Eff era, before version 5's K<F, A> redesign). Covers the core types (Option, Either, Validation, Fin, Aff, Eff, Seq), idioms for null elimination, errors as values, applicative vs monadic composition, async effect chaining with LINQ from-select, Prelude imports and railway-oriented style, common pitfalls (ValueUnsafe, mixing nulls with Option, running effects on the wrong thread), and how v3, v4 and v5 differ. Use when reading, writing or reviewing C# that uses LanguageExt, including any code with Option<>, Either<>,
Pattern Extraction
8Freddy-CHEN-ux/00_claude_skills
Three-tier system for documenting code patterns to optimize token usage
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.