design-sync

Design drift detection compares your creative-brief.md, parameter-spec.md, and panel YAML to identify misalignments. The Skill applies quantitative checks on parameter counts and HP width, plus semantic validation against feature coverage, then categorizes drift severity and recommends corrective actions.

Validation requires three inputs: a finalized creative-brief.md defining the original scope, a parameter-spec.md generated from your panel configuration, and a vN-panel.yaml file representing the current design. All three must be present to run drift detection.

Run design validation during Stage 5 planning and Stage 1 pre-checks, before GUI implementation begins. This catches inconsistencies early when corrective actions—adjusting the brief, updating the panel, or refining scope—are still practical.

The Skill produces a pass/fail decision with explicit thresholds for parameter counts, HP width, and feature coverage. If thresholds are exceeded, drift is categorized by severity level, and you receive recommended actions to realign the panel or adjust the brief.

No. The Skill requires a finalized panel with parameter-spec.md already generated. Use it after your panel configuration is complete but before GUI implementation to validate consistency with the creative brief.

The Skill presents a menu of corrective actions. Adjust the brief if scope assumptions changed; update the panel if implementation diverged from intent. The Skill's categorization and severity assessment help guide which action fits your situation.