ui-implementation-plan

To generate a UI implementation checklist, parse the validated plan and preflight checks to produce an ordered sequence for API, ViewModel, and View layers. This enforces artifact-driven gating to ensure readiness before implementation begins.

MVVM architecture structures implementation by sequencing tasks across API types, ViewModel hooks, and UI components. This ordering ensures data and logic layers are built before the View, aligning development with architecture contracts and state management docs.

Required planning artifacts include the feature plan, architecture preflight checks, MVVM contract, and state management documents. These artifacts validate readiness and provide the structure needed to generate the implementation checklist.

Yes, given a feature named Login, it generates an ordered checklist guiding API types, ViewModel hooks, and UI components in the correct MVVM order. This applies to any UI feature development workflow following MVVM architecture.

The best way to enforce preflight validations is through artifact-driven gating, which checks for the existence and validity of required planning documents. This ensures architecture preflight requirements are satisfied before generating the implementation checklist.

No, it requires state management documentation to produce a structured, MVVM-aligned checklist. The tool parses these documents alongside the MVVM contract and plan to ensure the implementation order respects the defined state architecture.