Consistent ce- Prefix for All Skills and Agents

Problem Frame

As the Claude Code plugin ecosystem grows, generic skill names like setup, plan, review, and frontend-design collide when users have multiple plugins installed. Typing /plan surfaces every plugin's plan skill, forcing users to scan descriptions. Agent names also collide across plugins — generic names like adversarial-reviewer or security-reviewer are common enough that multiple plugins could define them. The compound-engineering plugin currently uses an inconsistent mix: 8 core workflow skills have a ce: colon prefix, while 33 others have no prefix at all. Agents use verbose 3-segment references (compound-engineering:<category>:<agent-name>) that are cumbersome and can be simplified now that agents will have a unique ce- prefix. This creates collision risk, a confusing naming taxonomy, and unnecessarily verbose agent references.

Standardizing on a ce- hyphen prefix for all owned skills and agents eliminates collisions, creates a consistent namespace, simplifies agent references, and removes the colon character that requires filesystem sanitization on Windows.

Related: GitHub Issue #337

Requirements

When doing renames of files and folders, you are required to use git mv whenever possible for simplicity and explicit intent and history preservation. You can fallback provided you notify when it happens and why.

Naming Rules

• R1. All compound-engineering-owned skills and agents adopt a ce- hyphen prefix
• R2. Skills currently using ce: colon prefix change to ce- hyphen prefix (e.g., ce:plan -> ce-plan)
• R3. Skills and Agents currently without a prefix get ce- prepended (e.g., setup -> ce-setup, frontend-design -> ce-frontend-design, repo-research-analyst -> ce-repo-research-analyst)
• R4. git-* skills replace the git- prefix with ce- (e.g., git-commit -> ce-commit, git-worktree -> ce-worktree)
• R5. report-bug-ce normalizes to ce-report-bug (drops redundant suffix)

Exclusions

• R6. agent-browser and rclone are excluded (sourced from upstream, not our skills)
• R7. lfg and slfg are excluded from renaming (short memorable workflow entry points), but their internal skill invocations must be updated per R12

Propagation

• R8. The skill and agent frontmatter name: field must match after rename (no more colon-vs-hyphen divergence). Directories need to reflect the new names as well when applicable.
• R9. All cross-references updated: skill-to-skill invocations (/ce:plan -> /ce-plan), fully-qualified references (/compound-engineering:todo-resolve -> /compound-engineering:ce-todo-resolve), Skill("compound-engineering:...") programmatic invocations, prose mentions, skill description: frontmatter fields, and intra-skill path references (${CLAUDE_PLUGIN_ROOT}/skills/<old-name>/...)
• R10. Active documentation updated: root README, plugin README, AGENTS.md. Note: the AGENTS.md "Why ce:?" rationale section (lines 53-60) needs a conceptual rewrite explaining the ce- convention, not just find-and-replace. Historical docs in docs/ (past brainstorms, plans, solutions) are left as-is -- they are records of past decisions.
• R11. Agent prompt files updated where they reference skill names.
• R11b. Skill prompt files updated where they reference Agent names.
• R11c. Agent references drop the compound-engineering: plugin prefix and keep the category. The agent name itself gets the ce- prefix. (e.g. compound-engineering:review:adversarial-reviewer -> review:ce-adversarial-reviewer)
• R12. lfg and slfg orchestration chains updated to use new skill names (lfg/slfg themselves are not renamed per R7, but their internal skill and agent invocations must reflect new names)
• R13. Converter infrastructure preserved: sanitizePathName() and colon-handling logic stays as future protection, not removed. Add a test assertion that no skill name: field contains a colon, so the sanitizer is defense-in-depth rather than a silent workaround.
• R17. Codex converter's isCanonicalCodexWorkflowSkill() and toCanonicalWorkflowSkillName() in src/converters/claude-to-codex.ts updated to match ce- prefix pattern (currently hardcodes ce: prefix check). Related test fixtures in tests/codex-converter.test.ts and tests/codex-writer.test.ts updated accordingly.

Testing

• R14. Path sanitization tests updated to reflect new naming (collision detection still works)
• R15. bun test passes after all changes
• R16. bun run release:validate passes after all changes
• R18. Converter test fixtures that hardcode ce:plan etc. updated to ce-plan where they test compound-engineering plugin behavior. Fixtures testing abstract colon-handling for other plugins may remain.
• R19. Sanity check and for every skill and agent name, grep to confirm new names are correct and old names do not persist except in historical planning, requirements, etc docs.

---

Complete Rename Map

Excluded (no change) - 4 skills

ce: -> ce- (frontmatter only, dirs already match) - 8 skills

git-* -> ce-* (replace prefix) - 4 skills

Special normalization - 1 skill

Standard prefix addition - 24 skills

Total: 37 skills renamed, 4 excluded (41 skills total)

Agent renames - 49 agents

All agents are renamed with ce- prefix within their existing category subdirs. The compound-engineering: plugin prefix is dropped from references, keeping the <category>:ce-<agent-name> format. Category subdirs are preserved for organization.