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.