agentplane-release-and-packaging-operatorlisted

# Agentplane Release And Packaging Operator ## Use This Skill When - A task mentions release, publish, npm, provenance, package version parity, release-ready, or install smoke. - CI fails in package build or release gates. - A public install fails because a workspace package is missing, private, stale, or unpublished. - A release partially completed and you must decide whether to roll forward or stop. ## Core Rule Treat release work as a state machine, not a linear script. Before mutating, identify the current state of git tags, package versions, generated manifests, hosted workflows, and npm visibility. ## Required Preflight 1. Run the normal Agentplane preflight and load release policy when release/version/publish files are in scope. 2. Inspect the release task README and `agentplane task verify-show <task-id>`. 3. Check working tree cleanliness with `git status --short --untracked-files=no`. 4. Inspect recent release incidents: - `agentplane incidents advise --tag release --tag recipes --tag workflow --scope "<release scope>"` 5. Confirm which packages are release participants: - `@agentplaneorg/core` - `@agentplaneorg/recipes` - `agentplane` ## Version And Public Package Checks Use these before publishing and during recovery: ```bash bun run release:parity bun run release:state node scripts/check-npm-version-availability.mjs <version> npm view @agentplaneorg/core@<version> version npm view @agentplaneorg/recipes@<version> version npm view agentplane@<