gsd:workflow:checkpoint

You can track and approve project milestones by creating checkpoints at phase boundaries, updating ongoing progress, and formally completing them to trigger the next phase. This ensures phase alignment and measurable progress for wave-based projects.

Managing phase handoffs in a wave-based project is best handled through formal checkpoint completion, which requires approval to ensure explicit entry criteria are met before continuing to the next phase or iteration.

To create a checkpoint for a new phase, use the create-checkpoint entry point to define the boundary and document the initial progress notes, establishing a structured baseline for tracking and future approvals.

Yes, you can update and continue a checkpoint to reflect ongoing work and decisions. This allows you to document current progress and iterate before formally completing the checkpoint for final approval.

Yes, the workflow supports approving or rejecting checkpoints. Rejecting a checkpoint prevents phase advancement and triggers necessary iterations to ensure all success criteria and phase alignment are met.

You need a formal checkpoint workflow when managing wave-based projects that require explicit milestones, structured approvals, and clear handoffs to ensure measurable progress and strict phase alignment across project teams.