fix: Remove unnecessary restart/reload instructions from sync output (#178)

The restart/reload instructions shown after `deepwork sync` are not needed
as skills become available immediately without restarting the CLI session.

- Remove reload_instructions class variable from all adapters
- Remove "To use the new skills" output section from sync command
- Remove Step 6 (Relay Reload Instructions) from implement.md
- Simplify Step 7 in learn.md to just run sync without relay instructions

https://claude.ai/code/session_01FD9ALAxSQ6x4QWHqXJiJJR

Co-authored-by: Claude <noreply@anthropic.com>

Author: nhorton

src/deepwork/cli/sync.py

@@ -117,7 +117,6 @@ def sync_skills(project_path: Path) -> None:
     # Sync each platform
     generator = SkillGenerator()
     stats = {"platforms": 0, "skills": 0, "hooks": 0}
-    synced_adapters: list[AgentAdapter] = []
 
     for platform_name in platforms:
         try:
@@ -184,7 +183,6 @@ def sync_skills(project_path: Path) -> None:
                 console.print(f"    [red]✗[/red] Failed to sync skill permissions: {e}")
 
         stats["platforms"] += 1
-        synced_adapters.append(adapter)
 
     # Summary
     console.print()
@@ -202,10 +200,3 @@ def sync_skills(project_path: Path) -> None:
 
     console.print(table)
     console.print()
-
-    # Show reload instructions for each synced platform
-    if synced_adapters and stats["skills"] > 0:
-        console.print("[bold]To use the new skills:[/bold]")
-        for adapter in synced_adapters:
-            console.print(f"  [cyan]{adapter.display_name}:[/cyan] {adapter.reload_instructions}")
-        console.print()

src/deepwork/core/adapters.py

@@ -58,10 +58,6 @@ class AgentAdapter(ABC):
     skill_template: ClassVar[str] = "skill-job-step.md.jinja"
     meta_skill_template: ClassVar[str] = "skill-job-meta.md.jinja"
 
-    # Instructions for reloading skills after sync (shown to users)
-    # Subclasses should override with platform-specific instructions.
-    reload_instructions: ClassVar[str] = "Restart your AI assistant session to use the new skills."
-
     # Mapping from generic SkillLifecycleHook to platform-specific event names.
     # Subclasses should override this to provide platform-specific mappings.
     hook_name_mapping: ClassVar[dict[SkillLifecycleHook, str]] = {}
@@ -296,12 +292,6 @@ class ClaudeAdapter(AgentAdapter):
     display_name = "Claude Code"
     config_dir = ".claude"
 
-    # Claude Code doesn't have a reload command - must restart session
-    reload_instructions: ClassVar[str] = (
-        "Type 'exit' to leave your current session, then run "
-        "'claude --resume' (your history will be maintained)."
-    )
-
     # Claude Code uses PascalCase event names
     hook_name_mapping: ClassVar[dict[SkillLifecycleHook, str]] = {
         SkillLifecycleHook.AFTER_AGENT: "Stop",
@@ -576,11 +566,6 @@ class GeminiAdapter(AgentAdapter):
     skill_template = "skill-job-step.toml.jinja"
     meta_skill_template = "skill-job-meta.toml.jinja"
 
-    # Gemini CLI can reload with /memory refresh
-    reload_instructions: ClassVar[str] = (
-        "Run '/memory refresh' to reload skills, or restart your Gemini CLI session."
-    )
-
     # Gemini CLI does NOT support skill-level hooks
     # Hooks are global/project-level in settings.json, not per-skill
     hook_name_mapping: ClassVar[dict[SkillLifecycleHook, str]] = {}

src/deepwork/standard_jobs/deepwork_jobs/steps/implement.md

@@ -126,11 +126,7 @@ This will:
 - Generate skills for each step
 - Make the skills available in `.claude/skills/` (or appropriate platform directory)
 
-### Step 6: Relay Reload Instructions
-
-After running `deepwork sync`, look at the "To use the new skills" section in the output. **Relay these exact reload instructions to the user** so they know how to pick up the new skills. Don't just reference the sync output - tell them directly what they need to do (e.g., "Type 'exit' then run 'claude --resume'" for Claude Code, or "Run '/memory refresh'" for Gemini CLI).
-
-### Step 7: Consider Rules for the New Job
+### Step 6: Consider Rules for the New Job
 
 After implementing the job, consider whether there are **rules** that would help enforce quality or consistency when working with this job's domain.
 
@@ -221,8 +217,7 @@ Before marking this step complete, ensure:
 - [ ] Each instruction file is complete and actionable
 - [ ] `deepwork sync` executed successfully
 - [ ] Skills generated in platform directory
-- [ ] User informed to follow reload instructions from `deepwork sync`
-- [ ] Considered whether rules would benefit this job (Step 7)
+- [ ] Considered whether rules would benefit this job (Step 6)
 - [ ] If rules suggested, offered to run `/deepwork_rules.define`
 
 ## Quality Criteria

src/deepwork/standard_jobs/deepwork_jobs/steps/learn.md

@@ -233,14 +233,12 @@ If instruction files were modified:
      changes: "Improved [step] instructions based on execution learnings: [brief description]"
    ```
 
-### Step 7: Sync and Relay Instructions
+### Step 7: Sync Skills
 
-1. **Run deepwork sync** (if instructions were modified)
-   ```bash
-   deepwork sync
-   ```
-
-2. **If skills were regenerated**, look at the "To use the new skills" section in the `deepwork sync` output and **relay these exact reload instructions to the user** (e.g., "Type 'exit' then run 'claude --resume'" for Claude Code)
+**Run deepwork sync** (if instructions were modified)
+```bash
+deepwork sync
+```
 
 ## File Reference Patterns
 
@@ -330,7 +328,7 @@ I found the following job executions:
 
 **Summary**
 
-Updated job instructions and created AGENTS.md with bespoke learnings. To get the updated skills, type 'exit' then run 'claude --resume'.
+Updated job instructions and created AGENTS.md with bespoke learnings.
 ```
 
 ## Handling Edge Cases