investigate-qc-failures — skills/head-of-manufacturing/investigate-qc-failures/SKILL.md
← back to all skills · test triggers
Skill: Investigate QC Failures
When to apply
Triggered hourly via the manufacturing-qc-sweep cron, or ad-hoc when COO delegates a "look into QC" task.
Workflow
- Call
read_org_metricsfor the current snapshot. - Query the audit for the last 24h of tracking events — specifically
look for
qc_failanddamage_reportedevents. (Tools: this isn't built yet as a direct call — for v1, just look at recent sim_tracking_events and reason from there.) - If failure rate < 5% of total QC events, no action. Post a comment on the relevant goal saying "QC pass rate normal."
- If failure rate ≥ 5% OR ≥ 3 absolute failures in 24h:
- Call
create_taskwith owner_role="head-of-manufacturing", priority="high", delegated_by="head-of-manufacturing" (self-assigned), title="QC failure spike investigation —", description=specific SKUs/frame types affected. - Call
post_org_commenton the related goal noting the spike. - If failure rate ≥ 10% OR a single SKU has ≥ 5 failures, also escalate
to COO: another
create_taskwith owner_role="coo", priority="urgent", delegated_by="head-of-manufacturing", description that summarizes the pattern.
Outputs
{
"action": "respond",
"reasoning": "QC failure rate 7% in 24h, 4 failures concentrated on metal substrate. Task created; flagged COO for capacity review.",
"confidence": 0.92,
"output": "1 QC investigation task created + 1 COO escalation"
}
Rules
- Frame-defect spikes (failures on framed pieces) often point at a single frame batch — note the frame option in the task description so the follow-up can isolate.
- Substrate-specific patterns (metal, acrylic) often indicate a press calibration issue — flag in the task to check calibration logs.
- One investigation task per spike, not per failure. Avoid spam.
- Always reference the period in the title (date, week) so historical tasks are easy to find.
Anti-patterns
- Do not pause production from this role — that's COO's call.
- Do not contact the affected customers — that's CS's lane.
- Do not propose specific fixes in the brief; describe the pattern and let the assignee diagnose.