deepwork 0.7.0a1__tar.gz → 0.7.0a2__tar.gz

{deepwork-0.7.0a1/src/deepwork/standard_jobs → deepwork-0.7.0a2/.deepwork/jobs}/deepwork_jobs/job.yml

@@ -58,12 +58,6 @@ changelog:
     changes: "Removed implementation_summary and learning_summary outputs; simplified step outputs"
   - version: "0.5.0"
     changes: "Standardized on 'ask structured questions' phrasing for user input; Updated quality criteria hooks to verify phrase usage; Added guidance in implement.md to use phrase in generated instructions"
-  - version: "0.6.0"
-    changes: "Added doc spec support; define.md now detects document-oriented workflows and guides doc spec creation; learn.md now identifies and applies doc spec-related improvements"
-  - version: "0.7.0"
-    changes: "Added job.yml doc spec; define step now outputs job.yml with doc_spec reference for quality validation"
-  - version: "0.8.0"
-    changes: "Added review_job_spec step between define and implement for doc spec-based quality validation using sub-agent review"
   - version: "0.9.0"
     changes: "Improved skill descriptions with third-person voice and 'Use when...' triggers for better discoverability"
 
@@ -76,8 +70,7 @@ steps:
       - name: job_purpose
         description: "What complex task or workflow are you trying to accomplish?"
     outputs:
-      - file: job.yml
-        doc_spec: .deepwork/doc_specs/job_spec.md
+      - job.yml
     dependencies: []
   - id: implement
     name: "Implement Job Steps"
@@ -158,8 +151,6 @@ steps:
       - "**Instructions Improved**: Were job instructions updated to address identified issues?"
       - "**Instructions Concise**: Are instructions free of redundancy and unnecessary verbosity?"
       - "**Shared Content Extracted**: Is lengthy/duplicated content extracted into referenced files?"
-      - "**doc spec Reviewed (if applicable)**: For jobs with doc spec outputs, were doc spec-related learnings identified?"
-      - "**doc spec Updated (if applicable)**: Were doc spec files updated with improved quality criteria or structure?"
       - "**Bespoke Learnings Captured**: Were run-specific learnings added to AGENTS.md?"
       - "**File References Used**: Do AGENTS.md entries reference other files where appropriate?"
       - "**Working Folder Correct**: Is AGENTS.md in the correct working folder for the job?"
@@ -206,11 +197,10 @@ steps:
     name: "Clean Up Errata"
     description: "Removes obsolete files and folders from prior DeepWork versions, including old skill directories, temp files, and deprecated configurations."
     instructions_file: steps/errata.md
+    outputs: []
     inputs:
       - file: .deepwork/jobs/
         from_step: fix_jobs
-    outputs:
-      - repair_summary.md
     dependencies:
       - fix_settings
       - fix_jobs
@@ -221,5 +211,5 @@ steps:
       - "**Rules Folder Removed**: Is `.deepwork/rules/` folder backed up and removed (fully deprecated)?"
       - "**Rules Job Removed**: Is `.deepwork/jobs/deepwork_rules/` removed if present?"
       - "**Config Version Updated**: Is `.deepwork/config.yml` using current version format?"
-      - "**Summary Provided**: Is a repair_summary.md file created documenting all changes made?"
+      - "**DeepWork Re-installed**: Was `deepwork install` run after cleanup, and does it complete without errors?"
       - "**Git Status Clean**: Are changes ready to be committed (no untracked garbage files)?"

{deepwork-0.7.0a1 → deepwork-0.7.0a2}/.deepwork/jobs/deepwork_jobs/steps/define.md

@@ -31,60 +31,6 @@ Start by asking structured questions to understand what the user wants to accomp
    - What are the distinct stages from start to finish?
    - Are there any dependencies between phases?
 
-### Step 1.5: Detect Document-Oriented Workflows
-
-**Check for document-focused patterns** in the user's description:
-- Keywords: "report", "summary", "document", "create", "monthly", "quarterly", "for stakeholders", "for leadership"
-- Final deliverable is a specific document (e.g., "AWS spending report", "competitive analysis", "sprint summary")
-- Recurring documents with consistent structure
-
-**If a document-oriented workflow is detected:**
-
-1. Inform the user: "This workflow produces a specific document type. I recommend defining a doc spec first to ensure consistent quality."
-
-2. Ask structured questions to understand if they want to:
-   - Create a doc spec for this document
-   - Use an existing doc spec (if any exist in `.deepwork/doc_specs/`)
-   - Skip doc spec and proceed with simple outputs
-
-### Step 1.6: Define the Doc Spec (if needed)
-
-When creating a doc spec, gather the following information:
-
-1. **Document Identity**
-   - What is the document called? (e.g., "Monthly AWS Spending Report")
-   - Brief description of its purpose
-   - Where should these documents be stored? (path patterns like `finance/aws-reports/*.md`)
-
-2. **Audience and Context**
-   - Who reads this document? (target audience)
-   - How often is it produced? (frequency)
-
-3. **Quality Criteria** (3-5 criteria, each with name and description)
-
-   **Important**: Doc spec quality criteria define requirements for the **output document itself**, not the process of creating it. Focus on what the finished document must contain or achieve.
-
-   Examples for a spending report:
-   - **Visualization**: Must include charts showing spend breakdown by service
-   - **Variance Analysis**: Must compare current month against previous with percentages
-   - **Action Items**: Must include recommended cost optimization actions
-
-   **Note**: When a doc spec is created for a step's output, the step should generally NOT have separate `quality_criteria` in the job.yml. The doc spec's criteria cover output quality. Only add step-level quality_criteria if there are essential process requirements (e.g., "must use specific tool"), and minimize these when possible.
-
-4. **Document Structure**
-   - What sections should it have?
-   - Any required elements (tables, charts, summaries)?
-
-### Step 1.7: Create the doc spec File (if needed)
-
-Create the doc spec file at `.deepwork/doc_specs/[doc_spec_name].md`:
-
-**Template reference**: See `.deepwork/jobs/deepwork_jobs/templates/doc_spec.md.template` for the standard structure.
-
-**Complete example**: See `.deepwork/doc_specs/job_spec.md` for a fully worked example (the doc spec for job.yml files).
-
-After creating the doc spec, proceed to Step 2 with the doc spec reference for the final step's output.
-
 ### Step 2: Define Each Step
 
 For each major phase they mentioned, ask structured questions to gather details:
@@ -106,8 +52,6 @@ For each major phase they mentioned, ask structured questions to gather details:
    - Where should each output be saved? (filename/path)
    - Should outputs be organized in subdirectories? (e.g., `reports/`, `data/`, `drafts/`)
    - Will other steps need this output?
-   - **Does this output have a doc spec?** If a doc spec was created in Step 1.6/1.7, reference it for the appropriate output
-
    #### Work Product Storage Guidelines
 
    **Key principle**: Job outputs belong in the main repository directory structure, not in dot-directories. The `.deepwork/` directory is for job definitions and configuration only.
@@ -189,18 +133,6 @@ For each major phase they mentioned, ask structured questions to gather details:
 
 **Note**: You're gathering this information to understand what instructions will be needed, but you won't create the instruction files yet - that happens in the `implement` step.
 
-#### Doc Spec-Aware Output Format
-
-When a step produces a document with a doc spec reference, use this format in job.yml:
-
-```yaml
-outputs:
-  - file: reports/monthly_spending.md
-    doc_spec: .deepwork/doc_specs/monthly_aws_report.md
-```
-
-The doc spec's quality criteria will automatically be included in the generated skill, ensuring consistent document quality.
-
 ### Capability Considerations
 
 When defining steps, identify any that require specialized tools:
@@ -299,8 +231,6 @@ This creates:
 
 (Where `[job_name]` is the name of the NEW job you're creating, e.g., `competitive_research`)
 
-**Doc Spec**: See `.deepwork/doc_specs/job_spec.md` for the complete specification with quality criteria.
-
 **Template reference**: See `.deepwork/jobs/deepwork_jobs/templates/job.yml.template` for the standard structure.
 
 **Complete example**: See `.deepwork/jobs/deepwork_jobs/templates/job.yml.example` for a fully worked example.

{deepwork-0.7.0a1/src/deepwork/standard_jobs → deepwork-0.7.0a2/.deepwork/jobs}/deepwork_jobs/steps/errata.md

@@ -134,7 +134,23 @@ Check for and remove other obsolete files:
 | `.claude/commands/` | Generated commands | Keep (current system) |
 | `.claude/settings.local.json` | Local overrides | Keep (user settings) |
 
-### Step 6: Verify Git Status
+### Step 6: Re-install DeepWork
+
+After all cleanup is complete, re-run `deepwork install` to ensure configurations are current and consistent:
+
+```bash
+deepwork install
+```
+
+**Then verify:**
+1. Check that `.deepwork/config.yml` is valid and up to date
+2. Check that `.claude/skills/deepwork/` exists and contains the expected skill entry point
+3. Check that all jobs in `.deepwork/jobs/` have valid `job.yml` files
+4. Run `deepwork install` a second time and confirm the output is clean (no errors or warnings)
+
+If any issues are found, fix them before proceeding. The goal is a clean, working DeepWork installation with no residual problems from the repair process.
+
+### Step 7: Verify Git Status
 
 Check that the cleanup hasn't left untracked garbage:
 

{deepwork-0.7.0a1 → deepwork-0.7.0a2}/.deepwork/jobs/deepwork_jobs/steps/learn.md

@@ -66,15 +66,6 @@ For each learning identified, determine if it is:
   - "Quality criteria should include checking for Y"
   - "Add example of correct output format"
 
-**doc spec-Related** (should improve doc spec files):
-- Improvements to document quality criteria
-- Changes to document structure or format
-- Updated audience or frequency information
-- Examples:
-  - "The report should include a summary table"
-  - "Quality criterion 'Visualization' needs clearer requirements"
-  - "Documents need a section for action items"
-
 **Bespoke** (should go in AGENTS.md):
 - Specific to THIS project/codebase/run
 - Depends on local conventions or structure
@@ -85,30 +76,6 @@ For each learning identified, determine if it is:
   - "This project uses camelCase for function names"
   - "The main config file is at `config/settings.yml`"
 
-### Step 3.5: Identify doc spec-Related Learnings
-
-Review the conversation for doc spec-related improvements:
-
-1. **Quality Criteria Changes**
-   - Were any quality criteria unclear or insufficient?
-   - Did the agent repeatedly fail certain criteria?
-   - Are there new criteria that should be added?
-
-2. **Document Structure Changes**
-   - Did the user request different sections?
-   - Were parts of the document format confusing?
-   - Should the example document be updated?
-
-3. **Metadata Updates**
-   - Has the target audience changed?
-   - Should frequency or path patterns be updated?
-
-**Signals for doc spec improvements:**
-- User asked for changes to document format
-- Repeated validation failures on specific criteria
-- Feedback about missing sections or information
-- Changes to how documents are organized/stored
-
 ### Step 4: Update Job Instructions (Generalizable Learnings)
 
 For each generalizable learning:
@@ -162,41 +129,6 @@ Review all instruction files for the job and identify content that:
    - Shorter instruction files - easier to read and maintain
    - Consistent guidance across steps
 
-### Step 4.5: Update doc spec Files (doc spec-Related Learnings)
-
-If doc spec-related learnings were identified:
-
-1. **Locate the doc spec file**
-   - Find doc spec references in job.yml outputs (look for `doc_spec: .deepwork/doc_specs/[doc_spec_name].md`)
-   - doc spec files are at `.deepwork/doc_specs/[doc_spec_name].md`
-
-2. **Update quality_criteria array**
-   - Add new criteria with name and description
-   - Modify existing criteria descriptions for clarity
-   - Remove criteria that are no longer relevant
-
-3. **Update example document**
-   - Modify the markdown body to reflect structure changes
-   - Ensure the example matches updated criteria
-
-4. **Update metadata as needed**
-   - target_audience: If audience has changed
-   - frequency: If production cadence has changed
-   - path_patterns: If storage location has changed
-
-**Example doc spec update:**
-```yaml
-# Before
-quality_criteria:
-  - name: Visualization
-    description: Include charts
-
-# After
-quality_criteria:
-  - name: Visualization
-    description: Include Mermaid.js charts showing spend breakdown by service and month-over-month trend
-```
-
 ### Step 5: Create/Update AGENTS.md (Bespoke Learnings)
 
 The AGENTS.md file captures project-specific knowledge that helps future agent runs.

{deepwork-0.7.0a1 → deepwork-0.7.0a2}/.deepwork/schemas/job.schema.json

@@ -150,8 +150,7 @@
         },
         "outputs": {
           "type": "array",
-          "minItems": 1,
-          "description": "List of output files/directories produced by this step",
+          "description": "List of output files/directories produced by this step. May be empty for cleanup or validation steps.",
           "items": {
             "$ref": "#/$defs/stepOutput"
           }

{deepwork-0.7.0a1 → deepwork-0.7.0a2}/CONTRIBUTING.md

@@ -7,6 +7,7 @@ Thank you for your interest in contributing to DeepWork! This guide will help yo
 - [Prerequisites](#prerequisites)
 - [Development Setup](#development-setup)
 - [Installing DeepWork Locally](#installing-deepwork-locally)
+- [Installing Pre-Release Versions](#installing-pre-release-versions)
 - [Testing Your Local Installation](#testing-your-local-installation)
 - [Running Tests](#running-tests)
 - [Code Quality](#code-quality)
@@ -240,6 +241,32 @@ which deepwork  # Should point to .venv/bin/deepwork
 deepwork --version
 ```
 
+## Installing Pre-Release Versions
+
+DeepWork uses pre-release versions (e.g., `0.7.0a1`) during development. By default, `uv` and `pip` skip pre-release versions, so you need to opt in explicitly.
+
+### With uv
+
+```bash
+# Install the latest pre-release from PyPI
+uv pip install --prerelease=allow deepwork
+
+# Or pin to a specific pre-release
+uv pip install --prerelease=allow "deepwork==0.7.0a1"
+```
+
+### With pip
+
+```bash
+pip install --pre deepwork
+```
+
+### With uv tool install (global CLI)
+
+```bash
+uv tool install --prerelease=allow deepwork
+```
+
 ## Testing Your Local Installation
 
 To test your local DeepWork installation in a real project:

{deepwork-0.7.0a1 → deepwork-0.7.0a2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: deepwork
-Version: 0.7.0a1
+Version: 0.7.0a2
 Summary: Framework for enabling AI agents to perform complex, multi-step work tasks
 Project-URL: Homepage, https://github.com/deepwork/deepwork
 Project-URL: Documentation, https://github.com/deepwork/deepwork#readme

{deepwork-0.7.0a1 → deepwork-0.7.0a2}/doc/mcp_interface.md

@@ -65,7 +65,7 @@ Start a new workflow session. Creates a git branch, initializes state tracking,
 |-----------|------|----------|-------------|
 | `goal` | `string` | Yes | What the user wants to accomplish |
 | `job_name` | `string` | Yes | Name of the job |
-| `workflow_name` | `string` | Yes | Name of the workflow within the job |
+| `workflow_name` | `string` | Yes | Name of the workflow within the job. If the name doesn't match but the job has only one workflow, that workflow is selected automatically. If the job has multiple workflows, an error is returned listing the available workflow names. |
 | `instance_id` | `string \| null` | No | Optional identifier for naming (e.g., 'acme', 'q1-2026') |
 
 #### Returns

{deepwork-0.7.0a1 → deepwork-0.7.0a2}/flake.lock

@@ -1,6 +1,59 @@
 {
   "nodes": {
+    "claude-code-nix": {
+      "inputs": {
+        "flake-utils": "flake-utils",
+        "nixpkgs": "nixpkgs"
+      },
+      "locked": {
+        "lastModified": 1770315205,
+        "narHash": "sha256-yOYprNUvMHRBC7EfmhNOYYLqNm43cLtydV39ITnCfZk=",
+        "owner": "sadjow",
+        "repo": "claude-code-nix",
+        "rev": "b774ffcdcd9987f4a2e6e3809130d04438e29a13",
+        "type": "github"
+      },
+      "original": {
+        "owner": "sadjow",
+        "repo": "claude-code-nix",
+        "type": "github"
+      }
+    },
+    "flake-utils": {
+      "inputs": {
+        "systems": "systems"
+      },
+      "locked": {
+        "lastModified": 1731533236,
+        "narHash": "sha256-l0KFg5HjrsfsO/JpG+r7fRrqm12kzFHyUHqHCVpMMbI=",
+        "owner": "numtide",
+        "repo": "flake-utils",
+        "rev": "11707dc2f618dd54ca8739b309ec4fc024de578b",
+        "type": "github"
+      },
+      "original": {
+        "owner": "numtide",
+        "repo": "flake-utils",
+        "type": "github"
+      }
+    },
     "nixpkgs": {
+      "locked": {
+        "lastModified": 1770169770,
+        "narHash": "sha256-awR8qIwJxJJiOmcEGgP2KUqYmHG4v/z8XpL9z8FnT1A=",
+        "owner": "NixOS",
+        "repo": "nixpkgs",
+        "rev": "aa290c9891fa4ebe88f8889e59633d20cc06a5f2",
+        "type": "github"
+      },
+      "original": {
+        "owner": "NixOS",
+        "ref": "nixpkgs-unstable",
+        "repo": "nixpkgs",
+        "type": "github"
+      }
+    },
+    "nixpkgs_2": {
       "locked": {
         "lastModified": 1770197578,
         "narHash": "sha256-AYqlWrX09+HvGs8zM6ebZ1pwUqjkfpnv8mewYwAo+iM=",
@@ -64,12 +117,28 @@
     },
     "root": {
       "inputs": {
-        "nixpkgs": "nixpkgs",
+        "claude-code-nix": "claude-code-nix",
+        "nixpkgs": "nixpkgs_2",
         "pyproject-build-systems": "pyproject-build-systems",
         "pyproject-nix": "pyproject-nix",
         "uv2nix": "uv2nix"
       }
     },
+    "systems": {
+      "locked": {
+        "lastModified": 1681028828,
+        "narHash": "sha256-Vy1rq5AaRuLzOxct8nz4T6wlgyUR7zLU309k9mBC768=",
+        "owner": "nix-systems",
+        "repo": "default",
+        "rev": "da67096a3b9bf56a91d16901293e51ba5b49a27e",
+        "type": "github"
+      },
+      "original": {
+        "owner": "nix-systems",
+        "repo": "default",
+        "type": "github"
+      }
+    },
     "uv2nix": {
       "inputs": {
         "nixpkgs": [

{deepwork-0.7.0a1 → deepwork-0.7.0a2}/flake.nix

@@ -4,6 +4,9 @@
   inputs = {
     nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
 
+    # Claude Code with pre-built native binaries (hourly updates)
+    claude-code-nix.url = "github:sadjow/claude-code-nix";
+
     pyproject-nix = {
       url = "github:pyproject-nix/pyproject.nix";
       inputs.nixpkgs.follows = "nixpkgs";
@@ -23,7 +26,7 @@
     };
   };
 
-  outputs = { self, nixpkgs, pyproject-nix, uv2nix, pyproject-build-systems, ... }:
+  outputs = { self, nixpkgs, claude-code-nix, pyproject-nix, uv2nix, pyproject-build-systems, ... }:
     let
       inherit (nixpkgs) lib;
 
@@ -64,9 +67,6 @@
             config.allowUnfree = true;
           };
 
-          # Local claude-code package (update via nix/claude-code/update.sh)
-          claude-code = pkgs.callPackage ./nix/claude-code/package.nix { };
-
           # Python set with editable overlay for development
           pythonSet = pythonSets.${system}.overrideScope editableOverlay;
 
@@ -80,7 +80,7 @@
               pkgs.uv
               pkgs.git
               pkgs.jq
-              claude-code
+              claude-code-nix.packages.${system}.default
               pkgs.gh
             ];
 
@@ -97,9 +97,6 @@
               unset PYTHONPATH
               export REPO_ROOT=$(git rev-parse --show-toplevel)
 
-              # Add nix/ scripts to PATH (for 'update' command)
-              export PATH="$PWD/nix:$PATH"
-
               # Only show welcome message in interactive shells
               if [[ $- == *i* ]]; then
                 echo ""
@@ -113,9 +110,8 @@
                 echo "  pytest             Run tests"
                 echo "  ruff check src/    Lint code"
                 echo "  mypy src/          Type check"
-                echo "  claude-code        Claude Code CLI"
+                echo "  claude             Claude Code CLI"
                 echo "  gh                 GitHub CLI"
-                echo "  update             Update claude-code and flake inputs"
                 echo ""
               fi
             '';

{deepwork-0.7.0a1 → deepwork-0.7.0a2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "deepwork"
-version = "0.7.0a1"
+version = "0.7.0a2"
 description = "Framework for enabling AI agents to perform complex, multi-step work tasks"
 readme = "README.md"
 requires-python = ">=3.11"

{deepwork-0.7.0a1 → deepwork-0.7.0a2}/src/deepwork/__init__.py

@@ -1,6 +1,6 @@
 """DeepWork - Framework for enabling AI agents to perform complex, multi-step work tasks."""
 
-__version__ = "0.7.0a1"
+__version__ = "0.7.0a2"
 __author__ = "DeepWork Contributors"
 
 __all__ = [

{deepwork-0.7.0a1 → deepwork-0.7.0a2}/src/deepwork/mcp/tools.py

@@ -132,6 +132,9 @@ class WorkflowTools:
     def _get_workflow(self, job: JobDefinition, workflow_name: str) -> Workflow:
         """Get a specific workflow from a job.
 
+        If the workflow name doesn't match any workflow but the job has exactly
+        one workflow, that workflow is returned automatically.
+
         Args:
             job: Job definition
             workflow_name: Workflow name to find
@@ -140,12 +143,16 @@ class WorkflowTools:
             Workflow
 
         Raises:
-            ToolError: If workflow not found
+            ToolError: If workflow not found and job has multiple workflows
         """
         for wf in job.workflows:
             if wf.name == workflow_name:
                 return wf
 
+        # Auto-select if there's only one workflow
+        if len(job.workflows) == 1:
+            return job.workflows[0]
+
         available = [wf.name for wf in job.workflows]
         raise ToolError(
             f"Workflow '{workflow_name}' not found in job '{job.name}'. "
@@ -214,10 +221,10 @@ class WorkflowTools:
         if first_step is None:
             raise ToolError(f"First step not found: {first_step_id}")
 
-        # Create session
+        # Create session (use resolved workflow name in case it was auto-selected)
         session = await self.state_manager.create_session(
             job_name=input_data.job_name,
-            workflow_name=input_data.workflow_name,
+            workflow_name=workflow.name,
             goal=input_data.goal,
             first_step_id=first_step_id,
             instance_id=input_data.instance_id,

{deepwork-0.7.0a1 → deepwork-0.7.0a2}/src/deepwork/schemas/job.schema.json

@@ -150,8 +150,7 @@
         },
         "outputs": {
           "type": "array",
-          "minItems": 1,
-          "description": "List of output files/directories produced by this step",
+          "description": "List of output files/directories produced by this step. May be empty for cleanup or validation steps.",
           "items": {
             "$ref": "#/$defs/stepOutput"
           }

{deepwork-0.7.0a1/.deepwork/jobs → deepwork-0.7.0a2/src/deepwork/standard_jobs}/deepwork_jobs/job.yml

@@ -58,12 +58,6 @@ changelog:
     changes: "Removed implementation_summary and learning_summary outputs; simplified step outputs"
   - version: "0.5.0"
     changes: "Standardized on 'ask structured questions' phrasing for user input; Updated quality criteria hooks to verify phrase usage; Added guidance in implement.md to use phrase in generated instructions"
-  - version: "0.6.0"
-    changes: "Added doc spec support; define.md now detects document-oriented workflows and guides doc spec creation; learn.md now identifies and applies doc spec-related improvements"
-  - version: "0.7.0"
-    changes: "Added job.yml doc spec; define step now outputs job.yml with doc_spec reference for quality validation"
-  - version: "0.8.0"
-    changes: "Added review_job_spec step between define and implement for doc spec-based quality validation using sub-agent review"
   - version: "0.9.0"
     changes: "Improved skill descriptions with third-person voice and 'Use when...' triggers for better discoverability"
 
@@ -76,8 +70,7 @@ steps:
       - name: job_purpose
         description: "What complex task or workflow are you trying to accomplish?"
     outputs:
-      - file: job.yml
-        doc_spec: .deepwork/doc_specs/job_spec.md
+      - job.yml
     dependencies: []
   - id: implement
     name: "Implement Job Steps"
@@ -158,8 +151,6 @@ steps:
       - "**Instructions Improved**: Were job instructions updated to address identified issues?"
       - "**Instructions Concise**: Are instructions free of redundancy and unnecessary verbosity?"
       - "**Shared Content Extracted**: Is lengthy/duplicated content extracted into referenced files?"
-      - "**doc spec Reviewed (if applicable)**: For jobs with doc spec outputs, were doc spec-related learnings identified?"
-      - "**doc spec Updated (if applicable)**: Were doc spec files updated with improved quality criteria or structure?"
       - "**Bespoke Learnings Captured**: Were run-specific learnings added to AGENTS.md?"
       - "**File References Used**: Do AGENTS.md entries reference other files where appropriate?"
       - "**Working Folder Correct**: Is AGENTS.md in the correct working folder for the job?"
@@ -206,11 +197,10 @@ steps:
     name: "Clean Up Errata"
     description: "Removes obsolete files and folders from prior DeepWork versions, including old skill directories, temp files, and deprecated configurations."
     instructions_file: steps/errata.md
+    outputs: []
     inputs:
       - file: .deepwork/jobs/
         from_step: fix_jobs
-    outputs:
-      - repair_summary.md
     dependencies:
       - fix_settings
       - fix_jobs
@@ -221,5 +211,5 @@ steps:
       - "**Rules Folder Removed**: Is `.deepwork/rules/` folder backed up and removed (fully deprecated)?"
       - "**Rules Job Removed**: Is `.deepwork/jobs/deepwork_rules/` removed if present?"
       - "**Config Version Updated**: Is `.deepwork/config.yml` using current version format?"
-      - "**Summary Provided**: Is a repair_summary.md file created documenting all changes made?"
+      - "**DeepWork Re-installed**: Was `deepwork install` run after cleanup, and does it complete without errors?"
       - "**Git Status Clean**: Are changes ready to be committed (no untracked garbage files)?"