|
| 1 | +# CodingBuddy Namespace Policy |
| 2 | + |
| 3 | +## Policy Statement |
| 4 | + |
| 5 | +CodingBuddy does **NOT** ship new bare top-level slash commands. All future commands use the `codingbuddy:*` namespace. Existing bare commands will be migrated to namespaced equivalents. |
| 6 | + |
| 7 | +This policy prevents collisions with Claude Code built-in commands and clearly identifies CodingBuddy-owned functionality. |
| 8 | + |
| 9 | +## Canonical Command Mapping |
| 10 | + |
| 11 | +| Legacy (bare) | Namespaced | Status | |
| 12 | +| ------------- | ----------------------- | ---------------- | |
| 13 | +| `/plan` | `/codingbuddy:plan` | migration target | |
| 14 | +| `/act` | `/codingbuddy:act` | migration target | |
| 15 | +| `/eval` | `/codingbuddy:eval` | migration target | |
| 16 | +| `/auto` | `/codingbuddy:auto` | migration target | |
| 17 | +| `/buddy` | `/codingbuddy:buddy` | migration target | |
| 18 | +| `/checklist` | `/codingbuddy:checklist` | migration target | |
| 19 | + |
| 20 | +### Migration Notes |
| 21 | + |
| 22 | +- Legacy bare commands remain functional during the transition period. |
| 23 | +- Once Claude Code fully supports the `plugin:command` namespace resolution, bare aliases will be removed. |
| 24 | +- Both forms invoke the same underlying command file in `commands/`. |
| 25 | + |
| 26 | +## Keyword Workflow Retention |
| 27 | + |
| 28 | +The following keywords remain as primary workflow shortcuts: |
| 29 | + |
| 30 | +- **PLAN** — enter planning mode |
| 31 | +- **ACT** — enter implementation mode |
| 32 | +- **EVAL** — enter evaluation mode |
| 33 | +- **AUTO** — enter autonomous cycle mode |
| 34 | + |
| 35 | +Keywords are **NOT** slash commands. They are workflow triggers detected by hooks and `parse_mode`. Keywords do not collide with any Claude Code namespace and require no migration. |
| 36 | + |
| 37 | +## Policy for New Commands |
| 38 | + |
| 39 | +1. All new commands **MUST** use the `codingbuddy:` prefix. |
| 40 | +2. No exceptions for "convenient" short names. |
| 41 | +3. Command files are placed in `commands/` and automatically discovered by the plugin system. |
| 42 | +4. The namespaced form (`codingbuddy:<name>`) is the canonical invocation. |
0 commit comments