[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/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
-/compound [brief context]    # Provide additional context hint
+/workflows:compound                    # Document the most recent fix
+/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
-4. **Start `/work` on remote** - Begin implementing in Claude Code on the web (use `&` to run in background)
+3. **Start `/workflows:work`** - Begin implementing this plan locally
+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
-- **`/work` on remote** → Run `/work plans/<issue_title>.md &` to start work in background for Claude Code web
+- **`/workflows:work`** → Call the /workflows:work command with the plan file path
+- **`/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]"
 ---