release-readiness

Runs release readiness lenses and records findings in the shared Marshall store.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Release readiness reviews often live in repo-local state files that only one person or machine can see, making it hard for teams and agents to share a single view of whether a release is safe to ship. This Skill runs the configured readiness lenses against a release and records findings in the hosted Marshall store so results are visible across machines, people, and agents. ## Core Features & Use Cases - Lens-based readiness review: Loads the lens selection from the store, pre-filters lenses against the changed files with lenses_applicable, and fans out one subagent per applicable lens. - Durable shared findings: Records findings atomically via record_findings as store rows of kind readiness, and supports defer, accept, fix, and re-open through resolve_findings. - Reconciliation and verdicts: Reconciles fresh findings against existing open, deferred, accepted, or fixed findings to avoid duplicates, then reports a ship, ship-with-followups, or hold verdict. - Use Case: Before tagging a release, ask for a readiness review; the Skill inspects the commit log, diff, and changelog, runs migration-safety and deploy lenses, and records any blockers in the shared store for the whole team. ## Quick Start Ask the agent to run a release readiness review for the current Marshall-tracked release and report whether it is ready to ship.

Frequently Asked Questions about release-readiness

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

FAQPage Schema
How do I run a release readiness review with Marshall?

Ask for a readiness review of a Marshall-tracked release or invoke /marshall:release-readiness. The Skill resolves the release, loads the lens selection from the store, pre-filters lenses against the changed files, runs one subagent per applicable lens, and records findings in the shared store.

How are readiness findings stored and shared across a team?

Findings are written to the hosted Marshall store as rows of kind readiness via record_findings, not to a local review-state.json file. Because the store is shared, a review one person or agent runs is visible to everyone working the release.

What verdicts does a release readiness review produce?

The review reports ship, ship-with-followups, or hold. This vocabulary is deliberately distinct from change review's approve and changes-required verdicts, since readiness decides whether a release ships rather than whether a component is approved.

What happens if no readiness lenses are configured for a release?

The review stops immediately when project.reviews.readiness.lenses is empty, since reviewing with an empty lens set is not allowed. Lenses must first be selected with the set_release_lenses store tool.

How does the skill avoid duplicate findings across review runs?

Each fresh finding is reconciled against existing store findings: matches to open or deferred findings are surfaced as already-tracked, matches to accepted or fixed findings are suppressed unless the issue regressed, and only new findings are recorded in one batched record_findings call.