executing-sequential-phase

Sequential-phase execution automates stacking by using `gs branch create` to stack branches on HEAD in your main worktree. Tasks run in order on their task branches without requiring manual `gs upstack onto` commands, keeping the stack intact and simplifying phase workflows.

Sequential phases execute all tasks in a single main worktree using natural stacking, while separate worktrees fragment work across multiple directories. This Skill keeps dependent tasks on the same shared workspace, maintaining stack integrity and avoiding manual branch management.

Yes. Sequential-phase execution keeps each task on its own task branch while maintaining proper stacking order. Tasks build on each other through git-spice's natural stacking mechanism, so branches remain separate but logically connected in the stack.

Phase boundary enforcement ensures tasks implement only work from the current phase. The Skill verifies that each task stays within its phase scope, preventing tasks from pulling in work from other phases and maintaining clear separation of concerns.

Verify the stack through git-spice logs and contextual checks to confirm branches are properly stacked, tasks executed in order, and all phases remained on the main worktree. This confirms the sequential execution completed without manual upstack issues.