recipe-prepare-implementation

Preflight checks evaluate an approved work plan by validating references, prerequisites, and observability requirements to ensure Phase 1 execution can proceed without missing UI or environment surfaces.

An Implementation Readiness Report is a deterministic output that confirms a work plan meets the Implementation Readiness Marker Contract. You need it when verifying Phase 0 prep tasks are complete before starting Phase 1 build execution.

You generate prep tasks by running preflight checks on an approved work plan; when readiness gaps are discovered, the system automatically articulates Phase 0 implementation prep tasks to resolve them.

Yes, preflight readiness checks are applicable across both backend and frontend tasks, validating verification references, prerequisites, and environment surfaces from Phase 0 prep through Phase 1 execution.

Preflight checks require an approved work plan as input and only validate references, prerequisites, and observability criteria; they do not execute implementation logic or generate code for the actual build.

A work plan fails the Implementation Readiness Marker Contract when preflight checks detect missing verification references, incomplete prerequisites, or absent observability criteria required for Phase 1 execution.