revert: "refactor(cli)!: rename all skills and agents to consistent ce- prefix" (#503)

AGENTS.md

@@ -120,10 +120,10 @@ Only add a provider when the target format is stable, documented, and has a clea
 
 ## Agent References in Skills
 
-When referencing agents from within skill SKILL.md files (e.g., via the `Agent` or `Task` tool), use the **category-qualified namespace** with the `ce-` prefix: `<category>:ce-<agent-name>`. Never use the bare agent name alone.
+When referencing agents from within skill SKILL.md files (e.g., via the `Agent` or `Task` tool), always use the **fully-qualified namespace**: `compound-engineering:<category>:<agent-name>`. Never use the short agent name alone.
 
 Example:
-- `research:ce-learnings-researcher` (correct)
+- `compound-engineering:research:learnings-researcher` (correct)
 - `learnings-researcher` (wrong - will fail to resolve at runtime)
 
 This prevents resolution failures when the plugin is installed alongside other plugins that may define agents with the same short name.

README.md

@@ -33,16 +33,16 @@ Brainstorm -> Plan -> Work -> Review -> Compound -> Repeat
 
 | Command | Purpose |
 |---------|---------|
-| `/ce-ideate` | Discover high-impact project improvements through divergent ideation and adversarial filtering |
-| `/ce-brainstorm` | Explore requirements and approaches before planning |
-| `/ce-plan` | Turn feature ideas into detailed implementation plans |
-| `/ce-work` | Execute plans with worktrees and task tracking |
-| `/ce-code-review` | Multi-agent code review before merging |
-| `/ce-compound` | Document learnings to make future work easier |
+| `/ce:ideate` | Discover high-impact project improvements through divergent ideation and adversarial filtering |
+| `/ce:brainstorm` | Explore requirements and approaches before planning |
+| `/ce:plan` | Turn feature ideas into detailed implementation plans |
+| `/ce:work` | Execute plans with worktrees and task tracking |
+| `/ce:review` | Multi-agent code review before merging |
+| `/ce:compound` | Document learnings to make future work easier |
 
-`/ce-brainstorm` is the main entry point -- it refines ideas into a requirements plan through interactive Q&A, and short-circuits automatically when ceremony isn't needed. `/ce-plan` takes either a requirements doc from brainstorming or a detailed idea and distills it into a technical plan that agents (or humans) can work from.
+`/ce:brainstorm` is the main entry point -- it refines ideas into a requirements plan through interactive Q&A, and short-circuits automatically when ceremony isn't needed. `/ce:plan` takes either a requirements doc from brainstorming or a detailed idea and distills it into a technical plan that agents (or humans) can work from.
 
-`/ce-ideate` is used less often but can be a force multiplier -- it proactively surfaces strong improvement ideas based on your codebase, with optional steering from you.
+`/ce:ideate` is used less often but can be a force multiplier -- it proactively surfaces strong improvement ideas based on your codebase, with optional steering from you.
 
 Each cycle compounds: brainstorms sharpen plans, plans inform future plans, reviews catch more issues, patterns get documented.
 
@@ -115,7 +115,7 @@ bunx @every-env/compound-plugin install compound-engineering --to all
 | Target | Output path | Notes |
 |--------|------------|-------|
 | `opencode` | `~/.config/opencode/` | Commands as `.md` files; `opencode.json` MCP config deep-merged; backups made before overwriting |
-| `codex` | `~/.codex/prompts` + `~/.codex/skills` | Claude commands become prompt + skill pairs; all skills copied directly; deprecated `workflows:*` aliases are omitted |
+| `codex` | `~/.codex/prompts` + `~/.codex/skills` | Claude commands become prompt + skill pairs; canonical `ce:*` workflow skills also get prompt wrappers; deprecated `workflows:*` aliases are omitted |
 | `droid` | `~/.factory/` | Tool names mapped (`Bash`->`Execute`, `Write`->`Create`); namespace prefixes stripped |
 | `pi` | `~/.pi/agent/` | Prompts, skills, extensions, and `mcporter.json` for MCPorter interoperability |
 | `gemini` | `.gemini/` | Skills from agents; commands as `.toml`; namespaced commands become directories (`workflows:plan` -> `commands/workflows/plan.toml`) |

docs/brainstorms/2026-04-02-slack-analyst-agent-requirements.md

@@ -1,6 +1,6 @@
 ---
 date: 2026-04-02
-topic: ce-slack-researcher-agent
+topic: slack-researcher-agent
 ---
 
 # Slack Analyst Agent
@@ -15,7 +15,7 @@ The official Slack plugin provides user-facing commands (`/slack:find-discussion
 
 **Agent Identity and Placement**
 
-- R1. Create a research-category agent at `agents/research/ce-slack-researcher.md` following the established research agent pattern (frontmatter with name, description, model:inherit; examples block; phased execution).
+- R1. Create a research-category agent at `agents/research/slack-researcher.md` following the established research agent pattern (frontmatter with name, description, model:inherit; examples block; phased execution).
 - R2. The agent's role is analytical: it searches Slack for context relevant to the task at hand and returns a concise, structured digest. It does not send messages, create canvases, or take any write actions in Slack.
 
 ---
@@ -53,9 +53,9 @@ The official Slack plugin provides user-facing commands (`/slack:find-discussion
 **Workflow Integration**
 
 - R12. Integrate into three calling workflows:
-  - **ce-ideate** -- dispatch during Phase 1 (Codebase Scan), alongside learnings-researcher. Slack context enriches ideation by surfacing org discussions about the focus area.
-  - **ce-plan** -- dispatch during the research/context-gathering phase. Slack context surfaces constraints, prior decisions, and ongoing discussions relevant to the implementation.
-  - **ce-brainstorm** -- dispatch during Phase 1.1 (Existing Context Scan). Brainstorming especially benefits from knowing what the org has already discussed about the topic.
+  - **ce:ideate** -- dispatch during Phase 1 (Codebase Scan), alongside learnings-researcher. Slack context enriches ideation by surfacing org discussions about the focus area.
+  - **ce:plan** -- dispatch during the research/context-gathering phase. Slack context surfaces constraints, prior decisions, and ongoing discussions relevant to the implementation.
+  - **ce:brainstorm** -- dispatch during Phase 1.1 (Existing Context Scan). Brainstorming especially benefits from knowing what the org has already discussed about the topic.
 - R13. In all calling workflows, dispatch the Slack analyst agent in parallel with other research agents (learnings-researcher, etc.) to avoid adding latency. Callers wait for all parallel agents to return before consolidating results (this is the existing pattern for parallel research dispatch). The Slack analyst's dispatch condition is MCP availability (R3). The agent itself handles the meaningful-context check (R4) internally.
 - R14. Callers should incorporate the Slack analyst's output into their existing context summary alongside other research results, not as a separate section.
 
@@ -94,7 +94,7 @@ The official Slack plugin provides user-facing commands (`/slack:find-discussion
 
 - [Affects R3][Technical] How exactly should callers detect Slack MCP availability? Claude Code's tool list inspection, checking for any `slack_*` tool prefix, or another mechanism?
 - [Affects R5][Needs research] What is the optimal number of search queries per invocation to balance coverage vs. token cost? Start with 2-3 and tune based on real usage.
-- [Affects R12][Technical] What modifications are needed in ce-ideate, ce-plan, and ce-brainstorm skill files to add the conditional dispatch? Review each skill's research phase to find the right insertion point.
+- [Affects R12][Technical] What modifications are needed in ce:ideate, ce:plan, and ce:brainstorm skill files to add the conditional dispatch? Review each skill's research phase to find the right insertion point.
 
 ## Next Steps
 

docs/plans/2026-03-16-001-feat-issue-grounded-ideation-plan.md

@@ -29,7 +29,7 @@ Two deliverables:
 
 ### Deliverable 1: Issue Intelligence Analyst Agent
 
-**File**: `plugins/compound-engineering/agents/research/ce-issue-intelligence-analyst.agent.md`
+**File**: `plugins/compound-engineering/agents/research/issue-intelligence-analyst.md`
 
 **Frontmatter:**
 ```yaml
@@ -240,7 +240,7 @@ When checking for recent ideation documents, treat issue-grounded and non-issue
 ## Sources & References
 
 - **Origin brainstorm:** [docs/brainstorms/2026-03-16-issue-grounded-ideation-requirements.md](docs/brainstorms/2026-03-16-issue-grounded-ideation-requirements.md) — Key decisions: pattern-first ideation, hybrid frame strategy, flexible argument detection, additive to Phase 1, standalone agent
-- **Exemplar agent:** `plugins/compound-engineering/agents/research/ce-repo-research-analyst.agent.md` — agent structure pattern
+- **Exemplar agent:** `plugins/compound-engineering/agents/research/repo-research-analyst.md` — agent structure pattern
 - **ce:ideate skill:** `plugins/compound-engineering/skills/ce-ideate/SKILL.md` — integration target
 - **Institutional learning:** `docs/solutions/skill-design/compound-refresh-skill-improvements.md` — impact clustering pattern, platform-agnostic tool references, evidence-first interaction
 - **Real-world test repo:** `EveryInc/proof` (555 issues, 25+ LIVE_DOC_UNAVAILABLE duplicates, structured labels)

docs/plans/2026-03-22-001-feat-frontend-design-skill-rewrite-beta-plan.md

@@ -49,7 +49,7 @@ Two external sources informed the redesign: Anthropic's official frontend-design
 - `plugins/compound-engineering/skills/ce-plan-beta/SKILL.md` -- reference for cross-agent interaction patterns (Pattern A: platform's blocking question tool with named equivalents)
 - `plugins/compound-engineering/skills/reproduce-bug/SKILL.md` -- reference for cross-agent patterns
 - `plugins/compound-engineering/skills/agent-browser/SKILL.md` -- upstream-vendored, reference for browser automation CLI
-- `plugins/compound-engineering/agents/design/ce-design-iterator.agent.md` -- contains `<frontend_aesthetics>` block that overlaps with current skill; new skill will supersede this when both are loaded
+- `plugins/compound-engineering/agents/design/design-iterator.md` -- contains `<frontend_aesthetics>` block that overlaps with current skill; new skill will supersede this when both are loaded
 - `plugins/compound-engineering/AGENTS.md` -- skill compliance checklist (cross-platform interaction, tool selection, reference rules)
 
 ### Institutional Learnings

docs/plans/2026-03-23-001-feat-plan-review-personas-beta-plan.md

@@ -42,7 +42,7 @@ The current `document-review` applies five generic criteria (Clarity, Completene
 
 - `plugins/compound-engineering/skills/ce-review/SKILL.md` -- Multi-agent orchestration reference: parallel dispatch via Task tool, always-on + conditional agents, P1/P2/P3 severity, finding synthesis with dedup
 - `plugins/compound-engineering/skills/document-review/SKILL.md` -- Current single-voice skill to replace. Key contract: "Review complete" terminal signal
-- `plugins/compound-engineering/agents/review/ce-*.agent.md` -- 15 existing review agents. Frontmatter schema: `name`, `description`, `model: inherit`. Body: examples block, role definition, analysis protocol, output format
+- `plugins/compound-engineering/agents/review/*.md` -- 15 existing review agents. Frontmatter schema: `name`, `description`, `model: inherit`. Body: examples block, role definition, analysis protocol, output format
 - `plugins/compound-engineering/AGENTS.md` -- Agent naming: fully-qualified `compound-engineering:<category>:<agent-name>`. Agent placement: `agents/<category>/<name>.md`
 
 ### Caller Integration Points
@@ -214,8 +214,8 @@ Orchestrator routing (document review simplification):
 **Dependencies:** None
 
 **Files:**
-- Create: `plugins/compound-engineering/agents/document-review/ce-coherence-reviewer.agent.md`
-- Create: `plugins/compound-engineering/agents/document-review/ce-feasibility-reviewer.agent.md`
+- Create: `plugins/compound-engineering/agents/review/coherence-reviewer.md`
+- Create: `plugins/compound-engineering/agents/review/feasibility-reviewer.md`
 
 **Approach:**
 - Follow existing agent structure: frontmatter (name, description, model: inherit), examples block, role definition, analysis protocol
@@ -237,8 +237,8 @@ Orchestrator routing (document review simplification):
 - Suppress: implementation style choices, testing strategy details, code organization preferences, theoretical scalability concerns
 
 **Patterns to follow:**
-- `plugins/compound-engineering/agents/review/ce-code-simplicity-reviewer.agent.md` for agent structure and output format conventions
-- `plugins/compound-engineering/agents/review/ce-architecture-strategist.agent.md` for systematic analysis protocol style
+- `plugins/compound-engineering/agents/review/code-simplicity-reviewer.md` for agent structure and output format conventions
+- `plugins/compound-engineering/agents/review/architecture-strategist.md` for systematic analysis protocol style
 - iterative-engineering agents for confidence calibration and suppress conditions pattern
 
 **Test scenarios:**
@@ -267,10 +267,10 @@ Orchestrator routing (document review simplification):
 **Dependencies:** Unit 1 (for consistent agent structure)
 
 **Files:**
-- Create: `plugins/compound-engineering/agents/document-review/ce-product-lens-reviewer.agent.md`
-- Create: `plugins/compound-engineering/agents/document-review/ce-design-lens-reviewer.agent.md`
-- Create: `plugins/compound-engineering/agents/document-review/ce-security-lens-reviewer.agent.md`
-- Create: `plugins/compound-engineering/agents/document-review/ce-scope-guardian-reviewer.agent.md`
+- Create: `plugins/compound-engineering/agents/review/product-lens-reviewer.md`
+- Create: `plugins/compound-engineering/agents/review/design-lens-reviewer.md`
+- Create: `plugins/compound-engineering/agents/review/security-lens-reviewer.md`
+- Create: `plugins/compound-engineering/agents/review/scope-guardian-reviewer.md`
 
 **Approach:**
 All four use the same structure established in Unit 1 (frontmatter, examples, role, protocol, confidence calibration, suppress conditions). Output normalization handled by shared reference files.
@@ -311,7 +311,7 @@ All four use the same structure established in Unit 1 (frontmatter, examples, ro
 
 **Patterns to follow:**
 - Unit 1 agents for consistent structure
-- `plugins/compound-engineering/agents/review/ce-security-sentinel.agent.md` for security analysis style (plan-level adaptation)
+- `plugins/compound-engineering/agents/review/security-sentinel.md` for security analysis style (plan-level adaptation)
 
 **Test scenarios:**
 - product-lens-reviewer challenges a plan that builds a complex admin dashboard when the stated goal is "improve user onboarding"

docs/plans/2026-03-25-001-feat-onboarding-skill-plan.md

@@ -277,5 +277,5 @@ The primary audience is human developers. A document that works for human compre
 - **Origin document:** [docs/brainstorms/2026-03-25-vonboarding-skill-requirements.md](../brainstorms/2026-03-25-vonboarding-skill-requirements.md)
 - Script-first architecture: [docs/solutions/skill-design/script-first-skill-architecture.md](../solutions/skill-design/script-first-skill-architecture.md)
 - Compound-refresh learnings: [docs/solutions/skill-design/compound-refresh-skill-improvements.md](../solutions/skill-design/compound-refresh-skill-improvements.md)
-- Repo-research-analyst agent: `plugins/compound-engineering/agents/research/ce-repo-research-analyst.agent.md`
+- Repo-research-analyst agent: `plugins/compound-engineering/agents/research/repo-research-analyst.md`
 - Skill compliance checklist: `plugins/compound-engineering/AGENTS.md`