Skip to content

Improve sub-agent output clarity in migration documentation #211

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nhorton merged 2 commits into from
Feb 15, 2026
Merged

Improve sub-agent output clarity in migration documentation #211

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d323364
Instruct repair sub-agents to output minimal, concise text
claude Feb 15, 2026
b7e819a
Use single sub-agent for all legacy skill folder cleanup in errata
claude Feb 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 5 additions & 7 deletions src/deepwork/standard_jobs/deepwork_jobs/steps/errata.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,13 +19,13 @@ Old DeepWork versions created individual skill folders for each job and step. Th
ls .deepwork/jobs/
```

2. **For each job**, kick off a sub-agent to find and remove legacy skill folders. The sub-agent should:
- Search in both `.claude/skills/` and `.gemini/skills/`
- Find folders matching:
2. **Kick off a single sub-agent** to remove all legacy skill folders for every job at once. Be concise — output minimal text, only reporting what was removed or confirming nothing was found. The sub-agent should:
- For each job in `.deepwork/jobs/`, search in both `.claude/skills/` and `.gemini/skills/` for folders matching:
- `{job_name}/` - folder named exactly like the job
- `{job_name}.*/` - folders starting with the job name followed by a period (e.g., `my_job.step1/`, `my_job.step2/`)
- Remove each matching folder
- Report what was removed
- **Do NOT remove** `.claude/skills/deepwork/` or `.gemini/skills/deepwork/`
- Report only: what was removed (one line per folder) or "No legacy folders found"

**Example commands for a job named `competitive_research`:**
```bash
Expand All @@ -38,9 +38,7 @@ Old DeepWork versions created individual skill folders for each job and step. Th
rm -rf .gemini/skills/competitive_research.*/ 2>/dev/null
```

3. **Run sub-agents in parallel** - one for each job to speed up the process.

4. **Verify the `deepwork` skill folder remains:**
3. **Verify the `deepwork` skill folder remains:**
```bash
ls -d .claude/skills/deepwork/ 2>/dev/null || echo "ERROR: deepwork skill missing!"
ls -d .gemini/skills/deepwork/ 2>/dev/null || echo "WARNING: gemini deepwork skill missing (may not have been installed)"
Expand Down
4 changes: 3 additions & 1 deletion src/deepwork/standard_jobs/deepwork_jobs/steps/fix_jobs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,8 @@ For each job directory, you'll need to check and potentially fix the `job.yml` f

**Example prompt for sub-agent:**
```
Be concise. Output minimal text — only report changes made or confirm no changes needed. Do not echo back file contents, do not explain what each migration rule means, and do not narrate your process.

Audit and repair the job at `.deepwork/jobs/[job_name]/job.yml`:
1. Remove any `exposed: true` fields from steps
2. Migrate `stop_hooks` to `hooks.after_agent` format
Expand All @@ -42,7 +44,7 @@ Audit and repair the job at `.deepwork/jobs/[job_name]/job.yml`:
8. Bump version and add changelog entry if changes were made
9. Validate YAML syntax

Report what changes were made.
Report only: which checks passed with no changes, and which changes were made (one line each).
```

### Step 2: Remove `exposed` Field
Expand Down