<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

PM Changelog Curator (Dispatch Skill)

Cross-client dispatch wrapper for the pm-changelog-curator sub-agent. Detects runtime; dispatches to the native sub-agent on Claude Code; reads subagents/pm-changelog-curator.md and executes inline on non-Claude clients.

When to Use

• You are preparing a release and want a CHANGELOG draft from git log between two tags
• You are running on a non-Claude AI client without native pm-changelog-curator sub-agent support
• You want a draft that respects pm-skills CHANGELOG hygiene rules (no internal-notes references, no em-dashes, public paths only) without manually applying them

When NOT to Use

• You want to commit CHANGELOG entries directly (this skill produces a draft for review, not a commit)
• You want to review a PM artifact -> use utility-pm-critic instead
• You want a repo-wide governance audit -> use utility-pm-skill-auditor
• You want a full guided release flow -> use utility-pm-release-conductor (which chains to this skill at gate G2)

Instructions

Runtime detection step. Determine which AI client is invoking this skill.

If you are running in Claude Code with the pm-skills plugin installed

Invoke @agent-pm-changelog-curator with the user's arguments. Pass --since-tag, --target-version, --committed-only from $ARGUMENTS if present. Return the sub-agent's draft to the user.

If you are running in any other AI client

Codex CLI, Cursor, Windsurf, Copilot, Gemini CLI, or any other client without native pm-skills plugin sub-agent support:

1. Read the canonical sub-agent definition at subagents/pm-changelog-curator.md
2. Execute the system prompt body in that file as your operating instructions
3. Run the 8-step drafting flow documented in the sub-agent definition (establish range -> read hygiene rules -> check working tree -> enumerate commits -> classify -> group -> rewrite -> determine target version -> emit draft)
4. Apply --since-tag, --target-version, and --committed-only arguments from $ARGUMENTS
5. Return the layered output per master plan D26 (full CHANGELOG draft + Status Summary + Status YAML)

Cross-Client Notes

The dispatch skill requires the AI client to:

1. Execute Bash for git log, git describe, and git status invocations
2. Read CLAUDE.md hygiene rules and existing CHANGELOG.md format reference
3. Read the canonical sub-agent definition file
4. Treat the agent body as operating instructions

Per master plan D30, dispatch skill availability is CONDITIONAL on Phase 2 GATE B spike outcomes. If any of the above is unreliable on a specific client, that client falls back to manual git log + manual CHANGELOG drafting (which negates most of the dispatch skill's value but at least gives the user the canonical hygiene-rule reference).

Reference Files

• Canonical sub-agent definition: subagents/pm-changelog-curator.md
• Behavioral spec: docs/internal/release-plans/v2.16.0/spec_pm-changelog-curator.md
• CHANGELOG hygiene rules source: CLAUDE.md (repo root)
• Existing CHANGELOG.md format: CHANGELOG.md (root); v2.15.1 + v2.15.2 entries are canonical exemplars
• Runtime components catalog: docs/reference/runtime-components.md
• Output template: references/TEMPLATE.md
• Worked example: references/EXAMPLE.md