ce-ship-releaselisted

Prepare the final human-owned release decision for a verified, reviewed, documented plan range. Derives version and changelog, checks fresh implementation evidence, documentation/doc-audit readiness, rollback, and supply-chain evidence, then writes a decision package on approval. Never tags, pushes, deploys, or claims compliance. Triggers: cut a release, decide a version, draft release notes, or make a release go/no-go decision. /core-engineering:ce-ship-document owns product docs; /core-engineering:ce-doc-audit validates reader workflows.
relusion/vg-sdlc-claude-plugins · ★ 0 · AI & Automation · score 73

Install: claude install-skill relusion/vg-sdlc-claude-plugins

# Ship Release **Invocation input:** $ARGUMENTS Prepare the evidence-backed decision to ship. This is the final workflow after review, verification, required documentation, and any required documentation audit. It decides and records; it never tags, pushes, deploys, or commits. ```text plan → architecture? → spec → implement → {review + verify} → ship-document? → doc-audit? → {refresh review + verify when docs/audit changed state} → ship-release ``` ## Runtime Inputs - Plan slug, resolved through `docs/plans/plans.json`. - Optional explicit `--version` and `--base`. - Current `plan.json`, feature plan, git range/tags, verification report and `verification-summary.json`, in-range `review-summary.json` artifacts, and strict task evidence. - Documentation impact evidence, latest applicable `docs/plans/<slug>/docs/<date>-docs-manifest.md`, and applicable `docs/doc-audits/<date>-<slug>.md`. - Rollback/forward plans and available SBOM, provenance, checksums, signatures, Scorecard, secret-scan, CI, and plugin-validation evidence. Writes: - `docs/plans/<slug>/release/<release-key>-release.md`; - `docs/plans/<slug>/evidence-pack/<release-key>/`; - an appended version section in `CHANGELOG.md` only as part of an approved GO. **Same-day collision rule:** use `<date>` first; if either release artifact or evidence-pack destination exists, use `<date>-2`, then `<date>-3`. Never overwrite or split one release across keys. ## Execution Contract 1. Validate