dom-release-notes-for-humans · git:20261104.42ab9cf · 2026-11-04 · sha256 81bfc382159f0e7a
dom-release-notes-for-humans git:20261104.42ab9cfA
Immutable. This exact content never changes and is served at /api/v1/blob/81bfc382159f0e7a.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_gocfgb5mey6srxjm/81bfc382159f0e7a39a4ff6c5f7ffe185cd5b7acc0dcd595ed72583ca86a29bb.json
Then /plugin install dom-release-notes-for-humans@markdownregistry-gocfgb5mey6srxjm in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
---
name: dom-release-notes-for-humans
description: |-
Use whenever `release-notes-for-humans` applies.
metadata:
internal: true
---
# Release Notes
## Public Workflow
For every invocation, load `release-notes-for-humans` and follow its complete workflow. This overlay adds scope and delivery defaults, bullet rendering, and package links below. Apply the global **Explicit user direction** policy to task-scoped overrides of this overlay’s procedure and presentation conventions.
## Workflow Defaults
Apply these defaults and constraints within the base workflow:
1. When the base workflow needs a default evidence scope, use the current repository and local `HEAD` as the target, including commits that haven’t been pushed to a remote. Exclude uncommitted changes unless explicitly requested.
2. Apply the [presentation conventions](#presentation-conventions).
3. When drafting or editing without a file target, default to ready-to-paste changelog Markdown. Present approval proposals and questions, decisions requiring review, required disclosures, and material evidence limitations separately from the changelog Markdown. Omit other commentary. Use the base workflow’s delivery for file edits and read-only reviews. Drafting alone doesn’t authorize file changes or submission.
## Presentation Conventions
- In release note prose outside headings, apply the [package link map](references/package-links.md) to package names.
- Use `*` for every unordered release note bullet. If a generic Markdown formatter’s only disagreement is normalizing this marker to `-`, preserve `*` and don’t treat the marker-only result as a release note failure.