Checkpoints and Execution

Checkpoints let a team stop work earlier than PR creation. Execution commands track longer work that has planning, task, PR, and merge phases.

Lifecycle checkpoints

vibepro checkpoint story .
vibepro checkpoint implementation-start . --story-id <story-id>
vibepro checkpoint test-plan . --story-id <story-id>
vibepro checkpoint implementation-complete . --story-id <story-id>
vibepro checkpoint verification . --story-id <story-id>
vibepro checkpoint pr . --story-id <story-id>

Stage	Blocks until
story	Story, architecture, and Spec gates are explicit
implementation-start	planning and architecture/spec reviews are complete
test-plan	test plan review is complete
implementation-complete	implementation review and runtime gates are complete
verification	verification, gate review, and current-head evidence are complete
pr	every required Gate DAG item is complete

Execution state

Use execution commands when work spans multiple steps or managed worktrees:

vibepro execute start . --story-id <story-id> --target pr_create --base origin/main
vibepro execute status . --story-id <story-id>
vibepro execute next . --story-id <story-id>
vibepro execute reconcile . --story-id <story-id>
vibepro execute merge . --story-id <story-id> --strategy squash --pr <number>

execute next should point to the next evidence-producing action, not simply to PR creation.

Task handoff

Task commands split a Story into reviewable work units:

vibepro story plan .
vibepro task create . --from-plan --id <story-id>
vibepro task list . --id <story-id>
vibepro task brief . --task <task-id> --id <story-id>
vibepro task execute . --task <task-id> --id <story-id> --dry-run-pr

Use task artifacts when different agents or worktrees own separate parts of the same Story.

Exploration records

Exploration is for investigative work before implementation:

vibepro explore prepare . --id <story-id> --topic "<question>"
vibepro explore record . --id <story-id> --role architecture --status needs_review --summary "<finding>"
vibepro explore status . --id <story-id>