About this skill

Problem

Production weekly reports often split outputs, yield, OEE, delivery rate, equipment issues, retrofit progress, and next-week plans across verbal notes, Word paragraphs, and Excel sheets. Manual drafting can miss carried-over items and make it hard to see which problems have been delayed or which projects remain blocked. This repeated cleanup also takes time away from data verification and can leave reports looking like simple logs.

How It Works

Multi-source parsing: accepts verbal descriptions, .docx file paths, and .xlsx file paths, then parses them into JSON-like structured fields.
Data gates: requires at least one completed item, one next-week plan, and one core metric; if missing, it stops and reports the gap.
History tracking: reads the last four weekly reports, extracts unresolved issues, in-progress projects, and carried-over tasks, and marks status changes or aging.
Report output: merges current data with tracked items, generates a fixed-section HTML page with embedded styles, and archives it under ./weekly_reports/history/.

Boundaries

Best for production management roles with basic production data and recurring report files. Not suited for real-time cross-system data pulls, complex BI dashboards, permission workflows, or automated distribution.

Screenshots

Use Cases

Before a weekly meeting, compile verbal notes, Word, and Excel outputs, yield, and equipment issues into an HTML report.
Read an .xlsx production sheet for completed items, next-week plans, and core metrics, then generate a printable PDF-ready web report.
Review the last four weekly reports to flag unresolved issues, in-progress projects, and changes in carried-over tasks.
If next-week plans or core metrics are missing, stop generation and prompt for gaps instead of inventing data.

Best For

Production supervisors who compile line output, yield, and OEE into a fixed weekly report
Site managers who archive equipment failures, retrofit progress, and next-week plans into weekly reports
Production data specialists who parse Word and Excel production logs into one structure
Project coordinators who track unresolved issues and carried-over tasks across the last four weeks