openspec-preflight

A preflight check for code changes inspects proposal artifacts to identify critical gaps and human-required tasks before implementation begins. You need it to reduce mid-implementation surprises and ensure workflow cohesion.

To identify human-required tasks in OpenSpec changes, run a preflight check that flags operator interventions like credentials, GCP provisioning, and external dashboards. This surfaces manual requirements early in the workflow.

To verify counterpart-layer cohesion, run a preflight inspection that checks user-facing capabilities for corresponding client surfaces and data consistency. This ensures data layers align before implementation starts.

Yes, you can reconcile proposal claims against canonical documentation automatically. The preflight process compares artifacts against canonical docs to check for consistency and flags discrepancies before implementation.

Yes, preflight mapping verifies that all test scenarios have corresponding test tasks. It inspects proposal artifacts to map test scenarios, ensuring complete test coverage before implementation begins.

To run a preflight check, you need proposal artifacts and access to canonical documentation. The preflight process requires these inputs to inspect gaps, reconcile claims, and map test scenarios effectively.