• Review Findings

-   Critical: wrapper deletion now crosses a sub-agent invariant. The plan deletes every non-workflow-\* command, including /pm-critic, /pm-audit-repo, /pm-draft-changelog, and /pm-release (docs/internal/ release-plans/v2.22.0/implementation-plan.md:37). But the repo still says every sub-agent has a companion command in agents/\_pairing.yaml and multiple public docs (agents/\_pairing.yaml:3, docs/ reference/runtime-components.md:53). If D2 is locked to retire them, the execution scope must explicitly retire the companion-command model too.

-   High: /pm-release has a safety contradiction. Your new D2 text says the retired commands are also reachable as @agent-pm-\* (docs/internal/release-plans/v2.22.0/plan_v2.22.0.md:54), but pm-release- conductor explicitly says it has no direct \@-mention path because release is too consequential (agents/pm-release-conductor.md:158). Safer wording: /pm-skills:utility-pm-release-conductor is the explicit user path; that skill may dispatch internally to the native sub-agent.

-   High: argument handling is still load-bearing. Current official Claude Code docs I pulled via Context7 document \$ARGUMENTS for command files, not clearly for SKILL.md. Several dispatch skills reference \$ARGUMENTS directly (skills/utility-pm-skill-auditor/SKILL.md:37, skills/utility-pm- changelog-curator/SKILL.md:37). The live gate should test all four utility dispatch skills with trailing arguments, especially /pm-skills:utility-pm-release-conductor v2.22.0 --dry-run.

-   Medium: “docs unchanged” is overstated. Release notes say skill pages are unchanged (docs/releases/ Release_v2.22.0.md:27), but the implementation correctly requires regenerating docs/skills/\* with new Try-it / How-to-Use invocation snippets (docs/internal/release-plans/v2.22.0/implementation- plan.md:30). Frame it as: skill content/templates/examples unchanged; generated invocation snippets change.

-   Medium: session log continuation is stale. It still says local-only, NOT pushed, and D2/D4 open. Current remote origin/release/v2.22.0 is at b0ef7ef, same as HEAD. Also, your workspace now has an uncommitted edit to plan_v2.22.0.md locking D2/D4; I did not make it.

Recommended Design

Use the 10-command path only if you explicitly retire the sub-agent companion-command contract. That means the execution plan must add these surfaces to the required sweep: agents/\_pairing.yaml, agents/ \*.md invocation sections, docs/reference/runtime-components.md, docs/guides/using-sub-agents.md, docs/concepts/sub-agents.md, docs/concepts/active-orchestration.md, docs/contributing/authoring-sub- agents.md, docs/contributing/release-runbook.md, docs/reference/sub-agent-compatibility.md, README.md, and AGENTS.md.

The safer execution sequence:

1.  Update the plan/continuation facts: pushed state, D2/D4 resolved, no direct @agent-pm-release- conductor user path.

2.  Run the live gate before deletion: direct skill invocation with trailing args for one content skill plus all four utility dispatch skills.

3.  Update CI/generators: validate-commands for 10 workflows, manifest validator, version validator, generate-skill-pages.py, and commands.md wording for “10 workflow commands” rather than “0 skill commands plus 10 workflow commands.”

4.  Delete wrappers and retire sub-agent companion-command docs/invariants in the same commit.

5.  Regenerate docs, sweep public short-command references, then run pre-tag validation and Astro build.

Continuation Prompt Fix

The next prompt should say: current branch is release/v2.22.0 at b0ef7ef, already on origin; D2/D4 are resolved; do not revive the rename; do not advertise direct @agent-pm-release-conductor; and the first live gate must prove direct skill invocation passes trailing args to the four utility dispatch skills before deleting commands.
