landing-report

To check the status of version queues and open pull requests, you can generate a read-only landing report that displays which version slots are claimed by open PRs and identifies work in progress across sibling Conductor workspaces.

Viewing the next version slot to ship is best done by generating a landing report, which predicts the next version slot that /ship would select and shows the current status of version queues without making mutations.

You can see which sibling Conductor workspaces have work in progress likely to ship soon by requesting a landing report, which provides a snapshot view of workspace statuses and claimed version slots.

To generate a landing report for software development workflow management, ask the landing-report Skill to execute, utilizing Bash and Read tools to produce a read-only queue dashboard showing version slots and open PRs.

The landing report does not modify version control queues or pull requests; it provides a no-mutation, read-only snapshot view of the current version slot statuses and open PR activity for software development teams.

You need a queue status dashboard for pull request-based development when you want to understand the current status of version slots, see open PRs, and determine which version will be picked next without altering the workflow.