Add review_job_spec step to deepwork_jobs workflow

Add DTD-based quality validation step between define and implement that:
- Uses a sub-agent (haiku model) for unbiased review of job.yml
- Evaluates all 9 DTD quality criteria from job_spec.md
- Iterates fix-review cycle until all criteria pass

This establishes a reusable pattern for DTD-conforming document validation.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: nhorton

.claude/skills/deepwork_jobs.define/SKILL.md

@@ -38,7 +38,7 @@ hooks:
 
 # deepwork_jobs.define
 
-**Step 1/3** in **deepwork_jobs** workflow
+**Step 1/4** in **deepwork_jobs** workflow
 
 > DeepWork job management commands
 
@@ -390,7 +390,7 @@ Claude: Great! Creating the job.yml specification now...
 - .deepwork/jobs/competitive_research/job.yml
 
 **Next step:**
-Run `/deepwork_jobs.implement` to generate the instruction files for each step based on this specification.
+Run `/deepwork_jobs.review_job_spec` to validate the specification against quality criteria.
 ```
 
 ## Important Guidelines
@@ -430,7 +430,7 @@ The complete YAML specification file (example shown in Step 5 above).
 After creating the file:
 1. Inform the user that the specification is complete
 2. Recommend that they review the job.yml file
-3. Tell them to run `/deepwork_jobs.implement` next
+3. Tell them to run `/deepwork_jobs.review_job_spec` next
 
 ## Quality Criteria
 
@@ -682,8 +682,8 @@ Stop hooks will automatically validate your work. The loop continues until all c
 ## On Completion
 
 1. Verify outputs are created
-2. Inform user: "Step 1/3 complete, outputs: job.yml"
-3. **Continue workflow**: Use Skill tool to invoke `/deepwork_jobs.implement`
+2. Inform user: "Step 1/4 complete, outputs: job.yml"
+3. **Continue workflow**: Use Skill tool to invoke `/deepwork_jobs.review_job_spec`
 
 ---
 

.claude/skills/deepwork_jobs.implement/SKILL.md

@@ -35,14 +35,14 @@ hooks:
 
 # deepwork_jobs.implement
 
-**Step 2/3** in **deepwork_jobs** workflow
+**Step 3/4** in **deepwork_jobs** workflow
 
 > DeepWork job management commands
 
 ## Prerequisites (Verify First)
 
 Before proceeding, confirm these steps are complete:
-- `/deepwork_jobs.define`
+- `/deepwork_jobs.review_job_spec`
 
 ## Instructions
 
@@ -52,7 +52,7 @@ Before proceeding, confirm these steps are complete:
 
 ## Objective
 
-Generate the DeepWork job directory structure and instruction files for each step based on the `job.yml` specification created in the previous step.
+Generate the DeepWork job directory structure and instruction files for each step based on the validated `job.yml` specification from the review_job_spec step.
 
 ## Task
 
@@ -82,7 +82,7 @@ touch .deepwork/jobs/[job_name]/hooks/.gitkeep .deepwork/jobs/[job_name]/templat
 ### Step 2: Read and Validate the Specification
 
 1. **Locate the job.yml file**
-   - Read `.deepwork/jobs/[job_name]/job.yml` from the define step
+   - Read `.deepwork/jobs/[job_name]/job.yml` from the review_job_spec step
    - Parse the YAML content
 
 2. **Validate the specification**
@@ -161,7 +161,7 @@ See `.deepwork/jobs/deepwork_jobs/steps/supplemental_file_references.md` for det
 
 ### Step 4: Verify job.yml Location
 
-Verify that `job.yml` is in the correct location at `.deepwork/jobs/[job_name]/job.yml`. The define step should have created it there. If for some reason it's not there, you may need to create or move it.
+Verify that `job.yml` is in the correct location at `.deepwork/jobs/[job_name]/job.yml`. The define and review_job_spec steps should have created and validated it. If for some reason it's not there, you may need to create or move it.
 
 ### Step 5: Sync Skills
 
@@ -306,7 +306,7 @@ learnings specific to the current run into AGENTS.md files in the working folder
 
 
 **Files from Previous Steps** - Read these first:
-- `job.yml` (from `define`)
+- `job.yml` (from `review_job_spec`)
 
 ## Work Branch
 
@@ -341,7 +341,7 @@ Stop hooks will automatically validate your work. The loop continues until all c
 ## On Completion
 
 1. Verify outputs are created
-2. Inform user: "Step 2/3 complete, outputs: steps/"
+2. Inform user: "Step 3/4 complete, outputs: steps/"
 3. **Continue workflow**: Use Skill tool to invoke `/deepwork_jobs.learn`
 
 ---