8D Report Quality Review

Problem Context

8D reports often look structurally complete, but it is hard to judge quickly whether D4 traces root causes to technical or management layers, or whether D7 actually updates FMEA and CP. Engineers need to turn scattered text in Word, PDF, and Excel into a reviewable structure.

How It Works

The skill first calls parse_document.py to parse the document and output JSON text, then cleans headers, footers, numbering, and special characters, and labels D1 through D8. It requires the user to confirm the full extracted text before analysis. The review checks each step:
- D1-D3: team capability, quantified problem description, and verifiable containment measures.
- D4: whether 5Why, FMEA, or fishbone diagrams trace technical or management causes, and validate occurrence and escape causes.
- D5-D7: whether corrective actions target root causes, preventive actions expand horizontally, and CP, FMEA, SIP files are updated.
- D8: whether action items close and customer sign-off is completed.

Boundaries

This skill is suitable for reviewing existing 8D report text or documents, not for replacing fault tree analysis, MSA, or 8D training. If parsing is incomplete, user correction is required; for pasted text it can skip script parsing, but loses original layout information.