gaia-val-validate-plan

To validate implementation plans, you can run a plan validator against your plan artifact to identify misconfigurations in file targets, version bumps, and ADR references before execution. This prevents failed deployments by producing actionable findings with severity labels and plan-step mapping.

Plan validation in GAIA workflows checks target existence, version sequencing, and architecture alignment in plan artifacts. It verifies file targets, version bumps, and ADR references to prevent regressions and deployment failures caused by out-of-date architecture decisions.

You can check version bump sequencing and ADR alignment by running a validation process on your plan artifacts. This process requires access to plan artifacts, memory loader context, and ADR-guided architecture guidance to produce structured findings with severity labels for fast remediation.

No, validating a plan artifact requires access to plan artifacts, memory loader context, and ADR-guided architecture guidance. Without these inputs, the validator cannot perform checks on target existence, version sequencing, and architecture alignment to produce actionable findings.

The best way to prevent deployment failures from misaligned architectures is to perform end-to-end plan validation prior to execution. This validates file targets, version bumps, and ADR references, exposing a structured set of findings with severity labels and plan-step mapping for fast remediation.

Plan validation may fail when checking ADR references if the architecture decisions in your plan artifacts are out of date or misaligned. The validator requires ADR-guided architecture guidance and memory loader context to verify architecture alignment and produce accurate findings.