菜单
Release sprint workflow: version-at-release via tooling, CHANGELOG [Unreleased] flow, release invariant checks, tags, GitHub Releases, RCs. Authoritative law: docs/orchestrator/VERSIONING.md
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | release |
| description | Release sprint workflow: version-at-release via tooling, CHANGELOG [Unreleased] flow, release invariant checks, tags, GitHub Releases, RCs. Authoritative law: docs/orchestrator/VERSIONING.md |
Authoritative law:
docs/orchestrator/VERSIONING.md(ADR-004). This skill is the operational cheat sheet. The pre-v8.5 "Version-First" rule (bump before work) is retired.
plans/vX.Y.Z/PLAN.md + sprint files ← what ships (target version = working label)
CHANGELOG.md [Unreleased] ← accumulates one entry per sprint (writer: @scribe)
VERSION ← single source of truth, written ONCE per release
scripts/version-bump.js <type> ← bump + [Unreleased] promotion + full touchpoint sync
scripts/sync-version.js --check ← all ~12 touchpoint files consistent?
scripts/release-check.js ← VERSION == CHANGELOG == tag == release?
release/vX.Y.Z → PR → merge commit ← CI: release-consistency.yml
.github/workflows/release-tag.yml ← annotated tag + DRAFT GitHub Release
VERSION, do NOT create dated CHANGELOG headings.## [Unreleased] (serialized).Version Relevance (none/patch/minor/major) in its sprint file.done; working tree clean; [Unreleased] non-emptynode scripts/release-check.js — resolve inherited drift (phantom releases) FIRSTVersion Relevance (semver table in VERSIONING.md)node scripts/version-bump.js <type> (use --dry-run first)npm run version:check green, npm run release:check green (on release/* branch)releasedvX.Y.Z-rc.N (annotated) + GitHub Release with the pre-release flag.release-check.js flags it.Ultracode / Max-Parallel mode — dynamic workflows fan work out across tens–hundreds of adversarially-verified parallel subagents for large, decomposable jobs (codebase-wide audits, big migrations, cross-checked research). Opt-in; higher token spend.
Smart Routing — the DEFAULT CC_GodMode routing policy. Risk-based, minimal-agent paths that preserve required safety gates for the changed scope.
Plan-first orchestration (ADR-004): comprehensive PLAN.md, sprint files with write-scope ownership, preflight checks, serialized integration, and the release sprint. Use for any non-trivial or multi-part request BEFORE dispatching agents.
Expanded department-based orchestration for large cross-domain CC_GodMode work. Freezes ownership, handoffs, and write scopes before implementation.
Bootstrap repo-local governance before CC_GodMode workflows run in an empty, newly initialized, or undocumented workspace. Use proactively when a project has no CLAUDE.md, no README, or no clear structure yet.
Meta-decision logic that adapts workflows based on task analysis — security overrides, breaking change escalation, performance paths, emergency hotfix, and documentation optimization