verify-phase

To verify phase goals are delivered, analyze the codebase by deriving must_haves from ROADMAP goals and checking artifacts for existence and wiring. This goal-backward verification ensures outcomes meet intended promises, producing a VERIFICATION.md report.

Goal-backward verification is a process that starts from phase outcomes to identify what must be true, what must exist, and how components must be wired. It traces goals through artifacts to validate that results meet phase promises rather than just completing tasks.

Generate a VERIFICATION.md report by running a verification process that checks artifacts for existence, substance, and wiring. The report includes evidence, statuses, and recommendations for fixes, ready to guide orchestration for the identified phase.

Yes, you need a ROADMAP and PLAN to verify phase outcomes, as must-haves are derived from ROADMAP goals or explicit PLAN frontmatter. REQUIREMENTS and phase summaries are also analyzed to validate truths, artifacts, and wiring for the phase.

The best way to check artifact substance and wiring is using an automated verification process that derives must_haves from phase goals. It validates artifact existence, verifies substance, and checks component wiring to ensure the phase outcome is truly delivered.