8D Report Generation Assistant

Problem It Solves

Quality issue write-ups often stop at symptoms and containment, without a traceable cause chain, verification loop, or preventive actions. An 8D report requires coverage of D0-D8, but manually drafted reports can miss fields, drift from the expected format, or keep D4 analysis at a high level and fail review.

How It Works

The skill uses step-by-step guidance and conversational collection: it asks only 1-2 questions at a time, with explanations, examples, and hints; missing data can be handled with now, later, or skip, and users can jump back with modify XX.

The main flow includes:
- Pre-information: issue ID, project name, key dates, customer/product context.
- D1-D3: team, problem description, and containment actions, including owners and timing.
- D4 core analysis: root-cause work around 5M1E, escape cause, and 5WHY.
- D5-D8: corrective actions, verification, prevention, and closure.

It first outputs a structured Markdown report, expected to show analysis in tables and include concrete values, dates, and evidence; only after user confirmation does it call the python-docx-based script to export Word.

Fit And Limits

It fits quality problem analysis, customer complaint closure, and internal failure reviews where an 8D document is required; it does not replace investigation, testing, or engineering validation. If inputs are incomplete, the report still prompts for follow-up; Word export depends on a local python-docx environment and is triggered only on confirmation.