releaselisted

# Release ## Iron Law `BREAKING CHANGES BUMP MAJOR. AGENTS PREPARE RELEASES; HUMANS MUTATE SHARED ENVIRONMENTS.` ## When to Use - The user explicitly asks for release prep, versioning, changelog work, release notes, tags, publish planning, rollout, rollback, deprecation, or migration notes. - The user approves release prep after a concrete diff exposes release artifacts or rollout obligations: manifests, `CHANGELOG.md`, package locks, plugin/package metadata, CI/CD gates, feature flags, migrations, publish scripts, or rollout plans. - A repo validator requires release artifact sync for an already-approved change. ## When NOT to Use - Starting implementation because a change might later need versioning, changelog, packaging, registry, rollout, or deployment work. Note release risk in `workflow` and ask only at the concrete release-prep decision point. - Triggering deploys, rollbacks, promotions, approvals, production config changes, feature-flag flips, DNS changes, infrastructure applies, or other shared-environment mutations. Prepare the command/checklist for a human. - Internal refactors with no caller-visible impact; use `refactoring`. - Local project bootstrap before release/deployment exists; use `scaffolding`. - Database DDL/data safety itself; pair with `database`. - Service monitoring and alert design; pair with `observability`. ## Core Ideas 1. Release is a late gate. Implementation approval is not release approval. Load this skill o