菜单
Release strategy for the Principled framework. Consult when working with changelogs, release readiness checks, version bumps, release plans, or tag operations. Covers changelog format conventions, semver bump heuristics, pipeline reference resolution, and the release lifecycle.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | release-strategy |
| description | Release strategy for the Principled framework. Consult when working with changelogs, release readiness checks, version bumps, release plans, or tag operations. Covers changelog format conventions, semver bump heuristics, pipeline reference resolution, and the release lifecycle. |
| user-invocable | false |
This skill provides Claude Code with comprehensive knowledge of how the Principled methodology extends to the release boundary. It is not directly invocable --- it informs Claude's behavior when release-related context is encountered.
Activate this knowledge when:
Read these files for detailed guidance on specific topics:
reference/release-conventions.md --- Changelog format adapted from Keep a Changelog, entry grouping categories (Features, Improvements, Decisions, Fixes, Uncategorized), pipeline reference patterns for commit-to-spec mapping, and the distinction between changelogs and release notes.reference/semver-rules.md --- Version bump heuristics (supersedes signals major, new RFCs signal minor, plan tasks signal patch), priority rules when multiple signals are present, --type override behavior, version manifest file detection across ecosystems, and module detection via CLAUDE.md./release-ready checks that all referenced pipeline documents are in terminal status before a release proceeds.Validate that a pull request follows principled conventions: references a plan or proposal, has correct labels, includes required sections in the description, and links to relevant documents. Use in CI or before merging to enforce PR quality.
Generate a structured pull request description from a DDD plan task. Reads the plan, task manifest, and implementation branch to produce a PR body with references to the originating proposal, plan, ADRs, and related tasks. Use when opening a PR for plan-driven work.
Process open GitHub issues through the principled pipeline. Lists untriaged issues, normalizes their metadata, ingests them into the documentation pipeline, and reports a summary. Operates as the batch entry point — delegates to /ingest-issue for each individual issue.
Implementation orchestration strategy for the Principled framework. Consult when working with DDD plan execution, git worktrees for task isolation, task manifests, or the decompose-spawn-validate-merge lifecycle. Covers worktree management, sub-agent patterns, task state machines, and manifest schema.
Top-level orchestrator for DDD plan execution. Decomposes a plan into tasks, iterates through phases respecting dependencies, spawns worktree-isolated agents, validates implementations, and merges results. Runs inline to coordinate multiple sub-agent spawns. Use for automated end-to-end plan execution.
Audit ADR coverage across modules. Identifies modules with no architectural governance, orphaned ADRs referencing removed modules, and stale architecture docs. Classifies findings by severity.