sl:ship

You can automate multi-phase plan execution by orchestrating plan resolution, hydration, execution, and review phases in dependency order. This workflow applies post-phase validation gates to prevent drift and ensure visibility across the entire release cycle.

The best way to prevent plan drift is to enforce quality gates after each execution phase. By validating progress against the resolved plan before moving to the next dependency, you ensure the workflow stays aligned with the original specifications.

Yes, you can run plan phases in parallel and automate approvals. The workflow supports auto-approval, parallel execution, and a no-test mode, allowing you to speed up orchestration while maintaining post-phase validation checks.

You can track progress by integrating plan files with task tracking during execution. The workflow coordinates each phase, providing visibility and reporting on ownership to ensure every step of the release is monitored and validated.

You should use parallel execution mode when you need to speed up multi-phase releases across independent tasks. It allows multiple phases to run concurrently while still applying quality gates, ensuring that dependency order is respected and drift is prevented.