release-readiness
Use when preparing to tag or cut a release of a WordPress plugin (or any repo that carries its version in readme.txt "Stable tag" and tags releases as bare semver). Triggers on "is this ready to tag", "prep the release", "release readiness", "get the release ready", "release preflight", "what's left before we ship X.Y.Z", or any moment just before a release tag. Audits everything merged since the last git tag, surfaces the gaps (undocumented features, missing changelog entries, dirty working tree, stale branches/worktrees, open PRs, version not bumped, failing tests), then — after one approval — closes the in-repo gaps it can (drafts the changelog, bumps the version, dispatches the repo's docs/verification agents, runs the suite behind a safety guard) and stops at a green "ready to tag" state. It NEVER pushes, tags, or publishes anything: every action that leaves the repo stays the human's decision.
Why it exists
Tags shipped without Stable tag alignment. This is the preflight.
History
1.0.0
Bare semver tag convention for VGP plugins.
How Jack actually uses it
Before any release tag on plugin repos.
What it is not
Not a generic tutorial. It's the house runbook for this machine and these agents.
Related
Package
Version 1.0.0
· install pin efd09da
· SSOT skills/release-readiness/ on GitHub
· agents: claude-code