
spc
Implement SPC charting, process capability analysis, and control chart interpretation. Covers control chart selection, capability indices, and out-of-control rules. USE WHEN user says 'SPC', 'Cpk', 'Ppk', 'control chart', 'process capability', 'X-bar R', 'statistical control', or 'out of control'. Integrates with ControlPlan, MSA, and AutomotiveManufacturing skills.
- Installs
- 50
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/robdtaylor/personal-ai-infrastructure --skill spc- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads spc automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Statistical Process Control (SPC)
When to Activate This Skill
- "Set up SPC for [characteristic]"
- "Calculate Cpk for [process]"
- "What control chart should I use?"
- "Is this process in control?"
- "Interpret out-of-control pattern"
- "Conduct capability study"
- "What's the difference between Cp and Cpk?"
Purpose of SPC
SPC uses statistical methods to monitor, control, and improve processes by distinguishing between:
- Common cause variation - Normal, inherent process variation
- Special cause variation - Abnormal, assignable causes requiring action
Why SPC Matters
Without SPC:
- React only when defects occur
- Cannot predict process behavior
- May over-adjust stable processes
- Miss early warning signs
With SPC:
- Detect problems before defects
- Understand process capability
- Make data-driven decisions
- Continuously improve
Workflow Routing
| Trigger | What to do |
|---|---|
| "what control chart should I use for [data]" | Use Control Chart Selection tables (Variable vs Attribute) to pick X-bar/R, X-bar/S, I-MR, p/np/c/u based on data type and subgroup size |
| "set up SPC / calculate control limits for [characteristic]" | Follow Capability Study Process Steps 1-3, then calculate limits via X-bar/R Chart or Individual/Moving Range (I-MR) Chart formulas |
| "is this process in control?" / "interpret this pattern" | Check plotted points against Out-of-Control Rules (Western Electric Rules 1-4 standard; Nelson Rules 5-8 for detailed analysis) |
| "calculate Cpk/Ppk" / "is this process capable?" | Apply Process Capability formulas, compare to Capability Targets (Cpk/Ppk ≥1.33 minimum, ≥1.67 for CC), interpret PPM via the Interpretation table |
| "what's the difference between Cp and Cpk" / "Cpk vs Ppk" | Explain via the Key Difference: Cp/Cpk vs Pp/Ppk table (within-subgroup vs overall variation) |
| "conduct a capability study" | Walk through Capability Study Process Steps 1-5 |
| "is pre-control appropriate here" | Use Pre-Control (Alternative to SPC) criteria and zone rules |
| "generate SPC report/analysis" | Emit using the Output Format template below |
Control Chart Selection
Variable Data Charts (Measurements)
| Chart | Data Type | When to Use |
|---|---|---|
| X-bar/R | Subgroups n=2-9 | Standard variable control chart |
| X-bar/S | Subgroups n≥10 | Large subgroups |
| I-MR | Individual measurements | Low volume, long cycle, destructive test |
Attribute Data Charts (Counts/Categories)
| Chart | Data Type | When to Use |
|---|---|---|
| p chart | Proportion defective | Variable sample size, defective/not |
| np chart | Count of defectives | Fixed sample size, defective/not |
| c chart | Defects per unit | Fixed area/unit, count defects |
| u chart | Defects per unit | Variable area/unit, count defects |
X-bar/R Chart
Setup
| Parameter | Guideline |
|---|---|
| Subgroup size (n) | 3-5 typical, 5 preferred |
| Subgroup frequency | Rational subgrouping - within-subgroup should be homogeneous |
| Minimum data points | 20-25 subgroups before calculating limits |
Control Limit Formulas
X-bar Chart:
UCL = X̄̄ + A₂ × R̄
CL = X̄̄
LCL = X̄̄ - A₂ × R̄
R Chart:
UCL = D₄ × R̄
CL = R̄
LCL = D₃ × R̄
Constants (A₂, D₃, D₄)
| n | A₂ | D₃ | D₄ |
|---|---|---|---|
| 2 | 1.880 | 0 | 3.267 |
| 3 | 1.023 | 0 | 2.575 |
| 4 | 0.729 | 0 | 2.282 |
| 5 | 0.577 | 0 | 2.115 |
| 6 | 0.483 | 0 | 2.004 |
Individual/Moving Range (I-MR) Chart
When to Use
- Long cycle time
- Destructive testing
- Expensive testing
- Batch processes
Control Limit Formulas
I Chart:
UCL = X̄ + 2.66 × MR̄
CL = X̄
LCL = X̄ - 2.66 × MR̄
MR Chart:
UCL = 3.267 × MR̄
CL = MR̄
LCL = 0
Out-of-Control Rules
Western Electric Rules (Standard)
| Rule | Pattern | Indicates |
|---|---|---|
| Rule 1 | 1 point beyond 3σ | Sudden shift |
| Rule 2 | 8 points in a row on same side of CL (some sources: 9) | Process shift/mean shift |
| Rule 3 | 6 points in a row trending (up or down) | Trend/drift |
| Rule 4 | 14 points in a row alternating up/down | Over-adjustment |
Nelson Rules (Extended)
| Rule | Pattern |
|---|---|
| Rule 5 | 2 of 3 points beyond 2σ (same side) |
| Rule 6 | 4 of 5 points beyond 1σ (same side) |
| Rule 7 | 15 points in a row within 1σ of CL |
| Rule 8 | 8 points beyond 1σ (both sides) |
MNMUK Standard
Use Rules 1-4 (Western Electric) as standard. Apply Nelson rules for critical characteristics or detailed analysis.
Important: Western Electric Rule 2 triggers at 7 or more consecutive points on one side of the centerline (some references cite 8 or 9 — the broadly accepted standard is that 7+ points on one side constitutes an out-of-control signal requiring investigation). A run of 7 consecutive points on one side of the centerline IS an out-of-control condition.
Process Capability
Indices Overview
| Index | Measures | Formula |
|---|---|---|
| Cp | Potential capability (spread) | (USL - LSL) / 6σ |
| Cpk | Actual capability (considers centering) | Min(Cpu, Cpl) |
| Pp | Process performance (spread) | (USL - LSL) / 6s |
| Ppk | Process performance (considers centering) | Min(Ppu, Ppl) |
Key Difference: Cp/Cpk vs Pp/Ppk
| Aspect | Cp/Cpk | Pp/Ppk |
|---|---|---|
| Variation estimate | Within-subgroup (R̄/d₂ or S̄/c₄) | Overall (sample std dev) |
| Represents | Process potential | Process performance |
| Use when | Process in control | Initial assessment |
| Typically | Higher | Lower |
Capability Formulas
Cp (Process Potential):
Cp = (USL - LSL) / 6σ
Where σ = R̄/d₂ (within-subgroup estimate)
Cpk (Process Capability):
Cpu = (USL - X̄̄) / 3σ
Cpl = (X̄̄ - LSL) / 3σ
Cpk = Min(Cpu, Cpl)
Pp (Process Performance):
Pp = (USL - LSL) / 6s
Where s = sample standard deviation
Ppk (Process Performance Index):
Ppu = (USL - X̄) / 3s
Ppl = (X̄ - LSL) / 3s
Ppk = Min(Ppu, Ppl)
d₂ Constants
| n | d₂ |
|---|---|
| 2 | 1.128 |
| 3 | 1.693 |
| 4 | 2.059 |
| 5 | 2.326 |
| 6 | 2.534 |
Capability Targets
Automotive Industry Standards
| Index | Minimum | Preferred | For CC |
|---|---|---|---|
| Cpk | 1.33 | 1.67 | 1.67 |
| Ppk | 1.33 | 1.67 | 1.67 |
Interpretation
| Cpk Value | PPM (one tail) | Interpretation |
|---|---|---|
| 0.67 | 22,750 | Poor, not capable |
| 1.00 | 1,350 | Barely capable |
| 1.33 | 32 | Capable (minimum automotive) |
| 1.50 | 3.4 | Good |
| 1.67 | 0.3 | Very good (CC target) |
| 2.00 | 0.001 | Excellent |
Capability Study Process
Step 1: Plan the Study
- Identify characteristic
- Select measurement system (verify MSA)
- Determine sample size (minimum 30, prefer 50-100)
- Define sampling method
Step 2: Collect Data
- Collect samples under normal conditions
- Record in time order
- Document any special events
Step 3: Analyze Data
- Create histogram (check distribution)
- Check normality
- Calculate statistics
- Create control chart
- Check for statistical control
Step 4: Calculate Capability
- If in control: Calculate Cp, Cpk
- If not in control: Address special causes first, or report Pp, Ppk only
- Compare to requirements
Step 5: Interpret and Act
- Is capability adequate?
- What actions needed?
- Document results
Pre-Control (Alternative to SPC)
When to Use Pre-Control
- Very capable processes (Cpk >1.33)
- Short runs
- Quick setup verification
- Simpler than SPC
Pre-Control Zones
┌─────────────────────────────────────────────┐
│ RED ZONE │ → Stop, adjust
├─────────────────────────────────────────────┤
│ YELLOW ZONE │ → Caution
├─────────────────────────────────────────────┤
│ GREEN ZONE (Middle 50%) │ → OK
├─────────────────────────────────────────────┤
│ YELLOW ZONE │ → Caution
├─────────────────────────────────────────────┤
│ RED ZONE │ → Stop, adjust
└─────────────────────────────────────────────┘
LSL Target USL
Pre-Control Rules
- Startup: 5 consecutive in Green = run production
- Running:
- Both in Green → Continue
- One Yellow → Check again immediately
- Both Yellow → Investigate/adjust
- Red → Stop, investigate
Output Format
When generating SPC content:
# SPC Analysis
## Characteristic Information
| Field | Value |
|-------|-------|
| **Characteristic** | [Description] |
| **Specification** | [LSL - USL] |
| **Target** | [Nominal] |
| **Chart Type** | [X-bar/R, I-MR, etc.] |
## Control Chart Data
| Subgroup | X̄ (or X) | R (or MR) |
|----------|----------|-----------|
| 1 | | |
| ... | | |
## Control Limits
| Chart | LCL | CL | UCL |
|-------|-----|----|----|
| X-bar | | | |
| R | | | |
## Process Capability
| Index | Value | Requirement | Status |
|-------|-------|-------------|--------|
| Cpk | | ≥1.33 | PASS/FAIL |
| Ppk | | ≥1.33 | PASS/FAIL |
## Assessment
- In Control: Yes / No
- Capable: Yes / No
- Actions Required: [List]
Examples
Example 1 — Selecting and setting up a control chart
User: "We're machining a bore diameter on a CNC lathe, subgroup of 5 parts every hour. What chart should we use and what are the control limits?"
Output: Recommends an X-bar/R chart per Control Chart Selection (subgroups n=2-9), calculates UCL/CL/LCL using the A₂/D₃/D₄ constants for n=5, and flags the minimum 20-25 subgroups needed before finalizing limits per the X-bar/R Chart Setup guidance.
Example 2 — Interpreting an out-of-control signal
User: "Our control chart shows 8 consecutive points above the centerline. Is this out of control, and what should we do?"
Output: Identifies this as a Rule 2 violation (run of 7+ points on one side of centerline) per Out-of-Control Rules, explains it indicates a process/mean shift (special cause variation), and recommends investigation per the MNMUK standard (Western Electric Rules 1-4).
Example 3 — Capability assessment for PPAP
User: "Customer wants Ppk for PPAP submission on a critical characteristic. We measured Cpk = 1.45 in production but haven't calculated Ppk yet."
Output: Distinguishes Cpk (within-subgroup, process potential) from Ppk (overall variation, process performance) per the Key Difference: Cp/Cpk vs Pp/Ppk table, calculates Ppk from the overall sample standard deviation, and compares to the CC target of ≥1.67 per Capability Targets, flagging if Ppk falls short of Cpk (indicating between-subgroup variation exists).
Integration with Related Skills
ControlPlan
Control Plan specifies SPC requirements:
- Which characteristics require SPC
- Sample size and frequency
- Reaction to out-of-control
Load: read ~/.claude/skills/Controlplan/SKILL.md
MSA
SPC validity requires adequate measurement system:
- ndc ≥5 for meaningful SPC
- Poor MSA = poor SPC decisions
- Verify MSA before starting SPC
Load: read ~/.claude/skills/Msa/SKILL.md
AutomotiveManufacturing
Work instructions should include SPC procedures:
- How to collect data
- How to plot points
- How to interpret charts
- What to do when out of control
Load: read ~/.claude/skills/Automotivemanufacturing/SKILL.md
Supplementary Resources
For detailed guidance:
read ~/.claude/skills/Spc/CLAUDE.md
For capability study template:
read ~/.claude/skills/Spc/templates/capability-study.md
For control chart selection:
read ~/.claude/skills/Spc/reference/control-chart-selection.md
For capability indices:
read ~/.claude/skills/Spc/reference/capability-indices.md
For out-of-control rules:
read ~/.claude/skills/Spc/reference/out-of-control-rules.md
FAQ
What does the spc skill do?
Implement SPC charting, process capability analysis, and control chart interpretation. Covers control chart selection, capability indices, and out-of-control rules. USE WHEN user says 'SPC', 'Cpk', 'Ppk', 'control chart', 'process capability', 'X-bar R', 'statistical control', or 'out of control'. Integrates with ControlPlan, MSA, and AutomotiveManufacturing skills.
How do I install spc?
Run npx skills add https://github.com/robdtaylor/personal-ai-infrastructure --skill spc in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/spc/ (personal) or .claude/skills/spc/ (project).
Which AI agents can use spc?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is spc safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains spc?
It is published by robdtaylor in robdtaylor/personal-ai-infrastructure. It has 50 recorded installs.
More from robdtaylor/personal-ai-infrastructure
businessstrategy
robdtaylor/personal-ai-infrastructure
MBA-trained business strategist with full commercial awareness. USE WHEN user says 'business plan', 'financial analysis', 'P&L', 'cash flow', 'valuation', 'market analysis', 'competitive analysis', 'SWOT', 'business model', 'unit economics', 'fundraising', 'pitch deck', or needs strategic business guidance.
structuralfea
robdtaylor/personal-ai-infrastructure
Open source FEA structural analysis for damper and mechanical components. Generates CalculiX input files, guides mesh setup, provides material databases, interprets results. USE WHEN user says 'FEA', 'structural analysis', 'stress analysis', 'buckling', 'modal analysis', 'finite element', 'CalculiX', 'mesh', or needs to validate damper component designs.
shippinglogistics
robdtaylor/personal-ai-infrastructure
UK, US, and Canadian shipping, logistics, customs, duties, and tariff expert with automotive commodity code expertise. Covers import/export documentation, HS/HTS codes, rules of origin, FTAs, and landed cost calculations. USE WHEN user says 'shipping', 'customs', 'tariff', 'duty', 'import', 'export', 'HS code', 'HTS code', 'commodity code', 'landed cost', 'incoterms', 'customs broker', 'freight', 'logistics', 'rules of origin', 'CUSMA', 'USMCA', 'TCA', or needs help with international trade compliance.
supplychain
robdtaylor/personal-ai-infrastructure
Executive-level supply chain expertise for automotive manufacturing. Strategic purchasing, materials management, supplier development, and cost optimization aligned with IATF 16949 requirements. USE WHEN user says 'supply chain', 'purchasing', 'procurement', 'supplier', 'materials management', 'inventory', 'sourcing', 'vendor', 'BOM cost', 'PPV', 'should cost', 'make vs buy', 'RFQ', 'category management', or needs strategic guidance on automotive supply chain decisions. Integrates with AutomotiveManufacturing, A3CriticalThinking, and HoshinKanri skills.
automotivemanufacturing
robdtaylor/personal-ai-infrastructure
Expert guidance for writing automotive manufacturing business processes, work instructions, and standard operating procedures. Follows IATF 16949, ISO 9001, and APQP/PPAP standards. Covers assembly, machining, quality/inspection, and material handling. USE WHEN user says 'write work instruction', 'create business process', 'automotive SOP', 'manufacturing procedure', 'APQP documentation', 'process flow', or 'quality procedure'. Integrates with A3CriticalThinking for problem solving and SupplyChain for supplier requirements.
quoteestimator
robdtaylor/personal-ai-infrastructure
Rough cycle time and cost estimation for CNC machined parts. Uses MNMUK plant capabilities and standard estimating factors. USE WHEN user says 'quote', 'estimate', 'cycle time', 'how long', 'cost estimate', 'pricing', 'how much to make', or describes a part needing a rough quote.
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.