Built by Berry
Official@builtbyberry · United States of America
Built by Berry provides a Marshall-store-backed release lifecycle skill suite covering planning, claiming, building, reviewing, deploying, and administering software releases.
Agent Skills by Built by Berry
Showing 14 vetted skills indexed across 1 GitHub repositories.
release-init
Creates a project and release directly in the shared Marshall store via MCP tools.
release-next
Recommend startable release components ranked by what they unblock from the Marshall store.
release-build
Carries one release component from claim through build, review, and merge against the Marshall store.
release-deploy
Drives release cut-over merges, deploy monitoring, smoke checks, and tagging against the Marshall store.
release-plan
Plans release components through a structured conversation and files them into the Marshall store.
release-admin
Archive, restore, hard-delete, or repair tracker links on Marshall projects, releases, and components.
release-topic
Claims a release component in the Marshall store and creates its topic branch.
release-wrap
Coordinates release wrap-up with change review, CHANGELOG generation, and readiness gating against the Marshall store.
release-graph
Declare blocked-by dependency edges between release components in the Marshall store.
release-unclaim
Releases or force-revokes component claims in the Marshall coordination store.
release-readiness
Runs release readiness lenses and records findings in the shared Marshall store.
change-review
Runs multi-lens reviews over a release component's diff and records findings in the Marshall store.
release-parallel
Dispatch parallel subagent work across release components tracked in the Marshall store.
release-open
Cuts release branches, scaffolds CHANGELOG entries, and opens draft release PRs against the Marshall store.
Frequently Asked Questions About Built by Berry
FAQPage SchemaWhat tasks can I perform with Built by Berry's release skills?▼
You can bootstrap releases in the Marshall store, plan components, declare dependency graphs, claim and build components, run multi-lens change and readiness reviews, deploy or tag releases, dispatch parallel work across components, and archive, restore, or repair release records.
Who are these release management skills designed for?▼
They target software engineers and release managers coordinating multi-component releases who need cross-machine claim locking, structured readiness gating, and resumable deploy steps recorded in a shared Marshall store rather than local state files.
How does a typical release flow run from start to finish?▼
Start with release-init to create the project and release, plan components with release-plan, map dependencies via release-graph, open the release branch and draft PR with release-open, build components through release-build, then wrap and deploy with release-wrap and release-deploy.
What prerequisites or integrations do these skills require?▼
Skills operate against the shared Marshall store as the system of record. Optional integrations include external trackers for issue filing, GitHub milestones for release linking, and GitHub Release plus Packagist publishing for tagged Composer packages in tag mode.
Can multiple components be worked on concurrently?▼
Yes. The release-parallel skill opens a dispatch run for a wave of startable components, takes claims via release-topic with worktrees, and spawns one subagent per component that reports progress back to the run, with release-unclaim available to revoke stuck claims.