What problem does it solve? Teams that receive standardized requirement-design specification documents (with function codes, IPO tables, and flow descriptions) must manually translate them into structured page definitions before any code can be generated. This Skill automates that translation, converting spec documents into the same page-spec JSON format consumed downstream by API contract and page generation steps. ## Core Features & Use Cases - Structured Spec Parsing: Recognizes the doc-skeleton structure (ch1-3.md, 4.x-{module}.md, 4.N-data-report.md), extracts function codes, IPO tables, field definitions, and control types, then maps them to page-spec JSON. - Self-Validation and Auto-Correction: Runs five parse validation checks, auto-fixes lossless issues like legacy activity code formats, and blocks on architectural problems (invalid function codes, unknown service prefixes) instead of guessing. - Parse Reports: Produces a report listing parsed functions, pending confirmations, auto-fixes, and blocked items for traceability. - Use Case: Given .wl-skills/docs/spec/huaxin/4.1-target.md containing function code PMMB001 with IPO tables, the Skill outputs page-spec JSON plus a SPEC_PARSE report, ready for the api-contract and page-codegen steps. ## Quick Start Parse the specification document at .wl-skills/docs/spec/huaxin/4.1-target.md into a page-spec JSON and generate the parse report.