What problem does it solve?
Managing deployment version slots across multiple pull requests and team workspaces is error-prone and time-consuming, requiring manual checks of PR status, WIP work, and available ship slots to avoid conflicts.
Core Features & Use Cases
- Version Slot Tracking: Shows exactly which VERSION slots are currently claimed by open PRs in your workspace, so you never accidentally overwrite someone else's deployment.
- WIP Work Visibility: Displays which sibling Conductor workspaces have work in progress likely to ship soon, helping you coordinate with your team and avoid version conflicts.
- Next Ship Prediction: Tells you precisely what slot the /ship command would pick next for your changes, so you can plan your deployment timeline accurately.
Use case: If you are a developer preparing to merge a feature branch, use this skill to instantly confirm your target version slot is available and see if any team work is queued ahead of your changes, without running multiple git and gstack commands manually.
Quick Start
Use the landing-report skill to show me the current version queue and which slot I should claim next for my pull request.
