landing-report

Visualize the workspace version queue with PR slot claims and next ship slot.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/MissTully/Gstack --skill landing-report-misstully
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: landing-report
Source: https://github.com/MissTully/Gstack/tree/main/landing-report
Command: npx skills add https://github.com/MissTully/Gstack --skill landing-report-misstully

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only view of the workspace version queue to reveal which slots are claimed by open PRs, which Conductor workspaces have in-progress work, and what slot would ship next.

Core Features & Use Cases

  • Deterministic, read-only dashboard of version slots and PR statuses for release planning.
  • Helps multi-workspace teams decide which version to ship next without mutating state.
  • Use during planning sessions or when answering "what's in the queue" queries.

Quick Start

Ask the landing-report skill to show the current version queue and identify the next slot to ship.

Frequently Asked Questions about landing-report

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

FAQPage Schema
How do I view which workspace version slots are claimed by open PRs?

To view which workspace version slots are claimed by open PRs, use a read-only landing report dashboard that reads workspace state and PR data to visualize the version queue. It provides a deterministic snapshot without mutating state.

What is a workspace version queue and when do I need a read-only snapshot?

A workspace version queue shows which Conductor workspaces have in-progress work and which slots are claimed by open PRs. You need a read-only snapshot during release planning, PR reviews, or multi-workspace coordination to make safe decisions.

How do I find out what version slot will ship next during release planning?

To find out what version slot will ship next during release planning, generate a landing report. It reads current workspace state and PR data to deterministically identify the next slot that would be picked.

Can I use a landing report for multi-workspace coordination without changing state?

Yes, you can use a landing report for multi-workspace coordination without changing state. It is a strictly read-only dashboard that reads workspace state and PR data to present clear, actionable insights without mutating anything.

What are the limitations of using a read-only dashboard for ship planning?

The limitation of using a read-only dashboard for ship planning is that it cannot mutate workspace state or claim version slots. It only visualizes the current queue and PR statuses, requiring separate tools to execute shipping actions.