transition

Phase transitions are coordinated by marking the current phase complete and advancing to the next while updating progress tracking across PROJECT.md, STATE.md, and the ROADMAP. The workflow enforces completeness checks and consistent state evolution across all related documents.

During phase transition, completeness checks verify that all current-phase PLAN.md and SUMMARY.md files are present. If incomplete, safety rails trigger user prompts for action, preventing destructive state updates when required plans are missing.

Phase management evolves project documentation by updating ROADMAP.md to mark completed phases, advancing current position in PROJECT.md, and refreshing STATE.md with accumulated context to reflect progression to the next phase.

Phase transitions support both interactive and deterministic modes for handoffs. The workflow cleans up stale handoffs and archives prompts to prepare for the next phase planning cycle, with safety rails preventing destructive actions when plans are missing.

Run the phase transition workflow during project roadmapping, phase handoffs, and updates to PROJECT.md, STATE.md, and the ROADMAP when you need to mark the current phase complete and coordinate state evolution across all related documents.

Yes, the transition workflow enforces completeness checks that verify all current-phase PLAN.md and SUMMARY.md files are present before marking a phase complete and advancing, applying safety rails to prevent progression when plans are missing.