Generate agent shims from agent-shim: true frontmatter

Instead of syncing pre-written agent shims from a repo, /ce:refresh
now auto-generates shims by scanning reviewers and orchestrators
for agent-shim: true in their frontmatter. Generated shims use
_shim- prefix and are cleaned up on each refresh.

Orchestrator shims delegate to /ce:run. Reviewer shims load the
full persona and answer in character.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: jcasimir

plugins/compound-engineering/skills/refresh/SKILL.md

@@ -74,17 +74,66 @@ bash "$PLUGIN_DIR/skills/refresh/sync-reviewers.sh" \
   orchestrator
 ```
 
-**Note:** The sync script's third argument (`orchestrator`) tells it to use `orchestrator-sources.yaml` as the user config instead of `reviewer-sources.yaml`. It fetches `.md` files from configured sources regardless of content type.
+**Note:** The sync script's third argument tells it which user config to use (`orchestrator-sources.yaml` instead of `reviewer-sources.yaml`). It fetches `.md` files from configured sources regardless of content type.
 
-## Step 5: Show results
+## Step 5: Generate agent shims
+
+After syncing reviewers and orchestrators, scan both directories for files with `agent-shim: true` in their YAML frontmatter. For each match, generate an agent shim file in `$PLUGIN_DIR/agents/review/`.
+
+### For orchestrators (`$PLUGIN_DIR/orchestrators/*.md`)
+
+Read each file's frontmatter. If `agent-shim: true` is present, extract the `name` and `description` fields. Generate a shim at `$PLUGIN_DIR/agents/review/_shim-<name>.md`:
+
+```markdown
+---
+name: <name>
+description: "<first line of description>. Use when the user mentions <name> by name."
+model: inherit
+---
+
+Run `/ce:run <name> $ARGUMENTS`
+```
+
+### For reviewers (`$PLUGIN_DIR/agents/review/*.md`)
+
+Read each file's frontmatter. If `agent-shim: true` is present, extract the `name`, `description`, and the reviewer's filename. Generate a shim at `$PLUGIN_DIR/agents/review/_shim-<short-name>.md` where `<short-name>` is the first name (e.g., `avi` from `avi-rails-architect`, `sandi` from `sandi-metz-oo-reviewer`):
+
+```markdown
+---
+name: <short-name>
+description: "<description>. Use when the user mentions <short-name> by name or asks for their opinion."
+model: inherit
+tools: Read, Grep, Glob, Bash
+---
+
+You are <short-name>. Load your full persona from `$PLUGIN_DIR/agents/review/<reviewer-filename>` and adopt it. Then address the user's request in character.
+
+$ARGUMENTS
+```
+
+### Cleanup
+
+Before generating, remove any existing `_shim-*.md` files in `agents/review/` to avoid stale shims from previously synced definitions.
+
+### Summary
+
+After generating, list the shims created:
+
+```
+Generated agent shims:
+  Orchestrators: erin, lfg, max, nelly, oscar
+  Reviewers: avi, abby, sandi, ...
+```
+
+## Step 6: Show results
 
 The sync script writes summaries to `~/.config/compound-engineering/`:
 - `last-reviewer-refresh-summary.md` — reviewer sync results
 - `last-orchestrator-refresh-summary.md` — orchestrator sync results
 
-Read both files and **output their contents to the user exactly as written**. The summaries are already formatted as markdown — do not summarize, paraphrase, or reformat them.
+Read all summary files that exist and **output their contents to the user exactly as written**. The summaries are already formatted as markdown — do not summarize, paraphrase, or reformat them.
 
-If only one summary file exists (e.g., no orchestrator sources configured yet), show just the one that exists.
+Then show the agent shim generation summary.
 
 ## Source YAML Format