Stats
Actions
Tags
From b00t
Reduces defects by eliminating variance via the DMAIC cycle. Applies to software: define criteria, measure coverage, analyze failures, improve code, add CI gates.
How this skill is triggered — by the user, by Claude, or both
Slash command
/b00t:six-sigmaThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Six Sigma aims to reduce defects to 3.4 per million by eliminating variance through the DMAIC cycle. The five phases are: (1) Define — what is the problem? what is the target state? who is affected? (2) Measure — collect baseline data. No guessing, no anecdote. (3) Analyze — find root cause using fishbone, 5-whys, or Pareto analysis. Do not fix symptoms. (4) Improve — implement targeted solutio...
Six Sigma aims to reduce defects to 3.4 per million by eliminating variance through the DMAIC cycle. The five phases are: (1) Define — what is the problem? what is the target state? who is affected? (2) Measure — collect baseline data. No guessing, no anecdote. (3) Analyze — find root cause using fishbone, 5-whys, or Pareto analysis. Do not fix symptoms. (4) Improve — implement targeted solution. Pilot first, measure impact. (5) Control — lock in the gain. Add monitoring and set triggers to catch regression.
The key rule: never skip Measure — improving an unmeasured process is theater. In code, DMAIC maps to: define acceptance criteria → measure test coverage → analyze failure modes → improve code → add CI gates.
Apply DMAIC when improving a process, reducing error rates, or addressing quality issues. Use it whenever you need a data-driven approach to process improvement rather than intuition-based changes.
npx claudepluginhub elasticdotventures/_b00t_ --plugin skill-document-understandingSystematically implements process improvements using the PDCA cycle: define problems, identify root causes, run small-scale pilots, and standardize gains before scaling.
Guides incremental code improvement, refactoring, error prevention, and standardization. Use when improving code quality or discussing process improvements.
Guides incremental refactoring, continuous code improvements, error-proofing, and standardization using Kaizen principles. Use for code quality enhancements, refactoring, or process discussions.