From 489f3853601e0d5382a0df41a200d1cdda79d39f Mon Sep 17 00:00:00 2001 From: Claude Date: Sun, 15 Feb 2026 22:58:57 +0000 Subject: [PATCH 1/2] Add callout requiring new_job workflow for job creation The /deepwork skill now prominently instructs agents to use the `new_job` workflow (via `deepwork_jobs` MCP tools) when creating new jobs. Uses an XML tag and clear MUST/NEVER language to prevent agents from manually writing job.yml files or directory structures, which bypasses quality gates and testing. https://claude.ai/code/session_01B5qQFeL3o78cDSMnqammQk --- .claude/skills/deepwork/SKILL.md | 22 +++++++++++++++++++ .../templates/claude/skill-deepwork.md.jinja | 22 +++++++++++++++++++ 2 files changed, 44 insertions(+) diff --git a/.claude/skills/deepwork/SKILL.md b/.claude/skills/deepwork/SKILL.md index ee3021d2..0d9fe9d4 100644 --- a/.claude/skills/deepwork/SKILL.md +++ b/.claude/skills/deepwork/SKILL.md @@ -19,6 +19,28 @@ Execute multi-step workflows with quality gate checkpoints. 4. Call `finished_step` with your outputs when done 5. Handle the response: `needs_work`, `next_step`, or `workflow_complete` +## Creating New Jobs + + +You MUST use the `new_job` workflow to create new DeepWork jobs. NEVER create job +definitions by manually writing `job.yml` files, step instructions, or job directory +structures by hand. The `new_job` workflow exists specifically to ensure jobs are +well-structured, tested, and reviewed. + + +To create a new job, use the MCP tools: + +1. Call `get_workflows` to confirm the `deepwork_jobs` job is available +2. Call `start_workflow` with: + - `job_name`: `"deepwork_jobs"` + - `workflow_name`: `"new_job"` + - `goal`: a description of what the new job should accomplish + - `instance_id`: a short name for the new job (e.g., `"code_review"`) +3. Follow the guided steps: **define** → **implement** → **test** → **iterate** + +The workflow handles specification authoring, file generation, real-world testing, and +iterative refinement. Skipping it produces brittle, untested jobs that lack quality gates. + ## Intent Parsing When the user invokes `/deepwork`, parse their intent: diff --git a/src/deepwork/templates/claude/skill-deepwork.md.jinja b/src/deepwork/templates/claude/skill-deepwork.md.jinja index e9922706..11741c4a 100644 --- a/src/deepwork/templates/claude/skill-deepwork.md.jinja +++ b/src/deepwork/templates/claude/skill-deepwork.md.jinja @@ -27,6 +27,28 @@ Execute multi-step workflows with quality gate checkpoints. 4. Call `finished_step` with your outputs when done 5. Handle the response: `needs_work`, `next_step`, or `workflow_complete` +## Creating New Jobs + + +You MUST use the `new_job` workflow to create new DeepWork jobs. NEVER create job +definitions by manually writing `job.yml` files, step instructions, or job directory +structures by hand. The `new_job` workflow exists specifically to ensure jobs are +well-structured, tested, and reviewed. + + +To create a new job, use the MCP tools: + +1. Call `get_workflows` to confirm the `deepwork_jobs` job is available +2. Call `start_workflow` with: + - `job_name`: `"deepwork_jobs"` + - `workflow_name`: `"new_job"` + - `goal`: a description of what the new job should accomplish + - `instance_id`: a short name for the new job (e.g., `"code_review"`) +3. Follow the guided steps: **define** → **implement** → **test** → **iterate** + +The workflow handles specification authoring, file generation, real-world testing, and +iterative refinement. Skipping it produces brittle, untested jobs that lack quality gates. + ## Intent Parsing When the user invokes `/deepwork`, parse their intent: From 0c7f9155a7f53c9633b163e4154a80f11d7ebb8f Mon Sep 17 00:00:00 2001 From: Claude Date: Sun, 15 Feb 2026 23:06:27 +0000 Subject: [PATCH 2/2] Revise new_job callout to defer to MCP tool guidance Remove hardcoded process details and negative phrasing from the callout. Instead of listing workflow steps or saying what not to do, direct the agent to follow the instructions returned by the MCP tools as it progresses through the workflow. https://claude.ai/code/session_01B5qQFeL3o78cDSMnqammQk --- .claude/skills/deepwork/SKILL.md | 12 ++++-------- .../templates/claude/skill-deepwork.md.jinja | 12 ++++-------- 2 files changed, 8 insertions(+), 16 deletions(-) diff --git a/.claude/skills/deepwork/SKILL.md b/.claude/skills/deepwork/SKILL.md index 0d9fe9d4..f24c3308 100644 --- a/.claude/skills/deepwork/SKILL.md +++ b/.claude/skills/deepwork/SKILL.md @@ -22,10 +22,9 @@ Execute multi-step workflows with quality gate checkpoints. ## Creating New Jobs -You MUST use the `new_job` workflow to create new DeepWork jobs. NEVER create job -definitions by manually writing `job.yml` files, step instructions, or job directory -structures by hand. The `new_job` workflow exists specifically to ensure jobs are -well-structured, tested, and reviewed. +You MUST create new DeepWork jobs by starting the `new_job` workflow via the DeepWork +MCP tools. Follow the guidance from the DeepWork MCP server as you go through the +workflow — it will walk you through each step. To create a new job, use the MCP tools: @@ -36,10 +35,7 @@ To create a new job, use the MCP tools: - `workflow_name`: `"new_job"` - `goal`: a description of what the new job should accomplish - `instance_id`: a short name for the new job (e.g., `"code_review"`) -3. Follow the guided steps: **define** → **implement** → **test** → **iterate** - -The workflow handles specification authoring, file generation, real-world testing, and -iterative refinement. Skipping it produces brittle, untested jobs that lack quality gates. +3. Follow the instructions returned by the MCP tools as you progress through the workflow ## Intent Parsing diff --git a/src/deepwork/templates/claude/skill-deepwork.md.jinja b/src/deepwork/templates/claude/skill-deepwork.md.jinja index 11741c4a..4acc469c 100644 --- a/src/deepwork/templates/claude/skill-deepwork.md.jinja +++ b/src/deepwork/templates/claude/skill-deepwork.md.jinja @@ -30,10 +30,9 @@ Execute multi-step workflows with quality gate checkpoints. ## Creating New Jobs -You MUST use the `new_job` workflow to create new DeepWork jobs. NEVER create job -definitions by manually writing `job.yml` files, step instructions, or job directory -structures by hand. The `new_job` workflow exists specifically to ensure jobs are -well-structured, tested, and reviewed. +You MUST create new DeepWork jobs by starting the `new_job` workflow via the DeepWork +MCP tools. Follow the guidance from the DeepWork MCP server as you go through the +workflow — it will walk you through each step. To create a new job, use the MCP tools: @@ -44,10 +43,7 @@ To create a new job, use the MCP tools: - `workflow_name`: `"new_job"` - `goal`: a description of what the new job should accomplish - `instance_id`: a short name for the new job (e.g., `"code_review"`) -3. Follow the guided steps: **define** → **implement** → **test** → **iterate** - -The workflow handles specification authoring, file generation, real-world testing, and -iterative refinement. Skipping it produces brittle, untested jobs that lack quality gates. +3. Follow the instructions returned by the MCP tools as you progress through the workflow ## Intent Parsing