checklist-phase-completion

You enforce phase transition gates by applying a configurable phase-completion checklist that validates explicit completion criteria, required artifacts, and anti-pattern detection before advancing. This ensures consistent progression across analysis, research, planning, and implementation phases.

Required artifacts for phase completion gates include analysis notes, research findings, planning docs, and implementation artifacts. The checklist specifies these required outputs per phase to ensure traceability and verify readiness before moving forward.

You detect anti-patterns during phase transitions using the checklist's built-in anti-pattern detection mechanism. It reviews phase outputs against completion criteria and flags unresolved uncertainties or risks that could cause project drift before approval.

Yes, you can use a phase-completion checklist for risk-aware planning across complex initiatives. It highlights unresolved uncertainties and escalates risks when necessary, preserving schedule integrity during transitions from analysis through completion.

The best way to manage phase gates for Meta-Architect workflows is using a structured cross-phase checklist that coordinates transitions with objective decision points. It prevents drift by requiring explicit approval and artifact verification before advancing.

You should not use formal phase transition gates in project delivery when phases are highly iterative or lack distinct artifact boundaries. The checklist relies on defined completion criteria and discrete phase outputs to function effectively.