arkweb-spec-review

Reviewing OpenHarmony ArkWeb design documents requires a checklist-based gatekeeping process to validate structural completeness, cross-document consistency, and technical feasibility. This generates a detailed checklist result table, identifies blocking items, and produces a saved review report.

Cross-document consistency validation in ArkWeb spec reviews ensures design documents align with ace_engine and web-webview analyses. It cross-validates class names, interface signatures, and file paths to reduce omissions and deviations across related requirement and design artifacts.

Running an ArkWeb spec validation workflow involves providing the design document path, code analysis results path, and reference materials path. It applies a 33-item checklist covering feasibility and DFX, ultimately outputting a pass, needs-modification, or fail conclusion.

A design review checklist can establish a quality gate before submitting an ArkWeb PR by running a minimized review loop of inspection, modification, and re-inspection. This ensures documents meet interface design and DFX standards, providing concrete justification for PR submission.

ArkWeb design documents need repeated revisions when structural completeness, terminology consistency, and interface-chart linkages are insufficient. Applying a systematic 33-item spec validation checklist identifies these blocking items early to minimize rework loops.

Performing an OpenHarmony ArkWeb requirement and design review is best handled via a Subagent mode that systematically evaluates structural completeness and technical feasibility. It produces a unified review report to drive the design document modification loop.