landing-report

Generate a read-only queue snapshot of claimed version slots and sibling workspace WIP.

Updated May 7, 2026
One-click install
npx skills add https://github.com/TumeloRamaphosa/StudEx-Valley-OS --skill landing-report-tumeloramaphosa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: landing-report
Source: https://github.com/TumeloRamaphosa/StudEx-Valley-OS/tree/main/.claude/skills/gstack/landing-report
Command: npx skills add https://github.com/TumeloRamaphosa/StudEx-Valley-OS --skill landing-report-tumeloramaphosa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The landing-report skill helps you quickly understand what is currently in the version queue and what you should claim next, without making any changes to the repo. It removes guesswork by showing which VERSION slots are already claimed by open PRs and which sibling Conductor workspaces have WIP likely to ship soon.

Core Features & Use Cases

  • Queue snapshot dashboard (read-only): Provides a workspace-aware view of which version slots are claimed and which slot/ship would be picked next.
  • PR-to-slot visibility: Surfaces which VERSION slots are currently taken by open PRs, so you do not double-claim work.
  • Sibling workspace WIP forecasting: Identifies sibling Conductor workspaces with WIP that is likely to ship soon, helping you pick the best next action.
  • Use when asked for operational context: Designed for requests like “landing report”, “what’s in the queue”, “show me open PRs”, or “which version do I claim next”.

Quick Start

Ask your AI to run landing-report to view the current version queue snapshot and see which version/ship should be claimed next.

Frequently Asked Questions about landing-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check which version slots are claimed by open PRs before claiming the next one?

A read-only landing report checks which version slots are claimed by open PRs so you can avoid double-claiming work. It provides a workspace-aware queue snapshot without making any changes to the repository.

What is the best way to view the version queue dashboard without modifying the repository?

A no-mutations queue dashboard view shows currently open PRs and claimed version slots. It uses read-only tools to gather state, ensuring the repository remains completely untouched during release coordination.

How does sibling workspace WIP forecasting work for version intake coordination?

Sibling workspace WIP forecasting identifies sibling Conductor workspaces with work in progress likely to ship soon. This helps you pick the best next action by showing which version slot would be picked next.

Can I use the landing report to see what I should claim next from the ship queue?

Yes, you can use the landing report to see what you should claim next from the ship queue. It applies deterministic snapshot behavior to show which version or ship slot is ready to be claimed.

Do I need any specific environment setup to get a read-only view of the version queue?

You need a Conductor workspace environment with open pull requests and active version slots. The skill relies on its CLI preamble and read-only tools to gather state, requiring no additional dependencies.

Why should I use a read-only reporting tool instead of directly inspecting the ship queue?

A read-only reporting tool prevents accidental mutations while providing a deterministic snapshot of the queue. Directly inspecting the ship queue risks modifying state and lacks workspace-aware sibling WIP visibility.