root-cause-pareto
Build a decision-grade Pareto for downtime, defects, complaints or delays - with unit-of-measure discipline, category hygiene, exposure normalization and a follow-up metric. Use when the user mentions pareto analysis, kök neden, duruş analizi, downtime, arıza analizi, defect ranking, şikayet analizi, 80/20 analysis. Differentiator - treats the Pareto as the start of a causal investigation, not a bar chart deliverable.
Original · translation is not supported for this source languageTarget: Target not categorized. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Root-Cause Pareto
- Workflow
- Pitfalls to check explicitly
- Output format
A Pareto chart is easy; a Pareto that survives challenge in a management meeting is not. The difference is four disciplines applied before the chart exists. 1. Pick the unit of measure deliberately. Occurrences, minutes, or money - choose the one closest to the pain being managed and say why. Ranking breakdowns by count when one category costs 10x more minutes per event points the team at the wrong problem. When in doubt, show count and impact side by side. 2. Enforce category hygiene before counting: Categories must sit at one granularity level (no "Mechanical failure" next to "Sensor S-114 misaligned") "Other/Miscellaneous" must stay under 15% of the total; if it is bigger, the categorization failed - split it before proceeding Merge synonyms and near-duplicates (free-text logs always contain them; list the merges made) 3. Normalize by exposure before comparing. Line A with 3 shifts will "lead" any raw ranking against Line B with 1 shift. Divide by machine-hours, orders, or units produced when comparing across lines, shifts, or periods - state the exposure base used. 4. Check stability. A Pareto from one bad week is an anecdote. Compare the ranking across at least two comparable
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- davila7/claude-code-templates
- Source file
- cli-tool/components/skills/operations/root-cause-pareto/SKILL.md
- Fixed revision
- 21be197f100a12b8d0dd9a211cc244c8179f84d3
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: davila7/claude-code-templates · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-09T15:01:39.561Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.