skills.rest
builtbyberry
builtbyberryOFFICIAL
Explore all skills by this author →
WebsiteGitHub

release-graph

Declare blocked-by dependency edges between release components in the Marshall store.

Updated Jul 15, 2026
Search Tags:#release management#mcp#dependency graph#release coordination#blocked-by#marshall#startability
One-click install
npx skills add https://github.com/builtbyberry/marshall-claude-plugin --skill release-graph-builtbyberry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-graph
Source: https://github.com/builtbyberry/marshall-claude-plugin/tree/main/marshall/skills/release-graph
Command: npx skills add https://github.com/builtbyberry/marshall-claude-plugin --skill release-graph-builtbyberry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Release components sit at the store's fail-safe unverified default until their dependency graph is declared, so nothing is startable. This Skill maps the blocked-by relationships between a release's components and writes them to the shared Marshall store, turning the graph on. ## Core Features & Use Cases - Dependency Mapping: Derive blocked-by edges from issue bodies, acceptance criteria, and "depends on" references, then confirm them with the user before writing. - Graph Verification: Write edges via the Marshall MCP set_release_graph tool, which validates the graph and rejects self-edges, cross-release edges, and cycles. - Startability Reporting: Report which components are now startable (roots) versus blocked after the graph is set. - Use Case: After opening a release with several components, run this Skill to declare that the API migration blocks the frontend rollout, so the store knows which work can start immediately. ## Quick Start Ask the assistant to map the dependencies for release 1.4.0 and write the graph to the Marshall store.

Frequently Asked Questions about release-graph

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

FAQPage Schema
How do I declare dependencies between release components in Marshall?▼

Load the release's components with the release_get MCP tool, derive blocked-by edges from issue bodies and acceptance criteria, confirm them with the user, then call set_release_graph with the release and edges using component ULIDs.

Why is nothing startable in my Marshall release?▼

Components sit at the store's fail-safe unverified default until the dependency graph is declared. Running the release-graph flow writes the edges and marks every component known, which makes root components startable.

What happens if the release dependency graph has a cycle?▼

The Marshall store rejects the write with an invalid_graph error and writes nothing. A cycle is a planning error, so fix the edges with the user rather than forcing the graph through.

Can I set an empty dependency graph for a release?▼

Yes. Pass an empty edges array to set_release_graph for a release whose components have no inter-dependencies. This still verifies the graph and marks the components known.

Does the Marshall CLI support writing the release graph?▼

No. The marshall CLI is read-only for the graph today. Use the Marshall MCP tools release_get and set_release_graph, which the plugin connects over OAuth.

Related Skills

Explore More Software Engineering Skills→
UKGovernmentBEISUKGovernmentBEIS
657

prepare-release

Prepares an inspect_evals release by collecting changelog fragments and opening a draft PR.

Official
Intermediate
LaPaGaYoLaPaGaYo

deploy

Automate end-to-end deployment workflows with health checks and release gating.

Community
Advanced
charly-vibescharly-vibes

create-issues

Convert markdown implementation plans into linked issues with dependencies.

Community
Intermediate
CruxExpertsCruxExperts
3

ls-keepass-secrets

Fetch and rotate KeePass secrets using repo-local mappings without writing values to tracked files.

Community
Advanced