feat: add DMAIC semantic anchor (EN + DE) (#696) - #699
Conversation
|
Warning Review limit reached
Next review available in: 20 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (13)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
3b79b2d to
5ee1e9f
Compare
DMAIC completes the Six Sigma cluster. spc, control-chart-shewhart and
nelson-rules all referenced it as the cycle they serve, but no anchor existed.
Utility is structural, not descriptive: naming it forces a baseline before any
improvement is proposed, separates validated root causes from solutioning, and
adds a Control phase most improvement approaches lack. Tier 3 — the proposer
confirmed activation on a weak local model (qwen3.6-27b named all five phases).
Attribution fetch-verified: Bill Smith introduced Six Sigma at Motorola in
1986; Jack Welch made it central to GE strategy in 1995; the methodologies
descend from Deming's PDSA.
Criticism section, all sourced: Juran ("there is nothing new there"), the
3M/McNerney case where it was withdrawn from research, the >60% project
failure rate (WSJ 2010), and Wheeler on the 1.5-sigma shift. Current Status
covers ISO 13053-1:2011 and Lean Six Sigma.
Also adds dmaic to :related: in both directions across the SPC cluster and
five-whys, and to the AgentSkill catalog.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
5ee1e9f to
a4af70b
Compare
2 participants
Closes #696.
Why this one is easy
@Advisior's proposal is the most complete one the catalog has received: full activation test, a real before/after viability test, and a weak-model datapoint added unprompted after submission (qwen3.6-27b named all five phases, plus variation reduction, root-cause identification, hypothesis testing and control mechanisms). Nothing to send back.
It also closes a hole.
spc,control-chart-shewhartandnelson-rulesall name DMAIC as the cycle whose Measure and Control phases they serve — while DMAIC itself was not an anchor.Gate
Tier ★★★, given the weak-model result.
Attribution — fetch-verified
Wikipedia's DMAIC article does not attribute the method, so I checked the Six Sigma article:
Mikel J. Harry appears in the same article as "the creator of Six Sigma" in the 1.5σ context, so all three are listed as proponents.
Criticism section
DMAIC has substantial documented criticism, so it gets a full
== Criticism/== Current Statusper the #603 convention:Current Status notes that DMAIC is unusually standardised for a management method (ISO 13053-1:2011, whose scope explicitly includes service and transactional processes), and that Lean Six Sigma is the dominant contemporary form.
One caveat on sourcing:
iso.orgreturns 403 to automated fetchers, so I verified the standard's number, exact title, year and DMAIC scope through search results rather than by fetching the page directly. Every other cited source was fetched and content-checked.Cross-links
:related: dmaicadded in both directions acrossspc,control-chart-shewhart,nelson-rulesandfive-whys(which DMAIC's Analyze phase uses), EN and DE.Verification
npm run build→ 190 anchor pages (+190 German), no skips/anchor/dmaicand/de/anchor/dmaicchecked in the browser — both correct, 0 console errorsnpm test121/121,npm run lintcleanpublic/data/*.jsondeliberately not committedNote: CI's
Dependency Security Auditfails on every PR right now for unrelated reasons — see #698.🤖 Generated with Claude Code