From d323364ca91e08d8d5d0ec3effcbee273185724a Mon Sep 17 00:00:00 2001 From: Claude Date: Sun, 15 Feb 2026 21:25:14 +0000 Subject: [PATCH 1/2] Instruct repair sub-agents to output minimal, concise text The parallel sub-agents in fix_jobs and errata steps were producing verbose output. Updated their prompts to request concise reporting: only changes made or confirmation of no changes needed. https://claude.ai/code/session_017B8xtZAgmif6v86MbXXjwb --- src/deepwork/standard_jobs/deepwork_jobs/steps/errata.md | 4 ++-- src/deepwork/standard_jobs/deepwork_jobs/steps/fix_jobs.md | 4 +++- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/src/deepwork/standard_jobs/deepwork_jobs/steps/errata.md b/src/deepwork/standard_jobs/deepwork_jobs/steps/errata.md index 10245c62..28a7227b 100644 --- a/src/deepwork/standard_jobs/deepwork_jobs/steps/errata.md +++ b/src/deepwork/standard_jobs/deepwork_jobs/steps/errata.md @@ -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: +2. **For each job**, kick off a sub-agent to find and remove legacy skill folders. The sub-agent should be concise — output minimal text, only reporting what was removed or confirming nothing was found. Do not narrate the process or echo commands. The sub-agent should: - Search in both `.claude/skills/` and `.gemini/skills/` - Find 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 + - Report only: what was removed (one line per folder) or "No legacy folders found" **Example commands for a job named `competitive_research`:** ```bash diff --git a/src/deepwork/standard_jobs/deepwork_jobs/steps/fix_jobs.md b/src/deepwork/standard_jobs/deepwork_jobs/steps/fix_jobs.md index ccb5e4a4..64984b1c 100644 --- a/src/deepwork/standard_jobs/deepwork_jobs/steps/fix_jobs.md +++ b/src/deepwork/standard_jobs/deepwork_jobs/steps/fix_jobs.md @@ -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 @@ -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 From b7e819a4334703a517429080a4ceab5574304e26 Mon Sep 17 00:00:00 2001 From: Claude Date: Sun, 15 Feb 2026 21:40:09 +0000 Subject: [PATCH 2/2] Use single sub-agent for all legacy skill folder cleanup in errata Instead of spawning one sub-agent per job, use a single sub-agent that iterates over all jobs and removes their legacy skill folders. https://claude.ai/code/session_017B8xtZAgmif6v86MbXXjwb --- .../standard_jobs/deepwork_jobs/steps/errata.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/src/deepwork/standard_jobs/deepwork_jobs/steps/errata.md b/src/deepwork/standard_jobs/deepwork_jobs/steps/errata.md index 28a7227b..e9e43605 100644 --- a/src/deepwork/standard_jobs/deepwork_jobs/steps/errata.md +++ b/src/deepwork/standard_jobs/deepwork_jobs/steps/errata.md @@ -19,12 +19,12 @@ 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 be concise — output minimal text, only reporting what was removed or confirming nothing was found. Do not narrate the process or echo commands. 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 + - **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`:** @@ -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)"