change-publish

What this skill does

Compile accepted ChDRs into the project's memory layer at {REPO_ROOT}/.adlc/memory/chdr/:

• Validate accepted ChDRs (status + provenance on Decision claims)
• Write each promoted ChDR to .adlc/memory/chdr/ChDR-{NNN}.md with OKF-style frontmatter
• Regenerate {REPO_ROOT}/.adlc/memory/chdr.md — the boot-facing index that team-boot injects into the session-start context (same convention as pdr.md/adr.md)
• Mark source drafts ### Status: **Published**

Unlike /levelup-publish (which opens a PR against team-ai-directives), change-publish writes project-local memory — ChDRs describe this repo's evolution and fail the team-wide signal gate. No PR is created; the user commits via their normal flow.

This skill does not run until ChDRs have been accepted via /change-clarify.

When to use

• After /change-clarify: accepted ChDRs need promotion to memory
• After re-running /change-init: new accepted ChDRs to add to the memory index