ship-sprint

Sprint planning automation pulls backlog features and decomposes them into deterministic waves for parallel work, ensuring velocity-driven capacity tracking and carry-over prioritization across projects. You execute this by running the /ship-sprint command and selecting features.

Calculating sprint capacity uses velocity history to determine team limits and automatically warns on overcommitment. This mechanism ensures the decomposed waves align with actual team throughput, preventing unrealistic sprint loading.

Extending an active sprint plan triggers a carry-over scan that integrates existing sprint state with new features. The workflow supports canceling, archiving, or resuming work while prioritizing carry-over items before new backlog features.

Wave orchestration applies across Shipyard projects, coordinating sprint planning by pulling backlog features and tracking capacity per project. It manages state transitions and plan persistence to keep multi-project sprints synchronized.

Existing backlog features are required for sprint wave decomposition, as the workflow pulls these features to calculate velocity-driven capacity and orchestrate parallel work. Without backlog items, sprint planning cannot execute.

Sprint planning requires state transitions for archiving completed work to maintain plan persistence and ensure accurate carry-over prioritization for future sprints. Archiving cleans the active sprint state and finalizes the workflow.