release-next

Recommend startable release components ranked by what they unblock from the Marshall store.

Updated Jul 15, 2026
One-click install
npx skills add https://github.com/builtbyberry/marshall-claude-plugin --skill release-next-builtbyberry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-next
Source: https://github.com/builtbyberry/marshall-claude-plugin/tree/main/marshall/skills/release-next
Command: npx skills add https://github.com/builtbyberry/marshall-claude-plugin --skill release-next-builtbyberry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple releases are in flight, it is hard to know which component to work on next without manually inspecting dependency graphs and checking who has claimed what. This Skill answers "what should I work on?" by querying the shared Marshall store for server-computed startability across one release, one project, or the whole workspace. ## Core Features & Use Cases - Cross-release startability scan: Query startable components across every unshipped release in the workspace, scoped by release, project, or nothing at all. - Ranked recommendations: Results are ranked by how many components each item unblocks, with per-release breakdowns of what is blocked and why. - Read-only by design: It never claims, heartbeats, or releases work — claiming is a deliberate next step via claim_component or /marshall:release-topic. - Use Case: A developer finishes a task and asks "what should I work on next?" The Skill calls release_next with no scope, returns the top 1–3 startable components across all unshipped releases, and explains what each one unblocks. ## Quick Start Ask the assistant what release work is startable right now, optionally naming a release version or project to narrow the scope.

Frequently Asked Questions about release-next

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

FAQPage Schema
How do I find the next startable release work?

Ask what you should work on next, optionally naming a release version or project. The Skill calls the release_next MCP tool, which ranks startable components by how many other components each one unblocks, and returns the top 1–3 recommendations.

Can I check startable work across multiple releases at once?

Yes, calling release_next with no scope scans every unshipped release in the workspace. You can also scope by project to see its unshipped releases, or name a single release for a focused answer.

What happens if the Marshall MCP server is not connected?

The Skill falls back to the marshall CLI with marshall next --release <version> --json. That path is per-release only with no cross-release scan, so you must specify which release to query.

Why does release_next return nothing startable?

An empty startable list means everything is blocked or claimed. Read the per-release blocked_summary to see which release is stuck and why, such as unverified graphs or unmet dependencies, rather than relaxing the server's verdict.

How do I fix a release_ambiguous error?

The error means the key matched more than one release. Retry with project set to one of the candidate projects and release set to its slug, since that pair is unique. Never retry with the same bare key.

Does release-next claim or start the work it recommends?

No, it is strictly read-only and never claims, heartbeats, or releases components. To begin work, claim the component with claim_component or use /marshall:release-topic as a deliberate next step.