spec-doc-parse

Parse standardized requirement-design specification documents into page-spec JSON for Vue page generation.

5|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ChenyCHENYU/wl-skills-kit --skill spec-doc-parse-chenychenyu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-doc-parse
Source: https://github.com/ChenyCHENYU/wl-skills-kit/tree/main/files/.wl-skills/skills/core/spec-doc-parse
Command: npx skills add https://github.com/ChenyCHENYU/wl-skills-kit --skill spec-doc-parse-chenychenyu

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about spec-doc-parse

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a requirement specification document into page-spec JSON?

Point the Skill at the spec directory under .wl-skills/docs/spec/ containing ch1-3.md and 4.x module files. It extracts function codes, IPO tables, and field definitions, then outputs page-spec JSON plus a parse report with pending confirmations.

What is the difference between spec-doc-parse and prototype-scan?

spec-doc-parse handles standardized wl-skills-design specification documents with function codes and IPO tables, while prototype-scan handles Axure prototypes, screenshots, and informal design notes. Both produce the same page-spec JSON format for downstream page generation.

Does spec-doc-parse generate Vue page code directly?

No, it only produces page-spec JSON and a parse report. Code generation is handled by the downstream page-codegen Skill, and API contracts are handled by the api-contract step.

What happens when the spec document has invalid function codes?

Function codes not matching the required pattern are treated as architectural decisions and blocked rather than auto-fixed. The blocked item is listed in the parse report for manual resolution before continuing.

Can spec-doc-parse parse Axure prototypes or screenshots?

No, it explicitly rejects Axure HTML and screenshots. Those inputs belong to the prototype-scan line, and the Skill will redirect you to it when non-standard documents are detected.