docs: fix workflow command documentation to use correct syntax

Update all documentation to show the correct command syntax:
- `/plan`, `/review`, `/work`, `/codify` (short form, autocompletes)

Previously showed `/workflows:plan` etc. which doesn't work.
The `name:` field in frontmatter determines the short command name.

Fixes #19

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

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

plugins/compounding-engineering/CHANGELOG.md

@@ -100,7 +100,7 @@ Major reorganization consolidating agents, commands, and skills from multiple so
 - `/prime` - Prime/setup command
 - `/create-agent-skill` - Create or edit Claude Code skills
 - `/heal-skill` - Fix skill documentation issues
-- `/workflows:codify` - Document solved problems for knowledge base
+- `/codify` - Document solved problems for knowledge base
 
 **New Skills (10)**
 - `andrew-kane-gem-writer` - Write Ruby gems following Andrew Kane's patterns
@@ -125,7 +125,7 @@ Major reorganization consolidating agents, commands, and skills from multiple so
 
 **Commands Restructured**
 - Workflow commands moved to `commands/workflows/` subdirectory
-- `/plan`, `/review`, `/work` now accessed as `/workflows:plan`, `/workflows:review`, `/workflows:work`
+- `/plan`, `/review`, `/work`, `/codify` accessible via short names (autocomplete) or full path
 
 ### Summary
 

plugins/compounding-engineering/CLAUDE.md

@@ -35,7 +35,7 @@ agents/
 └── docs/       # Documentation agents
 
 commands/
-├── workflows/  # Core workflow commands (/workflows:*)
+├── workflows/  # Core workflow commands (/plan, /review, /work, /codify)
 └── *.md        # Utility commands
 
 skills/

plugins/compounding-engineering/README.md

@@ -67,14 +67,14 @@ Agents are organized into categories for easier discovery.
 
 ### Workflow Commands
 
-Access via `/workflows:command`:
+Core workflow commands (use the short form for autocomplete):
 
 | Command | Description |
 |---------|-------------|
-| `/workflows:plan` | Create implementation plans |
-| `/workflows:review` | Run comprehensive code reviews |
-| `/workflows:work` | Execute work items systematically |
-| `/workflows:codify` | Document solved problems for knowledge base |
+| `/plan` | Create implementation plans |
+| `/review` | Run comprehensive code reviews |
+| `/work` | Execute work items systematically |
+| `/codify` | Document solved problems for knowledge base |
 
 ### Utility Commands
 

plugins/compounding-engineering/commands/generate_command.md

@@ -127,7 +127,7 @@ Implement #$ARGUMENTS following these steps:
 
 ## Creating the Command File
 
-1. **Create the file** at `.claude/commands/[name].md` or `.claude/commands/workflows/[name].md`
+1. **Create the file** at `.claude/commands/[name].md` (subdirectories like `workflows/` supported)
 2. **Start with YAML frontmatter** (see section above)
 3. **Structure the command** using the template above
 4. **Test the command** by using it with appropriate arguments

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

@@ -184,7 +184,7 @@ Work logs serve as:
 
 | Trigger | Flow | Tool |
 |---------|------|------|
-| Code review | `/workflows:review` → Findings → `/triage` → Todos | Review agent + skill |
+| Code review | `/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/compounding-engineering/skills/git-worktree/SKILL.md

@@ -20,8 +20,8 @@ This skill provides a unified interface for managing Git worktrees across your d
 
 Use this skill in these scenarios:
 
-1. **Code Review (`/workflows:review`)**: If NOT already on the PR branch, offer worktree for isolated review
-2. **Feature Work (`/workflows:work`)**: Always ask if user wants parallel worktree or live branch work
+1. **Code Review (`/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
 3. **Parallel Development**: When working on multiple features simultaneously
 4. **Cleanup**: After completing work in a worktree
 
@@ -29,7 +29,7 @@ Use this skill in these scenarios:
 
 ### In Claude Code Workflows
 
-The skill is automatically called from `/workflows:review` and `/workflows:work` commands:
+The skill is automatically called from `/review` and `/work` commands:
 
 ```
 # For review: offers worktree if not on PR branch
@@ -182,7 +182,7 @@ bash .claude/skills/git-worktree/scripts/worktree-manager.sh cleanup
 
 ## Integration with Workflows
 
-### `/workflows:review`
+### `/review`
 
 Instead of always creating a worktree:
 
@@ -195,7 +195,7 @@ Instead of always creating a worktree:
    - no → proceed with PR diff on current branch
 ```
 
-### `/workflows:work`
+### `/work`
 
 Always offer choice: