queue

Display a read-only multi-agent ship queue dashboard from the fstack brain.

1|Updated May 4, 2026
One-click install
npx skills add https://github.com/sanskarbasnet/fstack --skill queue-sanskarbasnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: queue
Source: https://github.com/sanskarbasnet/fstack/tree/main/queue
Command: npx skills add https://github.com/sanskarbasnet/fstack --skill queue-sanskarbasnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only multi-agent ship queue dashboard that shows what each agent is shipping, what's in flight, what version slots are claimed, and what /ship would pick next. Reads from fstack brain so it covers both agents. No mutations.

Core Features & Use Cases

  • Read-only visibility into two agents' ship queues from the fstack brain, including shipped items, in-flight work, and current commitments.
  • Quick assessment for planning: understand bottlenecks, prioritize handoffs, and anticipate the next ship decision.
  • Use Case: when your team asks "what's in the queue now?" or "which version comes next?", this dashboard gives a unified view across agents.

Quick Start

Run the queue view to inspect both agents' ship queues from the fstack brain and confirm the next ship decision.

Frequently Asked Questions about queue

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

FAQPage Schema
How do I view what each agent is shipping in a multi-agent queue?▼

To view what each agent is shipping in a multi-agent queue, use a read-only dashboard that reads from the fstack brain. It shows shipped items, in-flight work, and claimed version slots across all agents.

What is the best way to track in-flight work and version slots across multiple agents?▼

Tracking in-flight work and version slots across multiple agents requires a read-only dashboard reading from the fstack brain. It provides visibility into team-wide commitments and current bottlenecks without performing mutations.

Can I see what the /ship command would pick next across the team?▼

Yes, you can see what the /ship command would pick next by reading the fstack brain. The dashboard reveals the next ship decision and current commitments for both agents.

Does the multi-agent ship queue dashboard modify any deployment states?▼

No, the multi-agent ship queue dashboard does not modify any deployment states. It is strictly read-only and performs no mutations, ensuring safe visibility into shipped items and in-flight work.

How do I plan handoffs when multiple agents are shipping to the same queue?▼

To plan handoffs when multiple agents are shipping to the same queue, review a read-only dashboard of the fstack brain. It helps you understand bottlenecks, prioritize handoffs, and anticipate the next ship decision.

Why do I need a read-only view for multi-agent ship queue planning?▼

You need a read-only view for multi-agent ship queue planning to safely assess what each agent is shipping and which version slots are claimed. Reading from the fstack brain ensures accurate visibility without risking unintended mutations.