Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement. Use this to reduce a defect or error rate, design quality controls into a process, run a root cause analysis, respond to a customer quality complaint, or set up quality metrics that drive behavior.
npx skills add https://github.com/cbrock84/headcount --skill quality-management
Inspection at the end sorts good from bad. It never makes anything good. Quality is decided by the
process that produced the work, so that is where the effort belongs.
A standard nobody outside the team recognises is a preference. State quality in terms a customer
would agree with: correct, on time, complete, usable — with a threshold, so conformance is a fact
rather than an opinion.
Then distinguish:
A process can hit specification perfectly while producing something nobody wants. Only the second
question protects against that.
Cost of correction rises steeply with distance from the point of creation. Order of preference:
Every control pushed one step earlier is worth more than an additional control at the end.
"Human error" is where analysis stops, not where it should. Ask what made the error easy to make and
hard to notice: an ambiguous form, an unenforced sequence, a target that rewarded speed.
Work backwards through the causal chain until you reach something you can change structurally. A
corrective action that depends on people being more careful is not a corrective action — the same
conditions will produce the same result with different people.
Verify the fix by watching the defect rate, not by confirming the action was completed.
Any quality metric attached to individual performance will be gamed, usually by reclassifying
defects rather than preventing them. Measure at the process level, review trends rather than points,
and pair any rate metric with a volume metric so improvement by doing less is visible.
Escaped defects — those the customer found — are the honest measure. Everything else is a proxy.
Take cbrock84/quality-management from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.