메뉴
End-to-end release orchestration for SkillMeat. Routes five intents (version bump, regen openapi, regen SDK, audit coverage, rollover changelog) to the single linear release-orchestration workflow. Use when running /release:bump or coordinating a tagged release.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Cross-feature visibility layer for implementation plans, PRDs, and progress files. Use when: checking what's in progress, auditing stale plan statuses, remediating mismatches between frontmatter and task reality, summarizing active work, investigating orphaned/superseded PRDs. Complements artifact-tracking (which handles per-phase task updates). Routes intent to scripts/plan-status-report.py and artifact-tracking scripts.
Create rich, evidence-backed, theme-aware HTML delivery reports. One skill, four routes: `feature` (a completed feature, backward-looking — what did we deliver and how do we know), and `program` / `phase` / `readiness` (work in flight, forward-looking — where are we, what's blocked, and the next concrete action on each open item). Forward-route items each carry domain tags and a copyable agent handoff (command, existence-checked paths, grep-verified requirement IDs, blocking gates, tracker node, and a paste-ready prompt) — including for deferrals and externally blocked work. Use for: feature completion showcase, project/program status, phase or wave recap, go/no-go readiness review, stakeholder-friendly explanation of delivered value or current state. Triggers: "feature report", "completion showcase", "project status", "where are we", "program status", "status report", "phase report", "wave recap", "readiness review", "go/no-go". Do NOT use for: generic markup-to-HTML capsules (use html-capsules), live dashbo
Token-efficient tracking for AI orchestration. CLI-first for status updates (~50 tokens), agent fallback for complex ops (~1KB). Use when: updating task status, querying blockers, creating progress files, validating phases.
Unified execution engine for all development workflows. Progressive disclosure for phase execution, quick features, story completion, and scaffolding. Integrates with artifact-tracking and meatycapture-capture. Use when running /dev:execute-phase, /dev:quick-feature, /dev:implement-story, /dev:complete-user-story, or /dev:create-feature commands.
Generate and optimize PRDs, Implementation Plans, and Progress Tracking documents optimized as AI artifacts for development agents. Use when creating new feature plans, breaking down long planning docs (>800 lines), or setting up progress tracking. Supports: 1) Create PRD from feature request, 2) Create Implementation Plan from PRD with phase breakdown and subagent assignments, 3) Optimize existing plans by breaking into phase-specific files, 4) Create progress tracking with task assignments. Example: "Create a PRD for user authentication feature" or "Break down the sidebar-polish implementation plan into phase files" or "Create progress tracking for data-layer-fixes PRD".
Use this skill when authoring, modifying, or validating SkillMeat Dynamic Workflow scripts (.claude/workflows/*.js). Covers the full governed procedure: loading the master contract and per-workflow spec, choosing patterns from the pattern library, generating scripts against ExecutionGraph/ExecutionReport schemas, validating against the four-constraints checklist (no FS/shell in script, Mode D as boundary, edit-less reviewers, no Date.now/Math.random), syntax-check recipe (async-IIFE wrap for node --check), dry-run guidance, saving to .claude/workflows/, and registering in workflow-registry.md. Use whenever creating a new workflow, extending an existing one, or reviewing a workflow script for compliance.
| name | release |
| description | End-to-end release orchestration for SkillMeat. Routes five intents (version bump, regen openapi, regen SDK, audit coverage, rollover changelog) to the single linear release-orchestration workflow. Use when running /release:bump or coordinating a tagged release. |
| version | 1.1 |
| updated | "2026-04-27T00:00:00.000Z" |
| spec | ./SPEC.md |
Orchestration guidance for executing a complete, validated SkillMeat release — from version bump through git tag and GitHub release creation.
Load this skill when:
/release:bumpAlways co-load with changelog-sync when invoked via /release:bump (required pair per CLAUDE.md Command-Skill Bindings).
| Intent | Workflow Section | Canonical Spec |
|---|---|---|
| Bump the project version to a new semver | workflows/release-orchestration.md §Step 1: Version Bump | .claude/specs/version-bump-spec.md |
Regenerate openapi.json from the live app | workflows/release-orchestration.md §Step 2: Regen OpenAPI | skillmeat/api/CLAUDE.md §Endpoint Inventory Maintenance |
Regenerate SDK client from openapi.json | workflows/release-orchestration.md §Step 3: Regen SDK | .claude/specs/version-bump-spec.md §3. OpenAPI Spec + Generated SDK |
| Audit CHANGELOG coverage before tagging | workflows/release-orchestration.md §Step 4: Audit Gate | .claude/specs/changelog-spec.md |
Roll over [Unreleased] to versioned section | workflows/release-orchestration.md §Step 5: Rollover Changelog | .claude/specs/changelog-spec.md, .claude/specs/version-bump-spec.md §CHANGELOG Roll-Forward |
| Check skill alignment with new version | workflows/release-orchestration.md §Step 10: Skill Alignment | .claude/specs/version-bump-spec.md §6. Skill SPEC.md alignment |
| Commit, tag, and create GitHub release | workflows/release-orchestration.md §Step 7–9: Commit, Tag, Release | .claude/specs/version-bump-spec.md §Git Tagging |
For a full release, read workflows/release-orchestration.md and follow the steps in order. The workflow is a single linear flow — steps are not optional and cannot be reordered.
Dry-run (non-destructive preview through Step 5):
# Dry-run everything up to and including changelog rollover
python .claude/skills/release/scripts/rollover-changelog.py \
--version X.Y.Z --date YYYY-MM-DD --dry-run
Steps 7–9 (commit, tag, release) are always destructive; confirm with the operator before executing.
audit-coverage.py must exit zero before a tag is created. If it exits non-zero:
[Unreleased] to cover the flagged commits, then re-run.The --force flag bypasses the audit gate. Agents must never pass --force without an explicit human instruction in the current conversation. When a human operator passes --force, the workflow must print a visible warning and ask for confirmation before continuing. See workflows/release-orchestration.md §Force-Bypass Protocol.
audit-coverage.py exit zero is a hard prerequisite.version-bump-spec.md is the authoritative list of bump targets — do not add targets here.rollover-changelog.py) must complete before git tag is created.Full invariant set: SPEC.md §3. Invariants & Constraints
A commit-msg hook warns (but never blocks) when a user-facing commit is made without a corresponding [Unreleased] CHANGELOG entry.
# Run from the repository root
ln -s ../../.claude/hooks/check-changelog-entry.sh .git/hooks/commit-msg
The symlink is relative so it survives directory renames. Uninstall by removing .git/hooks/commit-msg.
chore, refactor, test, docs, ci, build, style, merge commits, version bumps).CHANGELOG.md is staged with an [Unreleased] diff line.[Unreleased] update is staged, prints a warning to stderr and exits 0.SKILLMEAT_SKIP_CHANGELOG_CHECK=1 git commit ...
| File | Purpose |
|---|---|
.claude/hooks/check-changelog-entry.sh | Shell wrapper (symlink target) |
.claude/hooks/check-changelog-entry.py | Python helper with detection logic |
tests/unit/skills/test_check_changelog_entry.py | Test suite (36 cases) |
Full specification: .claude/specs/changelog-spec.md §Pre-commit Hook
./workflows/release-orchestration.md./SPEC.md.claude/specs/version-bump-spec.md.claude/specs/changelog-spec.md.claude/skills/release/scripts/audit-coverage.py.claude/skills/release/scripts/rollover-changelog.py