[2.11.0] Namespace workflow commands to avoid collision with built-in /plan

Fixes #42

Workflow commands now use `workflows:` prefix to avoid collisions with
Claude Code's built-in commands:
- `/workflows:plan` (was `/plan`)
- `/workflows:review` (was `/review`)
- `/workflows:work` (was `/work`)
- `/workflows:compound` (was `/compound`)

To upgrade: Update to latest plugin version. If you see duplicate `/plan`
commands, the new namespaced commands avoid this collision.

Also fixed in this release:
- Added missing `name:` field to heal-skill.md and create-agent-skill.md
- Rewrote corrupted prime.md
- Shortened Playwright MCP alias from `playwright` to `pw`
- Removed deprecated codify.md

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

plugins/compound-engineering/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "compound-engineering",
-  "version": "2.10.0",
+  "version": "2.11.0",
   "description": "AI-powered development tools. 25 agents, 19 commands, 12 skills, 2 MCP servers for code review, research, design, and workflow automation.",
   "author": {
     "name": "Kieran Klaassen",

plugins/compound-engineering/CHANGELOG.md

@@ -5,6 +5,29 @@ All notable changes to the compound-engineering plugin will be documented in thi
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [2.11.0] - 2025-12-10
+
+### Changed
+
+- **Command naming convention** - Workflow commands now use `workflows:` prefix to avoid collisions with built-in Claude Code commands:
+  - `/workflows:plan` (was `/plan`)
+  - `/workflows:review` (was `/review`)
+  - `/workflows:work` (was `/work`)
+  - `/workflows:compound` (was `/compound`)
+
+  This ensures no collision with Claude Code's built-in `/plan` command.
+
+### Fixed
+
+- **`heal-skill.md`** - Added missing `name:` frontmatter field
+- **`create-agent-skill.md`** - Added missing `name:` frontmatter field
+- **`prime.md`** - Rewrote corrupted command file (was incorrectly containing CLAUDE.md content)
+- **Playwright MCP alias** - Shortened from `playwright` to `pw` to stay under 64-char API limit
+
+### Removed
+
+- **`codify.md`** - Removed deprecated command (replaced by `/compound`)
+
 ## [2.10.0] - 2025-12-10
 
 ### Added

plugins/compound-engineering/CLAUDE.md

@@ -35,13 +35,23 @@ agents/
 └── docs/       # Documentation agents
 
 commands/
-├── workflows/  # Core workflow commands (/plan, /review, /work, /compound)
+├── workflows/  # Core workflow commands (workflows:plan, workflows:review, etc.)
 └── *.md        # Utility commands
 
 skills/
 └── *.md        # All skills at root level
 ```
 
+## Command Naming Convention
+
+**Workflow commands** use `workflows:` prefix to avoid collisions with built-in commands:
+- `/workflows:plan` - Create implementation plans
+- `/workflows:review` - Run comprehensive code reviews
+- `/workflows:work` - Execute work items systematically
+- `/workflows:compound` - Document solved problems
+
+**Why `workflows:`?** Claude Code has built-in `/plan` and `/review` commands. Using `name: workflows:plan` in frontmatter creates a unique `/workflows:plan` command with no collision.
+
 ## Documentation
 
 See `docs/solutions/plugin-versioning-requirements.md` for detailed versioning workflow.

plugins/compound-engineering/README.md

@@ -69,14 +69,14 @@ Agents are organized into categories for easier discovery.
 
 ### Workflow Commands
 
-Core workflow commands (use the short form for autocomplete):
+Core workflow commands use `workflows:` prefix to avoid collisions with built-in commands:
 
 | Command | Description |
 |---------|-------------|
-| `/plan` | Create implementation plans |
+| `/workflows:plan` | Create implementation plans |
-| `/review` | Run comprehensive code reviews |
+| `/workflows:review` | Run comprehensive code reviews |
-| `/work` | Execute work items systematically |
+| `/workflows:work` | Execute work items systematically |
-| `/compound` | Document solved problems to compound team knowledge |
+| `/workflows:compound` | Document solved problems to compound team knowledge |
 
 ### Utility Commands
 
@@ -88,7 +88,7 @@ Core workflow commands (use the short form for autocomplete):
 | `/heal-skill` | Fix skill documentation issues |
 | `/plan_review` | Multi-agent plan review in parallel |
 | `/prime` | Prime/setup command |
-| `/report-bug` | Report a bug in the compound-engineering plugin |
+| `/report-bug` | Report a bug in the plugin |
 | `/reproduce-bug` | Reproduce bugs using logs and console |
 | `/resolve_parallel` | Resolve TODO comments in parallel |
 | `/resolve_pr_parallel` | Resolve PR comments in parallel |

plugins/compound-engineering/commands/workflows/compound.md

@@ -1,5 +1,5 @@
 ---
-name: ce:compound
+name: workflows:compound
 description: Document a recently solved problem to compound your team's knowledge
 argument-hint: "[optional: brief context about the fix]"
 ---
@@ -17,8 +17,8 @@ Captures problem solutions while context is fresh, creating structured documenta
 ## Usage
 
 ```bash
-/compound                    # Document the most recent fix
+/workflows:compound                    # Document the most recent fix
-/compound [brief context]    # Provide additional context hint
+/workflows:compound [brief context]    # Provide additional context hint
 ```
 
 ## Execution Strategy: Parallel Subagents
@@ -166,7 +166,7 @@ Build → Test → Find Issue → Research → Improve → Document → Validate
 
 <auto_invoke> <trigger_phrases> - "that worked" - "it's fixed" - "working now" - "problem solved" </trigger_phrases>
 
-<manual_override> Use /compound [context] to document immediately without waiting for auto-detection. </manual_override> </auto_invoke>
+<manual_override> Use /workflows:compound [context] to document immediately without waiting for auto-detection. </manual_override> </auto_invoke>
 
 ## Routes To
 
@@ -194,9 +194,9 @@ Based on problem type, these agents can enhance documentation:
 
 ### When to Invoke
 - **Auto-triggered** (optional): Agents can run post-documentation for enhancement
-- **Manual trigger**: User can invoke agents after /compound completes for deeper review
+- **Manual trigger**: User can invoke agents after /workflows:compound completes for deeper review
 
 ## Related Commands
 
 - `/research [topic]` - Deep investigation (searches docs/solutions/ for patterns)
-- `/plan` - Planning workflow (references documented solutions)
+- `/workflows:plan` - Planning workflow (references documented solutions)

plugins/compound-engineering/commands/workflows/plan.md

@@ -1,5 +1,5 @@
 ---
-name: ce:plan
+name: workflows:plan
 description: Transform feature descriptions into well-structured project plans following conventions
 argument-hint: "[feature description, bug report, or improvement idea]"
 ---
@@ -378,21 +378,21 @@ After writing the plan file, use the **AskUserQuestion tool** to present these o
 **Options:**
 1. **Open plan in editor** - Open the plan file for review
 2. **Run `/plan_review`** - Get feedback from reviewers (DHH, Kieran, Simplicity)
-3. **Start `/work`** - Begin implementing this plan locally
+3. **Start `/workflows:work`** - Begin implementing this plan locally
-4. **Start `/work` on remote** - Begin implementing in Claude Code on the web (use `&` to run in background)
+4. **Start `/workflows:work` on remote** - Begin implementing in Claude Code on the web (use `&` to run in background)
 5. **Create Issue** - Create issue in project tracker (GitHub/Linear)
 6. **Simplify** - Reduce detail level
 
 Based on selection:
 - **Open plan in editor** → Run `open plans/<issue_title>.md` to open the file in the user's default editor
 - **`/plan_review`** → Call the /plan_review command with the plan file path
-- **`/work`** → Call the /work command with the plan file path
+- **`/workflows:work`** → Call the /workflows:work command with the plan file path
-- **`/work` on remote** → Run `/work plans/<issue_title>.md &` to start work in background for Claude Code web
+- **`/workflows:work` on remote** → Run `/workflows:work plans/<issue_title>.md &` to start work in background for Claude Code web
 - **Create Issue** → See "Issue Creation" section below
 - **Simplify** → Ask "What should I simplify?" then regenerate simpler version
 - **Other** (automatically provided) → Accept free text for rework or specific changes
 
-Loop back to options after Simplify or Other changes until user selects `/work` or `/plan_review`.
+Loop back to options after Simplify or Other changes until user selects `/workflows:work` or `/plan_review`.
 
 ## Issue Creation
 
@@ -421,6 +421,6 @@ When user selects "Create Issue", detect their project tracker from CLAUDE.md:
 
 5. **After creation:**
    - Display the issue URL
-   - Ask if they want to proceed to `/work` or `/plan_review`
+   - Ask if they want to proceed to `/workflows:work` or `/plan_review`
 
 NEVER CODE! Just research and write the plan.

plugins/compound-engineering/commands/workflows/review.md

@@ -1,5 +1,5 @@
 ---
-name: ce:review
+name: workflows:review
 description: Perform exhaustive code reviews using multi-agent analysis, ultra-thinking, and worktrees
 argument-hint: "[PR number, GitHub URL, branch name, or latest]"
 ---

plugins/compound-engineering/commands/workflows/work.md

@@ -1,5 +1,5 @@
 ---
-name: ce:work
+name: workflows:work
 description: Execute work plans efficiently while maintaining quality and finishing features
 argument-hint: "[plan file, specification, or todo file path]"
 ---

plugins/compound-engineering/skills/file-todos/SKILL.md

@@ -184,7 +184,7 @@ Work logs serve as:
 
 | Trigger | Flow | Tool |
 |---------|------|------|
-| Code review | `/review` → Findings → `/triage` → Todos | Review agent + skill |
+| Code review | `/workflows:review` → Findings → `/triage` → Todos | Review agent + skill |
 | PR comments | `/resolve_pr_parallel` → Individual fixes → Todos | gh CLI + skill |
 | Code TODOs | `/resolve_todo_parallel` → Fixes + Complex todos | Agent + skill |
 | Planning | Brainstorm → Create todo → Work → Complete | Skill |

plugins/compound-engineering/skills/git-worktree/SKILL.md

@@ -38,8 +38,8 @@ git worktree add .worktrees/feature-name -b feature-name main
 
 Use this skill in these scenarios:
 
-1. **Code Review (`/review`)**: If NOT already on the PR branch, offer worktree for isolated review
+1. **Code Review (`/workflows:review`)**: If NOT already on the PR branch, offer worktree for isolated review
-2. **Feature Work (`/work`)**: Always ask if user wants parallel worktree or live branch work
+2. **Feature Work (`/workflows:work`)**: Always ask if user wants parallel worktree or live branch work
 3. **Parallel Development**: When working on multiple features simultaneously
 4. **Cleanup**: After completing work in a worktree
 
@@ -47,7 +47,7 @@ Use this skill in these scenarios:
 
 ### In Claude Code Workflows
 
-The skill is automatically called from `/review` and `/work` commands:
+The skill is automatically called from `/workflows:review` and `/workflows:work` commands:
 
 ```
 # For review: offers worktree if not on PR branch
@@ -204,7 +204,7 @@ bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh clean
 
 ## Integration with Workflows
 
-### `/review`
+### `/workflows:review`
 
 Instead of always creating a worktree:
 
@@ -217,7 +217,7 @@ Instead of always creating a worktree:
    - no → proceed with PR diff on current branch
 ```
 
-### `/work`
+### `/workflows:work`
 
 Always offer choice: