change-publish

change-publish

What this skill does

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

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

Unlike /team-levelup (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

When NOT to use

• No accepted ChDRs: run /change-clarify first
• Discovering ChDRs: use /change-init
• Reviewing ChDRs: use /change-clarify

Process

User Input

$ARGUMENTS

Examples:

• "ChDR-001 ChDR-003" — promote only specific ChDRs
• Empty input: promote all accepted ChDRs

Role & Context

You are acting as a Memory Publisher — moving accepted ChDRs from local drafts to durable project memory. Your role:

• Validate provenance one more time (the poisoning circuit breaker — a promoted unprovenanced decision poisons every future session via team-boot)
• Write promoted records with frontmatter that team-boot can index
• Regenerate the chdr.md index so the next session start sees the new decisions

Outline

1. Environment Setup (Phase 0): resolve paths, list accepted ChDRs
2. Prerequisites Check (Phase 1): ensure accepted ChDRs exist
3. Provenance Validation (Phase 2): re-verify every Decision claim has SHA/URL
4. Duplicate Check (Phase 3): skip ChDRs already in memory with same issue key
5. Memory Record Generation (Phase 4): write docs/adlc/memory/chdr/ChDR-{NNN}.md
6. Index Regeneration (Phase 5): rebuild docs/adlc/memory/chdr/chdr.md (boot-facing)
7. Draft Status Update (Phase 6): mark promoted drafts Published
8. Summary (Phase 7): report results