builtbyberry

Wrap a release against the Marshall store — deploy mode (hand off ready-for-deploy) or tag mode (hand off ready-to-ship for a tagged Composer package): run change-review + readiness (findings land in the store), fill the CHANGELOG, gate on unresolved high findings. Use when the user says /release-wrap, finish the release, we're ready to close out <release>, or all components are merged, what now.

Run a multi-lens change review over a release component's diff and record the findings in the shared Marshall store (not a local review-state file). Loads the configured change lenses, runs them against the component's diff, and writes findings (kind: change) via record_finding; supports defer/accept/fix/re-open via resolve_finding. Use when the user says /marshall:change-review, review this component, change review, or attaches a component diff/PR/branch for a Marshall-tracked release.

Archive, restore, or permanently delete a Marshall project, release, or component — the lifecycle verbs you reach for when a record was mis-created, abandoned, or has simply gone quiet. Use when the user says /marshall:release-admin, archive <release>, hide this project, restore the archived component, un-archive, delete this empty release, or clean up the release list.

Drive the final cut-over of a release against the shared Marshall store — deploy mode (merge the release PR, watch the deploy, smoke-check production, monitor the window, via set_deploy_step) or tag mode (merge, date, tag, GitHub Release, Packagist, via set_ship_step) — recording every step on the store's record so it is resumable across sessions and machines. Use when the user says /release-deploy, deploy the release, ship <release>, tag the release, or cut over to prod.

Bootstrap a project and release directly in the shared Marshall store — born-in-the-store, no GitHub round-trip. Resolve-or-create the workspace project, create the release (theme, version-or-slug, out_of_scope), and offer an optional external-tracker link. Use when the user says /release-init, bootstrap a release in the store, create a project and release in Marshall, start a release from scratch, or init a release without a GitHub milestone.

Recommend the next startable release work from the Marshall store — across every release in flight, or within one. Use when the user says /release-next, what is next, what should I work on, or I have a time budget.

Dispatch parallel work across a release's startable components against the shared Marshall store: open a dispatch_run for the wave, then for each member let /marshall:release-topic --worktree take the claim and materialize a worktree, and spawn one Claude subagent each that reports progress back to the run. Use when the user says /release-parallel, work on these in parallel, dispatch parallel work, start wave <n>, or run several components concurrently.

Plan a release straight into the shared Marshall store: run the structured planning conversation (theme → component sweep → deploy-safety → out-of-scope) and write each confirmed component via component_create — no GitHub issues, no release-plan.json. Use when the user says /marshall:release-plan, plan v<X.Y.Z>, plan the next release, scope <release>, or add a component to <release>.

Recommend the next startable release work from the Swarm Release Manager store — across every release in flight, or within one. Use when the user says /release-next, what is next, what should I work on, or I have a time budget.

Plan a release straight into the shared SRM store: run the structured planning conversation (theme → component sweep → deploy-safety → out-of-scope) and write each confirmed component via component_create — no GitHub issues, no release-plan.json. Use when the user says /srm:release-plan, plan v<X.Y.Z>, plan the next release, scope <release>, or add a component to <release>.

Open a release session against the shared SRM store: confirm the release is seeded, cut the release branch, scaffold the CHANGELOG, open the draft release PR, and optionally (on a yes) link a GitHub milestone. Use when the user says /release-open, start release, cut release branch, or let's start <release>.

Bootstrap a project and release directly in the shared SRM store — born-in-the-store, no GitHub round-trip. Resolve-or-create the workspace project, create the release (theme, version-or-slug, out_of_scope), and offer an optional external-tracker link. Use when the user says /release-init, bootstrap a release in the store, create a project and release in SRM, start a release from scratch, or init a release without a GitHub milestone.

Dispatch parallel work across a release's startable components against the shared SRM store: open a dispatch_run for the wave, then for each member let /srm:release-topic --worktree take the claim and materialize a worktree, and spawn one Claude subagent each that reports progress back to the run. Use when the user says /release-parallel, work on these in parallel, dispatch parallel work, start wave <n>, or run several components concurrently.

Drive the deploy step of a release against the shared SRM store: merge the release PR, watch the deploy, smoke-check production, monitor the window — recording every step on the store's Deploy record so it is resumable across sessions and machines. Use when the user says /release-deploy, deploy the release, ship <release>, or cut over to prod. Deploy-mode only.

Wrap a release against the SRM store: run change-review + readiness (findings land in the store), fill the CHANGELOG, gate on unresolved high findings, and hand off ready-for-deploy. Use when the user says /release-wrap, finish the release, we're ready to close out <release>, or all components are merged, what now. Deploy-mode only.

Run a multi-lens change review over a release component's diff and record the findings in the shared SRM store (not a local review-state file). Loads the configured change lenses, runs them against the component's diff, and writes findings (kind: change) via record_finding; supports defer/accept/fix/re-open via resolve_finding. Use when the user says /srm:change-review, review this component, change review, or attaches a component diff/PR/branch for an SRM-tracked release.

Checkpoint the current conversation back to its Swarm channel. Use ONLY when the user explicitly asks to checkpoint, share, or save their work to Swarm — never invoke automatically, because sharing is gated on the channel's capture mode and the user's intent.

Use when working in a project connected to Swarm, a shared context bus over MCP. At the start of a task, load shared context with get_context_for_injection; at meaningful checkpoints, share back per the channel's capture mode. Triggers whenever the Swarm MCP tools (get_context_for_injection, capture_context, share_session, list_channels) are available.

Set up a new project on Swarm — create its channel and seed it with intelligence records. Use when connecting a repository to Swarm for the first time, or when the user asks to onboard, initialize, or set up a project on Swarm.

Turn working context into durable channel canon — promote or create records, link them, and supersede replaced ones. Use when the user asks to curate, record, promote, or save findings as Swarm records, or to relate or supersede existing records.

Load shared Swarm context for the active channel. Use at the start of a task in a Swarm-connected project, or whenever the user asks to load or refresh Swarm context.

Work the produce-loop on a Swarm Project. Use when the user asks you to work on their Swarm project, address or review the change requests (recommendations) on a Swarm Project, or produce the changes a human has recommended — you author the edits to the Project's Artifacts and open a review gate for a human to approve. Scoped to a Swarm Project (channel + slug), not any local project folder.

Hand off curated context to another person or agent with a Swarm handoff bundle. Use when the user asks to hand off, transfer, or package context for a teammate or successor, or to inspect or acknowledge a handoff bundle.

Checkpoint the current conversation back to its Swarm channel. Use ONLY when the user explicitly asks to checkpoint, share, or save their work to Swarm — never invoke automatically, because sharing is gated on the channel's capture mode and the user's intent.

Execute a Swarm dispatch run end to end. Use when the user hands you a dispatch outbound bundle id, or asks you to run, pick up, or carry out a Swarm dispatch — you perform the scoped task off the main thread and return a proposal bundle for the operator to confirm.

Build and work with Laravel Swarm (builtbyberry/laravel-swarm) — author single-agent, inline, and class-based swarms; pick topologies and execution modes; keep runs governed; and test the audit trail. Use when creating or editing swarm classes/agents, running agents through the governed pipeline, or writing swarm tests.