fix: preserve skill-style document-review handoffs

plugins/compound-engineering/skills/ce-plan/SKILL.md

@@ -513,17 +513,17 @@ After writing the plan file, present the options using the platform's blocking q
 
 **Options:**
 1. **Open plan in editor** - Open the plan file for review
-2. **Run `deepen-plan` skill** - Stress-test weak sections with targeted research when the plan needs more confidence
-3. **Review and refine** - Improve the plan through structured document review
+2. **Run `/deepen-plan`** - Stress-test weak sections with targeted research when the plan needs more confidence
+3. **Run `document-review` skill** - Improve the plan through structured document review
 4. **Share to Proof** - Upload the plan for collaborative review and sharing
-5. **Start `ce:work` skill** - Begin implementing this plan in the current environment
-6. **Start `ce:work` skill in another session** - Begin implementing in a separate agent session when the current platform supports it
+5. **Start `/ce:work`** - Begin implementing this plan in the current environment
+6. **Start `/ce:work` in another session** - Begin implementing in a separate agent session when the current platform supports it
 7. **Create Issue** - Create an issue in the configured tracker
 
 Based on selection:
 - **Open plan in editor** → Open `docs/plans/<plan_filename>.md` using the current platform's file-open or editor mechanism (e.g., `open` on macOS, `xdg-open` on Linux, or the IDE's file-open API)
-- **`deepen-plan` skill** → Call the `deepen-plan` skill with the plan path
-- **Review and refine** → Load the `document-review` skill
+- **`/deepen-plan`** → Call `/deepen-plan` with the plan path
+- **`document-review` skill** → Load the `document-review` skill with the plan path
 - **Share to Proof** → Upload the plan:
   ```bash
   CONTENT=$(cat docs/plans/<plan_filename>.md)
@@ -534,12 +534,12 @@ Based on selection:
   PROOF_URL=$(echo "$RESPONSE" | jq -r '.tokenUrl')
   ```
   Display `View & collaborate in Proof: <PROOF_URL>` if successful, then return to the options
-- **`ce:work` skill** → Call the `ce:work` skill with the plan path
-- **`ce:work` skill in another session** → If the current platform supports launching a separate agent session, start the `ce:work` skill with the plan path there. Otherwise, explain the limitation briefly and offer to run the `ce:work` skill in the current session instead.
+- **`/ce:work`** → Call `/ce:work` with the plan path
+- **`/ce:work` in another session** → If the current platform supports launching a separate agent session, start `/ce:work` with the plan path there. Otherwise, explain the limitation briefly and offer to run `/ce:work` in the current session instead.
 - **Create Issue** → Follow the Issue Creation section below
 - **Other** → Accept free text for revisions and loop back to options
 
-If running with ultrathink enabled, or the platform's reasoning/effort level is set to max or extra-high, automatically run the `deepen-plan` skill only when the plan is `Standard` or `Deep`, high-risk, or still shows meaningful confidence gaps in decisions, sequencing, system-wide impact, risks, or verification.
+If running with ultrathink enabled, or the platform's reasoning/effort level is set to max or extra-high, automatically run `/deepen-plan` only when the plan is `Standard` or `Deep`, high-risk, or still shows meaningful confidence gaps in decisions, sequencing, system-wide impact, risks, or verification.
 
 ## Issue Creation
 
@@ -564,6 +564,6 @@ When the user selects "Create Issue", detect their project tracker from `CLAUDE.
 
 After issue creation:
 - Display the issue URL
-- Ask whether to proceed to the `ce:work` skill
+- Ask whether to proceed to `/ce:work`
 
 NEVER CODE! Research, decide, and write the plan.

plugins/compound-engineering/skills/deepen-plan/SKILL.md

@@ -17,7 +17,7 @@ Use this skill when the plan already exists and the question is not "Is this doc
 This skill does **not** turn plans into implementation scripts. It identifies weak sections, runs targeted research only for those sections, and strengthens the plan in place.
 
 `document-review` and `deepen-plan` are different:
-- Use `document-review` when the document needs clarity, simplification, completeness, or scope control
+- Use the `document-review` skill when the document needs clarity, simplification, completeness, or scope control
 - Use `deepen-plan` when the document is structurally sound but still needs stronger rationale, sequencing, risk treatment, or system-wide thinking
 
 ## Interaction Method
@@ -82,7 +82,7 @@ Use this default:
 
 If the plan already appears sufficiently grounded:
 - Say so briefly
-- Recommend moving to `ce:work` or `document-review`
+- Recommend moving to `/ce:work` or the `document-review` skill
 - If the user explicitly asked to deepen anyway, continue with a light pass and deepen at most 1-2 sections
 
 ### Phase 1: Parse the Current `ce:plan` Structure
@@ -304,18 +304,18 @@ If substantive changes were made, present next steps using the platform's blocki
 
 **Options:**
 1. **View diff** - Show what changed
-2. **Review and refine** - Run the `document-review` skill on the updated plan
+2. **Run `document-review` skill** - Improve the updated plan through structured document review
 3. **Start `ce:work` skill** - Begin implementing the plan
 4. **Deepen specific sections further** - Run another targeted deepening pass on named sections
 
 Based on selection:
 - **View diff** -> Show the important additions and changed sections
-- **Review and refine** -> Load the `document-review` skill with the plan path
+- **`document-review` skill** -> Load the `document-review` skill with the plan path
 - **Start `ce:work` skill** -> Call the `ce:work` skill with the plan path
 - **Deepen specific sections further** -> Ask which sections still feel weak and run another targeted pass only for those sections
 
 If no substantive changes were warranted:
 - Say that the plan already appears sufficiently grounded
-- Offer `document-review` or `ce:work` as the next step instead
+- Offer the `document-review` skill or `/ce:work` as the next step instead
 
 NEVER CODE! Research, challenge, and strengthen the plan.