create-validation-plan

Create a validation plan by defining measurable, observable, and falsifiable PASS criteria per journey. This plan maps user journeys to observable evidence, avoiding ad-hoc testing and unverifiable results by prioritizing dependency-aware validation efforts.

Journey discovery is the process of scanning codebases and platforms to enumerate routes, endpoints, screens, and CLI commands as distinct journeys. It identifies prerequisites and execution order before evidence capture begins.

Map dependencies and execution order by producing a persistent validation-plan artifact. This file structures per-journey steps and prerequisites into an execution sequence suitable for automated and manual evidence capture.

Yes, the validation plan produces a persistent artifact with per-journey steps, falsifiable PASS criteria, dependencies, and an execution order. This structure is explicitly designed to support both automated and manual evidence capture.

You need a validation plan before evidence capture to avoid missing dependencies and ad-hoc testing. It ensures validation efforts are prioritized, dependency-aware, and mapped to observable evidence for verifiable PASS criteria.

A validation plan file should use a structured markdown format, such as validation-plan.md. Populate it with journey IDs, priorities, dependencies, prerequisites, and at least two falsifiable PASS criteria per journey.