deepwork 0.7.0__py3-none-any.whl → 0.7.0a2__py3-none-any.whl

deepwork/__init__.py

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

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/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/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)?"

deepwork/standard_jobs/deepwork_jobs/make_new_job.sh

@@ -78,43 +78,47 @@ main() {
     mkdir -p "$job_path/steps"
     mkdir -p "$job_path/hooks"
     mkdir -p "$job_path/templates"
+    mkdir -p "$job_path/scripts"
 
     # Add .gitkeep files to empty directories
     touch "$job_path/hooks/.gitkeep"
     touch "$job_path/templates/.gitkeep"
+    touch "$job_path/scripts/.gitkeep"
 
     # Create AGENTS.md file
     cat > "$job_path/AGENTS.md" << 'EOF'
 # Job Management
 
-This folder and its subfolders are managed using the `deepwork_jobs` slash commands.
+This folder and its subfolders are managed using `deepwork_jobs` workflows.
 
-## Recommended Commands
+## Recommended Workflows
 
-- `/deepwork_jobs.define` - Create or modify the job.yml specification
-- `/deepwork_jobs.implement` - Generate step instruction files from the specification
-- `/deepwork_jobs.learn` - Improve instructions based on execution learnings
+- `deepwork_jobs/new_job` - Full lifecycle: define → implement → test → iterate
+- `deepwork_jobs/learn` - Improve instructions based on execution learnings
+- `deepwork_jobs/repair` - Clean up and migrate from prior DeepWork versions
 
 ## Directory Structure
 
 ```
 .
 ├── AGENTS.md          # This file - project context and guidance
-├── job.yml            # Job specification (created by /deepwork_jobs.define)
-├── steps/             # Step instruction files (created by /deepwork_jobs.implement)
+├── job.yml            # Job specification (created by define step)
+├── steps/             # Step instruction files (created by implement step)
 │   └── *.md           # One file per step
 ├── hooks/             # Custom validation scripts and prompts
 │   └── *.md|*.sh      # Hook files referenced in job.yml
+├── scripts/           # Reusable scripts and utilities created during job execution
+│   └── *.sh|*.py      # Helper scripts referenced in step instructions
 └── templates/         # Example file formats and templates
     └── *.md|*.yml     # Templates referenced in step instructions
 ```
 
 ## Editing Guidelines
 
-1. **Use slash commands** for structural changes (adding steps, modifying job.yml)
+1. **Use workflows** for structural changes (adding steps, modifying job.yml)
 2. **Direct edits** are fine for minor instruction tweaks
-3. **Run `/deepwork_jobs.learn`** after executing job steps to capture improvements
-4. **Run `deepwork sync`** after any changes to regenerate commands
+3. **Run `deepwork_jobs/learn`** after executing job steps to capture improvements
+4. **Run `deepwork install`** after any changes to regenerate commands
 EOF
 
     info "Created directory structure:"
@@ -122,13 +126,8 @@ EOF
     echo "  ├── AGENTS.md"
     echo "  ├── steps/"
     echo "  ├── hooks/.gitkeep"
+    echo "  ├── scripts/.gitkeep"
     echo "  └── templates/.gitkeep"
-
-    echo ""
-    info "Next steps:"
-    echo "  1. Run '/deepwork_jobs.define' to create the job.yml specification"
-    echo "  2. Run '/deepwork_jobs.implement' to generate step instructions"
-    echo "  3. Run 'deepwork sync' to create slash commands"
 }
 
 main "$@"

deepwork/standard_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/standard_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/standard_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.0.dist-info → deepwork-0.7.0a2.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: deepwork
-Version: 0.7.0
+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.0.dist-info → deepwork-0.7.0a2.dist-info}/RECORD

@@ -1,4 +1,4 @@
-deepwork/__init__.py,sha256=0Hf2rcJ94XxP2GKJUYlgAhlfagnYfpRIaqt-nM7kzgQ,748
+deepwork/__init__.py,sha256=AV8GZ4MCtUnIUSTGlzmnJPnw1nI5qgHiv80uyRX2YJ4,750
 deepwork/cli/__init__.py,sha256=3SqmfcP2xqutiCYAbajFDJTjr2pOLydqTN0NN-FTsIE,33
 deepwork/cli/hook.py,sha256=ATZJLV-J_GAHyly24lVIMvpsEY1o_-njbFrqrYg1NoM,2059
 deepwork/cli/install.py,sha256=yrtT5k8x2CgUtdvNwjPJcSbaqKblC9cF1kGspYJXjTQ,13846
@@ -23,26 +23,24 @@ deepwork/mcp/quality_gate.py,sha256=sURtwC3CaoWEZXHK_d68B__WEnyaPKIEZgPM9Hg3VQc,
 deepwork/mcp/schemas.py,sha256=IusmeXK8TMLbiuxbIaYBMQy4zBvGveDWqOi-TJpftIY,10124
 deepwork/mcp/server.py,sha256=iXw35DW9dUhXhleY0LV2yP3wbNS_aRY1uIZu9SNrSB8,9228
 deepwork/mcp/state.py,sha256=DcUt6j6zczfMTihkwDamFkHjouROCHiX31lSYZSaD0M,13721
-deepwork/mcp/tools.py,sha256=-pROXOeK1Gc7UgZ-TZH1yo49z6Rr0ZoND7yCGOZDso4,13449
+deepwork/mcp/tools.py,sha256=BOdne_pLL0ymnUIhcGma-M-zP1vNuJcdMHATmoyqgTo,13795
 deepwork/schemas/__init__.py,sha256=PpydKb_oaTv8lYapN_nV-Tl_OUCoSM_okvsEJ8gNTpI,41
 deepwork/schemas/doc_spec_schema.py,sha256=qByBtd86vQaLNsLfMr4iwVdpmyowvVLzYOnXY7RnqLY,2049
-deepwork/schemas/job.schema.json,sha256=a5gPAyoaBtVnu7U7aNa9iL2g5Bwa1S8Atjo6rD10l50,11095
+deepwork/schemas/job.schema.json,sha256=FcBuiIO3vd50oTEdohWqC_Qq8nenrJA5NH_91WPpwog,11117
 deepwork/schemas/job_schema.py,sha256=FT9Xn3Em85YEc2aTu71TGzdmunNhIztRymSG5N4vuhs,925
 deepwork/standard_jobs/deepwork_jobs/AGENTS.md,sha256=Y6I4jZ8DfN0RFY3UF5bgQRZvL7wQD9P0lgE7EZM6CGI,2252
-deepwork/standard_jobs/deepwork_jobs/job.yml,sha256=wQgbjblsDCWmaKWoBM81HuFX0aBsWtXv8c-dKTfQ-6g,12268
-deepwork/standard_jobs/deepwork_jobs/make_new_job.sh,sha256=JArfFU9lEaJPRsXRL3rU1IMt2p6Bq0s2C9f98aJ7Mxg,3878
-deepwork/standard_jobs/deepwork_jobs/doc_specs/job_spec.md,sha256=n9s70pSOjG1p6YX_72-TZ16pKIHaljeM2LnwOlrAfo0,7317
-deepwork/standard_jobs/deepwork_jobs/steps/define.md,sha256=K0eKBDze7CKwC8uKBwTOXLT7Ya46g3GdGxyqyn3CfVI,19856
-deepwork/standard_jobs/deepwork_jobs/steps/errata.md,sha256=1SjLCLc8xHlxGzFXZHn9Ch2tDTxZOyKKQ-B7RI651jw,4807
+deepwork/standard_jobs/deepwork_jobs/job.yml,sha256=Ul7lQU6AKbfTbnO5JfXGhRmO4NfJjQbVdyOlxo-Isds,11463
+deepwork/standard_jobs/deepwork_jobs/make_new_job.sh,sha256=zKgoqvGagPD5tTHka9gNcaeZxeOAa-ln96NuSvCPvzw,3881
+deepwork/standard_jobs/deepwork_jobs/steps/define.md,sha256=1UesrrPiRfPNJSqQeyfPRlAg4HS294EdoINsYG-xZTc,16523
+deepwork/standard_jobs/deepwork_jobs/steps/errata.md,sha256=3ZA2bTGGXwkcXqmB_HoFyjwvW4vf_ve-QEcM5Pllad8,5475
 deepwork/standard_jobs/deepwork_jobs/steps/fix_jobs.md,sha256=OHFX1ZuBjo_gWyFfC_HICay6J6eNZrm2IxzGT3IPxec,6074
 deepwork/standard_jobs/deepwork_jobs/steps/fix_settings.md,sha256=SJqeO_wuxcr7IzwFSlf3CmZ5ILivbvQK8YyYUc-FD4E,5361
 deepwork/standard_jobs/deepwork_jobs/steps/implement.md,sha256=6RVnS5sJpyrtGFhti5c2Dfzy6obvGJHWPHe3Hrc9SbM,5731
 deepwork/standard_jobs/deepwork_jobs/steps/iterate.md,sha256=JQkP-RMlbsnLpA3YH_yULUgHTOQx2ilSqI2gRsjPBhc,8405
-deepwork/standard_jobs/deepwork_jobs/steps/learn.md,sha256=moPKLTtYK4TGMTWmBKZO-OX__l52Cri3B6ecMoFB9kM,11630
+deepwork/standard_jobs/deepwork_jobs/steps/learn.md,sha256=1gF9t4QcyWxLWk9OzX4S6vDOu6CCOXDOI3kxCs3r1AE,9325
 deepwork/standard_jobs/deepwork_jobs/steps/supplemental_file_references.md,sha256=uKDEwB3TxMLK-Zim3QQfkvaW5W6AVWHjWnH25aY6wCw,1478
 deepwork/standard_jobs/deepwork_jobs/steps/test.md,sha256=MNoVqo9CC-lnvWvllkOtIRopHvYMSR8yJrMZa02x1i0,6816
 deepwork/standard_jobs/deepwork_jobs/templates/agents.md.template,sha256=SUJL862C6-DnT9lK3sNIZ5T2wVgXN4YRph4FrKtFnLo,739
-deepwork/standard_jobs/deepwork_jobs/templates/doc_spec.md.template,sha256=OXpkFTsEm4CVkJQmx7f6rUZ9My5rHeY_ncaygARjEpA,764
 deepwork/standard_jobs/deepwork_jobs/templates/job.yml.example,sha256=roRi6sIGFGmPCkoVW26HfuTBjAO8-pPsxI5-Gfg3rc0,2361
 deepwork/standard_jobs/deepwork_jobs/templates/job.yml.template,sha256=rlanRupKN73XUR48nF93Mm4pdL35Wa4IeZSKQs7QEWo,1912
 deepwork/standard_jobs/deepwork_jobs/templates/step_instruction.md.example,sha256=HXcjVaQz2HsDiA4ClnIeLvysVOGrFJ_5Tr-pm6dhdwc,2706
@@ -57,8 +55,8 @@ deepwork/utils/fs.py,sha256=TbkcGGqck4lborFerbBLrpVMDUz3E5ZaW6X0_B2t76k,4821
 deepwork/utils/git.py,sha256=J4tAB1zE6-WMAEHbarevhmSvvPLkeKBpiRv1UxUVwYk,3748
 deepwork/utils/validation.py,sha256=SyFg9fIu1JCDMbssQgJRCTUNToDNcINccn8lje-tjts,851
 deepwork/utils/yaml_utils.py,sha256=INHhOmzC38fh7HYKLrq7vmS3dcuNsigH7_U71erS-hw,3127
-deepwork-0.7.0.dist-info/METADATA,sha256=DXJFmPAwoz51ydikLv-kQEiKFf6NOFeeqr0oxeAeb3k,12368
-deepwork-0.7.0.dist-info/WHEEL,sha256=WLgqFyCfm_KASv4WHyYy0P3pM_m7J5L9k2skdKLirC8,87
-deepwork-0.7.0.dist-info/entry_points.txt,sha256=RhJBySzm619kh-yIdsAyfFXInAlY8Jm-39FLIBcOj2s,51
-deepwork-0.7.0.dist-info/licenses/LICENSE.md,sha256=W0EtJVYf0cQ_awukOCW1ETwNSpV2RKqnAGfoOjyz_K8,4126
-deepwork-0.7.0.dist-info/RECORD,,
+deepwork-0.7.0a2.dist-info/METADATA,sha256=24BEzKTwedhl5kQSEnle1BWoBXssLFtYoc7yQpjYOCM,12370
+deepwork-0.7.0a2.dist-info/WHEEL,sha256=WLgqFyCfm_KASv4WHyYy0P3pM_m7J5L9k2skdKLirC8,87
+deepwork-0.7.0a2.dist-info/entry_points.txt,sha256=RhJBySzm619kh-yIdsAyfFXInAlY8Jm-39FLIBcOj2s,51
+deepwork-0.7.0a2.dist-info/licenses/LICENSE.md,sha256=W0EtJVYf0cQ_awukOCW1ETwNSpV2RKqnAGfoOjyz_K8,4126
+deepwork-0.7.0a2.dist-info/RECORD,,

deepwork/standard_jobs/deepwork_jobs/doc_specs/job_spec.md

@@ -1,184 +0,0 @@
----
-name: "DeepWork Job Specification"
-description: "YAML specification file that defines a multi-step workflow job for AI agents"
-path_patterns:
-  - ".deepwork/jobs/*/job.yml"
-target_audience: "AI agents executing jobs and developers defining workflows"
-frequency: "Created once per job, updated as workflow evolves"
-quality_criteria:
-  - name: Valid Identifier
-    description: "Job name must be lowercase with underscores, no spaces or special characters (e.g., `competitive_research`, `monthly_report`)"
-  - name: Semantic Version
-    description: "Version must follow semantic versioning format X.Y.Z (e.g., `1.0.0`, `2.1.3`)"
-  - name: Concise Summary
-    description: "Summary must be under 200 characters and clearly describe what the job accomplishes"
-  - name: Rich Description
-    description: "Description must be multi-line and explain: the problem solved, the process, expected outcomes, and target users"
-  - name: Changelog Present
-    description: "Must include a changelog array with at least the initial version entry. Changelog should only include one entry per branch at most"
-  - name: Complete Steps
-    description: "Each step must have: id (lowercase_underscores), name, description, instructions_file, outputs (at least one), and dependencies array"
-  - name: Valid Dependencies
-    description: "Dependencies must reference existing step IDs with no circular references"
-  - name: Input Consistency
-    description: "File inputs with `from_step` must reference a step that is in the dependencies array"
-  - name: Output Paths
-    description: "Outputs must be valid filenames or paths within the main repo directory structure, never in dot-directories like `.deepwork/`. Use specific, descriptive paths that lend themselves to glob patterns (e.g., `competitive_research/acme_corp/swot.md` or `operations/reports/2026-01/spending_analysis.md`). Parameterized paths like `[competitor_name]/` are encouraged for per-entity outputs. Avoid generic names (`output.md`, `analysis.md`) and transient-sounding paths (`temp/`, `draft.md`). Supporting materials for a final output should go in a peer `_dataroom` folder (e.g., `spending_analysis_dataroom/`)."
-  - name: Concise Instructions
-    description: "The content of the file, particularly the description, must not have excessively redundant information. It should be concise and to the point given that extra tokens will confuse the AI."
----
-
-# DeepWork Job Specification: [job_name]
-
-A `job.yml` file defines a complete multi-step workflow that AI agents can execute. Each job breaks down a complex task into reviewable steps with clear inputs and outputs.
-
-## Required Fields
-
-### Top-Level Metadata
-
-```yaml
-name: job_name                    # lowercase, underscores only
-version: "1.0.0"                  # semantic versioning
-summary: "Brief description"      # max 200 characters
-description: |                    # detailed multi-line explanation
-  [Explain what this workflow does, why it exists,
-  what outputs it produces, and who should use it]
-```
-
-### Changelog
-
-```yaml
-changelog:
-  - version: "1.0.0"
-    changes: "Initial job creation"
-  - version: "1.1.0"
-    changes: "Added quality validation hooks"
-```
-
-### Steps Array
-
-```yaml
-steps:
-  - id: step_id                   # unique, lowercase_underscores
-    name: "Human Readable Name"
-    description: "What this step accomplishes"
-    instructions_file: steps/step_id.md
-    inputs:
-      # User-provided inputs:
-      - name: param_name
-        description: "What the user provides"
-      # File inputs from previous steps:
-      - file: output.md
-        from_step: previous_step_id
-    outputs:
-      - competitive_research/competitors_list.md           # descriptive path
-      - competitive_research/[competitor_name]/research.md # parameterized path
-      # With doc spec reference:
-      - file: competitive_research/final_report.md
-        doc_spec: .deepwork/doc_specs/report_type.md
-    dependencies:
-      - previous_step_id          # steps that must complete first
-```
-
-## Optional Fields
-
-### Agent Delegation
-
-When a step should be executed by a specific agent type, use the `agent` field. This automatically sets `context: fork` in the generated skill.
-
-```yaml
-steps:
-  - id: research_step
-    agent: general-purpose        # Delegates to the general-purpose agent
-```
-
-Available agent types:
-- `general-purpose` - Standard agent for multi-step tasks
-
-### Quality Hooks
-
-```yaml
-steps:
-  - id: step_id
-    hooks:
-      after_agent:
-        # Inline prompt for quality validation:
-        - prompt: |
-            Verify the output meets criteria:
-            1. [Criterion 1]
-            2. [Criterion 2]
-            If ALL criteria are met, include `<promise>...</promise>`.
-        # External prompt file:
-        - prompt_file: hooks/quality_check.md
-        # Script for programmatic validation:
-        - script: hooks/run_tests.sh
-```
-
-## Validation Rules
-
-1. **No circular dependencies**: Step A cannot depend on Step B if Step B depends on Step A
-2. **File inputs require dependencies**: If a step uses `from_step: X`, then X must be in its dependencies
-3. **Unique step IDs**: No two steps can have the same id
-4. **Valid file paths**: Output paths must not contain invalid characters and should be in the main repo (not dot-directories)
-5. **Instructions files exist**: Each `instructions_file` path should have a corresponding file created
-
-## Example: Complete Job Specification
-
-```yaml
-name: competitive_research
-version: "1.0.0"
-summary: "Systematic competitive analysis workflow"
-description: |
-  A comprehensive workflow for analyzing competitors in your market segment.
-  Helps product teams understand the competitive landscape through systematic
-  identification, research, comparison, and positioning recommendations.
-
-  Produces:
-  - Vetted competitor list
-  - Research notes per competitor
-  - Comparison matrix
-  - Strategic positioning report
-
-changelog:
-  - version: "1.0.0"
-    changes: "Initial job creation"
-
-steps:
-  - id: identify_competitors
-    name: "Identify Competitors"
-    description: "Identify 5-7 key competitors in the target market"
-    instructions_file: steps/identify_competitors.md
-    inputs:
-      - name: market_segment
-        description: "The market segment to analyze"
-      - name: product_category
-        description: "The product category"
-    outputs:
-      - competitive_research/competitors_list.md
-    dependencies: []
-
-  - id: research_competitors
-    name: "Research Competitors"
-    description: "Deep dive research on each identified competitor"
-    instructions_file: steps/research_competitors.md
-    inputs:
-      - file: competitive_research/competitors_list.md
-        from_step: identify_competitors
-    outputs:
-      - competitive_research/[competitor_name]/research.md
-    dependencies:
-      - identify_competitors
-
-  - id: positioning_report
-    name: "Positioning Report"
-    description: "Strategic positioning recommendations"
-    instructions_file: steps/positioning_report.md
-    inputs:
-      - file: competitive_research/[competitor_name]/research.md
-        from_step: research_competitors
-    outputs:
-      - file: competitive_research/positioning_report.md
-        doc_spec: .deepwork/doc_specs/positioning_report.md
-    dependencies:
-      - research_competitors
-```

deepwork/standard_jobs/deepwork_jobs/templates/doc_spec.md.template

@@ -1,26 +0,0 @@
----
-name: "[Document Name]"
-description: "[Brief description of the document's purpose]"
-path_patterns:
-  - "[path/to/documents/*.md]"
-target_audience: "[Who reads this document]"
-frequency: "[How often produced, e.g., Monthly, Per sprint, On demand]"
-quality_criteria:
-  - name: "[Criterion Name]"
-    description: "[What this criterion requires - be specific]"
-  - name: "[Criterion Name]"
-    description: "[What this criterion requires - be specific]"
-  - name: "[Criterion Name]"
-    description: "[What this criterion requires - be specific]"
----
-
-# [Document Title]: [Variables like Month, Year, Sprint]
-
-## Section 1
-[Describe what goes in this section]
-
-## Section 2
-[Describe what goes in this section]
-
-## Section 3
-[Describe what goes in this section]