feat(plugin): migrate slash commands to the namespaced codingbuddy:* surface

[JeremyDev87]

Background

The Claude Code plugin currently ships bare custom commands from /Users/pjw/workspace/codingbuddy/packages/claude-code-plugin/commands/, including:

• /plan
• /act
• /eval
• /auto
• /checklist
• /buddy

This is increasingly risky because Claude Code already has built-in slash commands and may add more over time. The current plugin surface can collide with built-in commands, bundled skills, or future reserved names. /plan is already the clearest example of a problematic overlap.

Goal

Move the CodingBuddy plugin away from bare top-level custom commands and onto a namespaced command surface:

• /codingbuddy:plan
• /codingbuddy:act
• /codingbuddy:eval
• /codingbuddy:auto
• /codingbuddy:checklist
• /codingbuddy:buddy

The user-facing workflow keywords PLAN, ACT, EVAL, and AUTO should remain available and continue to be the primary shortcut path.

Why this matters

• Prevent collisions with Claude Code built-ins and future reserved commands.
• Make CodingBuddy commands self-describing and easier to discover.
• Reduce ambiguity for users and for documentation.
• Establish a long-term namespace policy so this problem does not return.

Scope

This workstream should cover:

• defining the namespace policy
• moving from bare command delivery to a namespaced plugin-skill-compatible structure
• updating docs and generated README output
• defining the deprecation story for existing bare commands
• adding CI or validation to prevent future collisions

Non-goals

• Removing keyword-based mode entry such as PLAN and EVAL
• Reworking the PLAN/ACT/EVAL product model itself
• TUI changes

Success criteria

• CodingBuddy no longer depends on bare top-level custom slash commands.
• The canonical slash interface is codingbuddy:*.
• Docs, packaging, and tests all reflect the new command surface.
• Future command-name collisions are caught automatically.

Sub-issues

• feat(plugin): define the canonical codingbuddy:* slash-command mapping and namespace policy #1287 Define the canonical codingbuddy:* slash-command mapping and namespace policy
• refactor(plugin): migrate bare slash commands to a namespaced plugin-skill delivery model #1286 Migrate bare slash commands to a namespaced plugin-skill delivery model
• docs(plugin): migrate docs, examples, and generated README to codingbuddy:* commands #1285 Migrate docs, examples, and generated README to codingbuddy:* commands
• feat(plugin): add a compatibility and deprecation path for legacy bare slash commands #1289 Add a compatibility and deprecation path for legacy bare slash commands
• test(plugin): add collision guardrails for reserved slash commands in CI and packaging checks #1288 Add collision guardrails for reserved slash commands in CI and packaging checks

Recommended execution order

1. feat(plugin): define the canonical codingbuddy:* slash-command mapping and namespace policy #1287
2. refactor(plugin): migrate bare slash commands to a namespaced plugin-skill delivery model #1286
3. docs(plugin): migrate docs, examples, and generated README to codingbuddy:* commands #1285
4. feat(plugin): add a compatibility and deprecation path for legacy bare slash commands #1289
5. test(plugin): add collision guardrails for reserved slash commands in CI and packaging checks #1288

[JeremyDev87]

All 5 sub-issues completed and merged:

• feat(plugin): define the canonical codingbuddy:* slash-command mapping and namespace policy #1287 Namespace policy (PR feat(plugin): define canonical codingbuddy:* slash-command mapping (#1287) #1293) ✅
• test(plugin): add collision guardrails for reserved slash commands in CI and packaging checks #1288 Collision guardrails (PR test(plugin): add collision guardrails for reserved slash commands (#1288) #1294) ✅
• refactor(plugin): migrate bare slash commands to a namespaced plugin-skill delivery model #1286 Namespaced delivery model (PR refactor(plugin): migrate bare commands to namespaced plugin-skill delivery model (#1286) #1296) ✅
• feat(plugin): add a compatibility and deprecation path for legacy bare slash commands #1289 Deprecation path (PR feat(plugin): add compatibility and deprecation path for legacy bare commands (#1289) #1295) ✅
• docs(plugin): migrate docs, examples, and generated README to codingbuddy:* commands #1285 Docs migration (PR docs(plugin): migrate command docs to codingbuddy:* namespace (#1285) #1297) ✅

Slash command migration to codingbuddy:* namespace complete.