phase-transition

A phase transition review is a structured process to inventory deliverables, triage open issues, and validate assumptions before safely migrating project work to a new phase. It prevents scope gaps during phase changeovers.

Manage issue triage and risk handoff by reviewing unresolved items and deciding whether to carry them over for continuous handling or close them. This ensures open risks are properly transitioned to the new phase.

Define scope and create a new phase by using phase entity transitions or forks, then specifying the implementation range and deferred items. This establishes clear boundaries for the upcoming project work.

Yes, approval-gated execution and phase-aware migration require admin-profile ProjSight MCP tools. This access level supports secure phase creation and scope definition decisions.

The best way to review deliverables is to classify them as in-progress, under-review, or draft, then decide whether to carry them over to the new phase or mark them as complete. This prevents unfinished work from slipping.

Fork a phase when divergent scope paths are needed, rather than a linear transition. This creates distinct phase entities to handle separate deliverable tracks while maintaining proper issue triage.