What problem does it solve? When UI labels change in a product release, Japanese manuals often retain outdated capture text. This Skill checks whether As-is/To-be terms from the requirements sheet are correctly reflected in Japanese manual DOCX and PDF files, producing a structured consistency report. ## Core Features & Use Cases - Term Consistency Scanning: Reads the WEB_UI capture sheet from the requirements xlsx and counts As-is and To-be term occurrences in manual documents. - Status Classification: Labels each row as APPLIED, RESIDUAL, or N/A based on term counts, flagging outdated labels that remain in the manual. - Report Generation: Writes a dated Markdown report under the review results folder summarizing counts and top residual terms. - Use Case: Before shipping a Japanese manual update, run this check against the latest requirements sheet to confirm every renamed UI label was actually applied in the DOCX and PDF deliverables. ## Quick Start Check whether the Japanese manual in my 305매뉴얼 folder reflects all UI label changes from the latest requirements sheet and write a consistency report.