deepwork 0.1.1__py3-none-any.whl → 0.2.0__py3-none-any.whl

deepwork/cli/install.py

@@ -113,6 +113,48 @@ def _create_deepwork_gitignore(deepwork_dir: Path) -> None:
         gitignore_path.write_text(gitignore_content)
 
 
+def _create_default_policy_file(project_path: Path) -> bool:
+    """
+    Create a default policy file template in the project root.
+
+    Only creates the file if it doesn't already exist.
+
+    Args:
+        project_path: Path to the project root
+
+    Returns:
+        True if the file was created, False if it already existed
+    """
+    policy_file = project_path / ".deepwork.policy.yml"
+
+    if policy_file.exists():
+        return False
+
+    # Copy the template from the templates directory
+    template_path = Path(__file__).parent.parent / "templates" / "default_policy.yml"
+
+    if template_path.exists():
+        shutil.copy(template_path, policy_file)
+    else:
+        # Fallback: create a minimal template inline
+        policy_file.write_text(
+            """# DeepWork Policy Configuration
+#
+# Policies are automated guardrails that trigger when specific files change.
+# Use /deepwork_policy.define to create new policies interactively.
+#
+# Format:
+#   - name: "Policy name"
+#     trigger: "glob/pattern/**/*"
+#     safety: "optional/pattern/**/*"
+#     instructions: |
+#       Instructions for the AI agent...
+"""
+        )
+
+    return True
+
+
 class DynamicChoice(click.Choice):
     """A Click Choice that gets its values dynamically from AgentAdapter."""
 
@@ -238,6 +280,12 @@ def _install_deepwork(platform_name: str | None, project_path: Path) -> None:
     _create_deepwork_gitignore(deepwork_dir)
     console.print("  [green]✓[/green] Created .deepwork/.gitignore")
 
+    # Step 3d: Create default policy file template
+    if _create_default_policy_file(project_path):
+        console.print("  [green]✓[/green] Created .deepwork.policy.yml template")
+    else:
+        console.print("  [dim]•[/dim] .deepwork.policy.yml already exists")
+
     # Step 4: Load or create config.yml
     console.print("[yellow]→[/yellow] Updating configuration...")
     config_file = deepwork_dir / "config.yml"

deepwork/standard_jobs/deepwork_jobs/AGENTS.md

@@ -0,0 +1,60 @@
+# Project Context for deepwork_jobs
+
+This is the source of truth for the `deepwork_jobs` standard job.
+
+## Codebase Structure
+
+- Source location: `src/deepwork/standard_jobs/deepwork_jobs/`
+- Working copy: `.deepwork/jobs/deepwork_jobs/`
+- Templates: `templates/` directory within each location
+
+## Dual Location Maintenance
+
+**Important**: This job exists in two locations that must be kept in sync:
+
+1. **Source of truth**: `src/deepwork/standard_jobs/deepwork_jobs/`
+   - This is where changes should be made first
+   - Tracked in version control
+
+2. **Working copy**: `.deepwork/jobs/deepwork_jobs/`
+   - Must be updated after changes to source
+   - Used by `deepwork sync` to generate commands
+
+After making changes to the source, copy files to the working copy:
+```bash
+cp src/deepwork/standard_jobs/deepwork_jobs/job.yml .deepwork/jobs/deepwork_jobs/
+cp src/deepwork/standard_jobs/deepwork_jobs/steps/*.md .deepwork/jobs/deepwork_jobs/steps/
+cp -r src/deepwork/standard_jobs/deepwork_jobs/templates/* .deepwork/jobs/deepwork_jobs/templates/
+```
+
+## File Organization
+
+```
+deepwork_jobs/
+├── AGENTS.md              # This file
+├── job.yml                # Job definition
+├── make_new_job.sh        # Script to create new job structure
+├── steps/
+│   ├── define.md          # Define step instructions
+│   ├── implement.md       # Implement step instructions
+│   ├── learn.md           # Learn step instructions
+│   └── supplemental_file_references.md  # Reference documentation
+└── templates/
+    ├── job.yml.template              # Job spec structure
+    ├── step_instruction.md.template  # Step instruction structure
+    ├── agents.md.template            # AGENTS.md structure
+    ├── job.yml.example               # Complete job example
+    └── step_instruction.md.example   # Complete step example
+```
+
+## Version Management
+
+- Version is tracked in `job.yml`
+- Bump patch version (0.0.x) for instruction improvements
+- Bump minor version (0.x.0) for new features or structural changes
+- Always update changelog when bumping version
+
+## Last Updated
+
+- Date: 2026-01-15
+- From conversation about: Adding make_new_job.sh script and templates directory

deepwork/standard_jobs/deepwork_jobs/job.yml

@@ -1,5 +1,5 @@
 name: deepwork_jobs
-version: "0.2.0"
+version: "0.4.0"
 summary: "DeepWork job management commands"
 description: |
   Core commands for managing DeepWork jobs. These commands help you define new multi-step
@@ -18,6 +18,10 @@ changelog:
     changes: "Initial version"
   - version: "0.2.0"
     changes: "Replaced refine command with learn command for conversation-driven improvement"
+  - version: "0.3.0"
+    changes: "Added make_new_job.sh script and templates directory; updated instructions to reference templates instead of inline examples"
+  - version: "0.4.0"
+    changes: "Removed implementation_summary and learning_summary outputs; simplified step outputs"
 
 steps:
   - id: define
@@ -54,7 +58,7 @@ steps:
       - file: job.yml
         from_step: define
     outputs:
-      - implementation_summary.md
+      - steps/
     dependencies:
       - define
     hooks:
@@ -69,8 +73,7 @@ steps:
             5. **Quality Criteria**: Does each instruction file define quality criteria for its outputs?
             6. **Sync Complete**: Has `deepwork sync` been run successfully?
             7. **Commands Available**: Are the slash-commands generated in `.claude/commands/`?
-            8. **Summary Created**: Has `implementation_summary.md` been created?
-            9. **Policies Considered**: Have you thought about whether policies would benefit this job?
+            8. **Policies Considered**: Have you thought about whether policies would benefit this job?
                - If relevant policies were identified, did you explain them and offer to run `/deepwork_policy.define`?
                - Not every job needs policies - only suggest when genuinely helpful.
 
@@ -85,7 +88,7 @@ steps:
       - name: job_name
         description: "Name of the job that was run (optional - will auto-detect from conversation)"
     outputs:
-      - learning_summary.md
+      - AGENTS.md
     dependencies: []
     hooks:
       after_agent:

deepwork/standard_jobs/deepwork_jobs/make_new_job.sh

@@ -0,0 +1,134 @@
+#!/usr/bin/env bash
+#
+# make_new_job.sh - Create directory structure for a new DeepWork job
+#
+# Usage: ./make_new_job.sh <job_name>
+#
+
+set -euo pipefail
+
+# Color output helpers
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+NC='\033[0m' # No Color
+
+info() {
+    echo -e "${GREEN}[INFO]${NC} $1"
+}
+
+warn() {
+    echo -e "${YELLOW}[WARN]${NC} $1"
+}
+
+error() {
+    echo -e "${RED}[ERROR]${NC} $1"
+    exit 1
+}
+
+# Validate job name format
+validate_job_name() {
+    local name="$1"
+    if [[ ! "$name" =~ ^[a-z][a-z0-9_]*$ ]]; then
+        error "Invalid job name '$name'. Must be lowercase, start with a letter, and contain only letters, numbers, and underscores."
+    fi
+}
+
+# Main script
+main() {
+    if [[ $# -lt 1 ]]; then
+        echo "Usage: $0 <job_name>"
+        echo ""
+        echo "Creates the directory structure for a new DeepWork job."
+        echo ""
+        echo "Arguments:"
+        echo "  job_name    Name of the job (lowercase, underscores allowed)"
+        echo ""
+        echo "Example:"
+        echo "  $0 competitive_research"
+        exit 1
+    fi
+
+    local job_name="$1"
+    validate_job_name "$job_name"
+
+    # Determine the base path - look for .deepwork directory
+    local base_path
+    if [[ -d ".deepwork/jobs" ]]; then
+        base_path=".deepwork/jobs"
+    elif [[ -d "../.deepwork/jobs" ]]; then
+        base_path="../.deepwork/jobs"
+    else
+        # Create from current directory
+        base_path=".deepwork/jobs"
+        mkdir -p "$base_path"
+    fi
+
+    local job_path="${base_path}/${job_name}"
+
+    # Check if job already exists
+    if [[ -d "$job_path" ]]; then
+        error "Job '$job_name' already exists at $job_path"
+    fi
+
+    info "Creating job directory structure for '$job_name'..."
+
+    # Create main job directory and subdirectories
+    mkdir -p "$job_path"
+    mkdir -p "$job_path/steps"
+    mkdir -p "$job_path/hooks"
+    mkdir -p "$job_path/templates"
+
+    # Add .gitkeep files to empty directories
+    touch "$job_path/hooks/.gitkeep"
+    touch "$job_path/templates/.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.
+
+## Recommended Commands
+
+- `/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
+
+## 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)
+│   └── *.md           # One file per step
+├── hooks/             # Custom validation scripts and prompts
+│   └── *.md|*.sh      # Hook files referenced in job.yml
+└── 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)
+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
+EOF
+
+    info "Created directory structure:"
+    echo "  $job_path/"
+    echo "  ├── AGENTS.md"
+    echo "  ├── steps/"
+    echo "  ├── hooks/.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

@@ -135,68 +135,31 @@ stop_hooks:
 
 **Encourage prompt-based hooks** - They leverage the AI's ability to understand context and make nuanced quality judgments. Script hooks are best for objective checks (syntax, format, tests).
 
-### Step 5: Create the job.yml Specification
+### Step 5: Create the Job Directory and Specification
 
-Only after you have complete understanding, create the `job.yml` file:
+Only after you have complete understanding, create the job directory and `job.yml` file:
 
-**File Location**: `.deepwork/jobs/[job_name]/job.yml`
+**First, create the directory structure** using the `make_new_job.sh` script:
 
-(Where `[job_name]` is the name of the NEW job you're creating, e.g., `.deepwork/jobs/competitive_research/job.yml`)
-
-**Format**:
-```yaml
-name: [job_name]
-version: "1.0.0"
-summary: "[Brief one-line summary of what this job accomplishes]"
-description: |
-  [Detailed multi-line description of the job's purpose, process, and goals.
-
-  This should explain:
-  - What problem this workflow solves
-  - What the overall process looks like
-  - What the end result will be
-  - Who the intended users are
-  - Any important context about the workflow]
-
-changelog:
-  - version: "1.0.0"
-    changes: "Initial job creation"
-
-steps:
-  - id: [step_id]
-    name: "[Step Name]"
-    description: "[What this step does]"
-    instructions_file: steps/[step_id].md
-    inputs:
-      - name: [param_name]
-        description: "[What user needs to provide]"
-      # OR for file inputs from previous steps:
-      # - file: [filename_or_path]
-      #   from_step: [previous_step_id]
-    outputs:
-      - [output_filename_or_path]  # e.g., "report.md" or "reports/analysis.md"
-    dependencies: []  # List of step IDs that must complete first
-    # Optional: Quality validation hooks
-    stop_hooks:
-      - prompt: |
-          Verify this step's output meets quality criteria:
-          1. [Criterion 1]
-          2. [Criterion 2]
-          If ALL criteria are met, include `<promise>✓ Quality Criteria Met</promise>`.
-
-  - id: [another_step]
-    name: "[Another Step]"
-    description: "[What this step does]"
-    instructions_file: steps/[another_step].md
-    inputs:
-      - file: [output_filename_or_path]
-        from_step: [step_id]
-    outputs:
-      - [another_output_path]
-    dependencies:
-      - [step_id]  # This step requires the previous step
+```bash
+.deepwork/jobs/deepwork_jobs/make_new_job.sh [job_name]
 ```
 
+This creates:
+- `.deepwork/jobs/[job_name]/` - Main job directory
+- `.deepwork/jobs/[job_name]/steps/` - For step instruction files
+- `.deepwork/jobs/[job_name]/hooks/` - For custom validation scripts
+- `.deepwork/jobs/[job_name]/templates/` - For example file formats
+- `.deepwork/jobs/[job_name]/AGENTS.md` - Job management guidance
+
+**Then create the job.yml file** at `.deepwork/jobs/[job_name]/job.yml`
+
+(Where `[job_name]` is the name of the NEW job you're creating, e.g., `competitive_research`)
+
+**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.
+
 **Important**:
 - Use lowercase with underscores for job name and step IDs
 - Ensure file inputs reference steps in dependencies

deepwork/standard_jobs/deepwork_jobs/steps/implement.md

@@ -8,10 +8,31 @@ Generate the DeepWork job directory structure and instruction files for each ste
 
 Read the `job.yml` specification file and create all the necessary files to make the job functional, including directory structure and step instruction files. Then sync the commands to make them available.
 
-### Step 1: Read and Validate the Specification
+### Step 1: Create Directory Structure Using Script
+
+Run the `make_new_job.sh` script to create the standard directory structure:
+
+```bash
+.deepwork/jobs/deepwork_jobs/make_new_job.sh [job_name]
+```
+
+This creates:
+- `.deepwork/jobs/[job_name]/` - Main job directory
+- `.deepwork/jobs/[job_name]/steps/` - Step instruction files
+- `.deepwork/jobs/[job_name]/hooks/` - Custom validation scripts (with .gitkeep)
+- `.deepwork/jobs/[job_name]/templates/` - Example file formats (with .gitkeep)
+- `.deepwork/jobs/[job_name]/AGENTS.md` - Job management guidance
+
+**Note**: If the directory already exists (e.g., job.yml was created by define step), you can skip this step or manually create the additional directories:
+```bash
+mkdir -p .deepwork/jobs/[job_name]/hooks .deepwork/jobs/[job_name]/templates
+touch .deepwork/jobs/[job_name]/hooks/.gitkeep .deepwork/jobs/[job_name]/templates/.gitkeep
+```
+
+### Step 2: Read and Validate the Specification
 
 1. **Locate the job.yml file**
-   - Read `.deepwork/jobs/[job_name]/job.yml` from the define step (Where `[job_name]` is the name of the new job that was created in the define step)
+   - Read `.deepwork/jobs/[job_name]/job.yml` from the define step
    - Parse the YAML content
 
 2. **Validate the specification**
@@ -25,83 +46,20 @@ Read the `job.yml` specification file and create all the necessary files to make
    - List of all steps with their details
    - Understand the workflow structure
 
-### Step 2: Create Directory Structure
-
-Create the job directory in `.deepwork/jobs/[job_name]/`:
-
-```bash
-mkdir -p .deepwork/jobs/[job_name]/steps
-```
-
-Files to create:
-- `.deepwork/jobs/[job_name]/job.yml`
-- `.deepwork/jobs/[job_name]/steps/[step_id].md` - One for each step
-
 ### Step 3: Generate Step Instruction Files
 
 For each step in the job.yml, create a comprehensive instruction file at `.deepwork/jobs/[job_name]/steps/[step_id].md`.
 
-Each instruction file should follow this structure:
-
-```markdown
-# [Step Name]
-
-## Objective
-
-[Clear statement of what this step accomplishes, derived from the step's description]
-
-## Task
-
-[Detailed instructions for completing this step, based on:
-- The step's purpose
-- Expected inputs and outputs
-- The job's overall context
-]
-
-### Process
-
-[Break down the step into substeps. Use the information gathered during define about:
-- What needs to be done
-- What makes a good output
-- Any quality criteria
-]
+**Template reference**: See `.deepwork/jobs/deepwork_jobs/templates/step_instruction.md.template` for the standard structure.
 
-1. [Substep 1]
-2. [Substep 2]
-3. [Substep 3]
+**Complete example**: See `.deepwork/jobs/deepwork_jobs/templates/step_instruction.md.example` for a fully worked example.
 
-[If this step has user inputs, explain how to gather them]
-[If this step has file inputs, explain how to use them]
-
-## Output Format
-
-### [output_filename_1]
-
-[Description of what should be in this output file]
-
-**Structure**:
-```[file format]
-[Example or template of what the output should look like]
-```
-
-[Repeat for each output file]
-
-## Quality Criteria
-
-[List what makes this step's output high quality:
-- Completeness checks
-- Format requirements
-- Content requirements
-]
-
-- [Quality criterion 1]
-- [Quality criterion 2]
-- [Quality criterion 3]
-
-## Context
-
-[Provide context from the job's overall description to help understand why this step matters and how it fits into the bigger picture]
-```
+**Available templates in `.deepwork/jobs/deepwork_jobs/templates/`:**
+- `job.yml.template` - Job specification structure
+- `step_instruction.md.template` - Step instruction file structure
+- `agents.md.template` - AGENTS.md file structure
+- `job.yml.example` - Complete job specification example
+- `step_instruction.md.example` - Complete step instruction example
 
 **Guidelines for generating instructions:**
 
@@ -233,112 +191,9 @@ Would you like me to create this policy? I can run `/deepwork_policy.define` to
 
 ## Example Implementation
 
-**Given this job.yml:**
-```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.
-
-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:
-      - competitors_list.md
-    dependencies: []
-```
-
-**Generate this instruction file** (`.deepwork/jobs/competitive_research/steps/identify_competitors.md`):
-
-```markdown
-# Identify Competitors
-
-## Objective
-
-Identify 5-7 key competitors in the target market segment to analyze for competitive positioning.
-
-## Task
-
-Research and identify the most relevant competitors in the specified market segment and product category. Focus on companies that directly compete for the same customer base and solve similar problems.
-
-### Process
-
-1. **Understand the market context**
-   - Review the market segment provided by the user
-   - Understand the product category boundaries
-   - Consider direct and indirect competitors
-
-2. **Research competitors**
-   - Search for companies in this space
-   - Look for market leaders and emerging players
-   - Consider different competitive dimensions (features, price, target market)
-
-3. **Select 5-7 key competitors**
-   - Prioritize direct competitors
-   - Include at least one market leader
-   - Include 1-2 emerging/innovative players
-   - Ensure diversity in the competitive set
-
-4. **Document each competitor**
-   - Company name
-   - Brief description (2-3 sentences)
-   - Why they're a relevant competitor
-   - Primary competitive dimension
-
-## Output Format
-
-### competitors_list.md
-
-A markdown document listing each competitor with context.
-
-**Structure**:
-```markdown
-# Competitor Analysis: [Market Segment]
-
-## Market Context
-- **Segment**: [market segment]
-- **Category**: [product category]
-- **Analysis Date**: [current date]
-
-## Identified Competitors
-
-### 1. [Competitor Name]
-**Description**: [2-3 sentence description of what they do]
-
-**Why Relevant**: [Why they're a key competitor in this space]
-
-**Competitive Dimension**: [What they compete on - e.g., price, features, market segment]
-
-[Repeat for each competitor, 5-7 total]
-
-## Selection Rationale
-
-[Brief paragraph explaining why these specific competitors were chosen and what dimensions of competition they represent]
-```
-
-## Quality Criteria
-
-- 5-7 competitors identified (not too few, not too many)
-- Mix of established and emerging players
-- All competitors are genuinely relevant to the market segment
-- Each competitor has clear, specific description
-- Selection rationale explains the competitive landscape
-- Output is well-formatted and ready for use by next step
-
-## Context
-
-This is the foundation step for competitive analysis. The competitors identified here will be deeply researched in subsequent steps, so it's important to choose the right set. Focus on competitors that will provide strategic insights for positioning decisions.
-```
+For a complete worked example showing a job.yml and corresponding step instruction file, see:
+- **Job specification**: `.deepwork/jobs/deepwork_jobs/templates/job.yml.example`
+- **Step instruction**: `.deepwork/jobs/deepwork_jobs/templates/step_instruction.md.example`
 
 ## Important Guidelines
 
@@ -357,63 +212,6 @@ Before running `deepwork sync`, verify:
 - All step instruction files exist (one per step)
 - No file system errors
 
-## Output Format
-
-### implementation_summary.md
-
-After successful implementation, create a summary:
-
-```markdown
-# Job Implementation Complete: [job_name]
-
-## Overview
-
-Successfully implemented the **[job_name]** workflow with [N] steps.
-
-**Summary**: [job summary]
-
-**Version**: [version]
-
-## Files Created
-
-### Job Definition
-- `.deepwork/jobs/[job_name]/job.yml`
-
-### Step Instructions
-- `.deepwork/jobs/[job_name]/steps/[step1_id].md`
-- `.deepwork/jobs/[job_name]/steps/[step2_id].md`
-[... list all step files ...]
-
-
-## Generated Commands
-
-After running `deepwork sync`, the following slash-commands are now available:
-
-- `/[job_name].[step1_id]` - [step description]
-- `/[job_name].[step2_id]` - [step description]
-[... list all commands ...]
-
-## Next Steps
-
-1. **Reload commands**: [Include the specific reload instructions from the `deepwork sync` output here]
-2. **Start the workflow**: Run `/[job_name].[first_step_id]` to begin
-3. **Test the job**: Try executing the first step to ensure everything works
-
-## Job Structure
-
-[Show the workflow diagram with step names and dependencies]
-
-Step 1: [step_name]
-  ↓
-Step 2: [step_name]
-  ↓
-Step 3: [step_name]
-  ↓
-[Final output]
-
-The job is now ready for use!
-```
-
 ## Completion Checklist
 
 Before marking this step complete, ensure:
@@ -423,7 +221,6 @@ Before marking this step complete, ensure:
 - [ ] `deepwork sync` executed successfully
 - [ ] Commands generated in platform directory
 - [ ] User informed to follow reload instructions from `deepwork sync`
-- [ ] implementation_summary.md created
 - [ ] Considered whether policies would benefit this job (Step 7)
 - [ ] If policies suggested, offered to run `/deepwork_policy.define`
 

deepwork/standard_jobs/deepwork_jobs/steps/learn.md

@@ -142,42 +142,7 @@ The AGENTS.md file captures project-specific knowledge that helps future agent r
    - This keeps AGENTS.md in sync as the codebase evolves
    - Pattern: "See `path/to/file.ext` for [description]"
 
-3. **AGENTS.md structure**:
-
-```markdown
-# Project Context for [Job Name]
-
-## Codebase Structure
-
-<!-- Reference files rather than duplicating content -->
-- Project structure: See `README.md` for overview
-- API documentation: See `docs/api.md`
-- Configuration: See `config/README.md`
-
-## Conventions
-
-### Naming Conventions
-- [Convention]: See example in `path/to/example.ext:LINE`
-
-### File Organization
-- [Pattern]: Reference `path/to/pattern/`
-
-## Job-Specific Context
-
-### [Job Name]
-
-#### [Step Name]
-- [Learning]: Reference `relevant/file.ext`
-- [Context]: [Brief explanation with file reference]
-
-## Known Issues and Workarounds
-
-- [Issue]: [Workaround with file reference if applicable]
-
-## Last Updated
-- Date: [YYYY-MM-DD]
-- From conversation about: [Brief description]
-```
+3. **AGENTS.md structure**: See `.deepwork/jobs/deepwork_jobs/templates/agents.md.template` for the standard format.
 
 4. **Writing entries**
    - Be concise but specific
@@ -199,36 +164,14 @@ If instruction files were modified:
      changes: "Improved [step] instructions based on execution learnings: [brief description]"
    ```
 
-### Step 7: Sync and Summarize
+### Step 7: Sync and Relay Instructions
 
 1. **Run deepwork sync** (if instructions were modified)
    ```bash
    deepwork sync
    ```
 
-2. **Create learning_summary.md** in the working folder:
-   ```markdown
-   # Learning Summary
-
-   ## Job Analyzed
-   - Job: [job_name]
-   - Steps executed: [list of steps]
-
-   ## Generalizable Improvements Made
-   - [Step]: [What was improved]
-
-   ## Bespoke Learnings Captured
-   - Location: [path to AGENTS.md]
-   - Entries added: [list of entries]
-
-   ## Files Modified
-   - [List of files changed]
-
-   ## Recommendations
-   - [Any additional suggestions]
-   ```
-
-3. **If commands were regenerated**, look at the "To use the new commands" section in the `deepwork sync` output and **relay these exact reload instructions to the user** (e.g., "Type 'exit' then run 'claude --resume'" for Claude Code)
+2. **If commands were regenerated**, look at the "To use the new commands" section in the `deepwork sync` output and **relay these exact reload instructions to the user** (e.g., "Type 'exit' then run 'claude --resume'" for Claude Code)
 
 ## File Reference Patterns
 
@@ -259,7 +202,6 @@ When adding entries to AGENTS.md, prefer these patterns:
 - AGENTS.md created/updated with bespoke learnings
 - File references used instead of duplicating content
 - AGENTS.md is in the correct working folder
-- learning_summary.md documents all changes
 - When all criteria are met, include `<promise>✓ Quality Criteria Met</promise>`
 
 ## Example Dialog
@@ -319,7 +261,7 @@ I found the following job executions:
 
 **Summary**
 
-Created `learning_summary.md` documenting all changes. To get the updated commands, type 'exit' then run 'claude --resume'.
+Updated job instructions and created AGENTS.md with bespoke learnings. To get the updated commands, type 'exit' then run 'claude --resume'.
 ```
 
 ## Handling Edge Cases

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

@@ -0,0 +1,32 @@
+# Project Context for [Job Name]
+
+## Codebase Structure
+
+<!-- Reference files rather than duplicating content -->
+- Project structure: See `README.md` for overview
+- API documentation: See `docs/api.md`
+- Configuration: See `config/README.md`
+
+## Conventions
+
+### Naming Conventions
+- [Convention]: See example in `path/to/example.ext:LINE`
+
+### File Organization
+- [Pattern]: Reference `path/to/pattern/`
+
+## Job-Specific Context
+
+### [Job Name]
+
+#### [Step Name]
+- [Learning]: Reference `relevant/file.ext`
+- [Context]: [Brief explanation with file reference]
+
+## Known Issues and Workarounds
+
+- [Issue]: [Workaround with file reference if applicable]
+
+## Last Updated
+- Date: [YYYY-MM-DD]
+- From conversation about: [Brief description]

deepwork/standard_jobs/deepwork_jobs/templates/job.yml.example

@@ -0,0 +1,73 @@
+# Example: Competitive Research Job
+#
+# This is a complete example of a job.yml file for reference.
+
+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.
+
+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:
+      - 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: competitors_list.md
+        from_step: identify_competitors
+    outputs:
+      - research_notes.md
+    dependencies:
+      - identify_competitors
+    hooks:
+      after_agent:
+        - prompt: |
+            Verify the research meets criteria:
+            1. Each competitor has at least 3 data points
+            2. Sources are cited
+            3. Information is current (within last year)
+            If ALL criteria are met, include `<promise>✓ Quality Criteria Met</promise>`.
+
+  - id: comparative_analysis
+    name: "Comparative Analysis"
+    description: "Create side-by-side comparison matrix"
+    instructions_file: steps/comparative_analysis.md
+    inputs:
+      - file: research_notes.md
+        from_step: research_competitors
+    outputs:
+      - comparison_matrix.md
+    dependencies:
+      - research_competitors
+
+  - id: positioning_recommendations
+    name: "Positioning Recommendations"
+    description: "Strategic positioning recommendations based on analysis"
+    instructions_file: steps/positioning_recommendations.md
+    inputs:
+      - file: comparison_matrix.md
+        from_step: comparative_analysis
+    outputs:
+      - positioning_report.md
+    dependencies:
+      - comparative_analysis

deepwork/standard_jobs/deepwork_jobs/templates/job.yml.template

@@ -0,0 +1,56 @@
+# DeepWork Job Specification Template
+#
+# This template shows the structure of a job.yml file.
+# Replace placeholders in [brackets] with actual values.
+
+name: [job_name]
+version: "1.0.0"
+summary: "[Brief one-line summary of what this job accomplishes - max 200 chars]"
+description: |
+  [Detailed multi-line description of the job's purpose, process, and goals.
+
+  This should explain:
+  - What problem this workflow solves
+  - What the overall process looks like
+  - What the end result will be
+  - Who the intended users are
+  - Any important context about the workflow]
+
+changelog:
+  - version: "1.0.0"
+    changes: "Initial job creation"
+
+steps:
+  - id: [step_id]
+    name: "[Step Name]"
+    description: "[What this step does]"
+    instructions_file: steps/[step_id].md
+    inputs:
+      - name: [param_name]
+        description: "[What user needs to provide]"
+      # OR for file inputs from previous steps:
+      # - file: [filename_or_path]
+      #   from_step: [previous_step_id]
+    outputs:
+      - [output_filename_or_path]  # e.g., "report.md" or "reports/analysis.md"
+    dependencies: []  # List of step IDs that must complete first
+    # Optional: Quality validation hooks
+    hooks:
+      after_agent:
+        - prompt: |
+            Verify this step's output meets quality criteria:
+            1. [Criterion 1]
+            2. [Criterion 2]
+            If ALL criteria are met, include `<promise>✓ Quality Criteria Met</promise>`.
+
+  - id: [another_step]
+    name: "[Another Step]"
+    description: "[What this step does]"
+    instructions_file: steps/[another_step].md
+    inputs:
+      - file: [output_filename_or_path]
+        from_step: [step_id]
+    outputs:
+      - [another_output_path]
+    dependencies:
+      - [step_id]  # This step requires the previous step

deepwork/standard_jobs/deepwork_jobs/templates/step_instruction.md.example

@@ -0,0 +1,82 @@
+# Example: Identify Competitors Step Instruction
+#
+# This is a complete example of a step instruction file for reference.
+
+# Identify Competitors
+
+## Objective
+
+Identify 5-7 key competitors in the target market segment to analyze for competitive positioning.
+
+## Task
+
+Research and identify the most relevant competitors in the specified market segment and product category. Focus on companies that directly compete for the same customer base and solve similar problems.
+
+### Process
+
+1. **Understand the market context**
+   - Review the market segment provided by the user
+   - Understand the product category boundaries
+   - Consider direct and indirect competitors
+
+2. **Research competitors**
+   - Search for companies in this space
+   - Look for market leaders and emerging players
+   - Consider different competitive dimensions (features, price, target market)
+
+3. **Select 5-7 key competitors**
+   - Prioritize direct competitors
+   - Include at least one market leader
+   - Include 1-2 emerging/innovative players
+   - Ensure diversity in the competitive set
+
+4. **Document each competitor**
+   - Company name
+   - Brief description (2-3 sentences)
+   - Why they're a relevant competitor
+   - Primary competitive dimension
+
+## Output Format
+
+### competitors_list.md
+
+A markdown document listing each competitor with context.
+
+**Structure**:
+```markdown
+# Competitor Analysis: [Market Segment]
+
+## Market Context
+- **Segment**: [market segment]
+- **Category**: [product category]
+- **Analysis Date**: [current date]
+
+## Identified Competitors
+
+### 1. [Competitor Name]
+**Description**: [2-3 sentence description of what they do]
+
+**Why Relevant**: [Why they're a key competitor in this space]
+
+**Competitive Dimension**: [What they compete on - e.g., price, features, market segment]
+
+[Repeat for each competitor, 5-7 total]
+
+## Selection Rationale
+
+[Brief paragraph explaining why these specific competitors were chosen and what dimensions of competition they represent]
+```
+
+## Quality Criteria
+
+- 5-7 competitors identified (not too few, not too many)
+- Mix of established and emerging players
+- All competitors are genuinely relevant to the market segment
+- Each competitor has clear, specific description
+- Selection rationale explains the competitive landscape
+- Output is well-formatted and ready for use by next step
+- When all criteria are met, include `<promise>✓ Quality Criteria Met</promise>` in your response
+
+## Context
+
+This is the foundation step for competitive analysis. The competitors identified here will be deeply researched in subsequent steps, so it's important to choose the right set. Focus on competitors that will provide strategic insights for positioning decisions.

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

@@ -0,0 +1,58 @@
+# [Step Name]
+
+## Objective
+
+[Clear statement of what this step accomplishes, derived from the step's description]
+
+## Task
+
+[Detailed instructions for completing this step, based on:
+- The step's purpose
+- Expected inputs and outputs
+- The job's overall context
+]
+
+### Process
+
+[Break down the step into substeps. Use the information gathered during define about:
+- What needs to be done
+- What makes a good output
+- Any quality criteria
+]
+
+1. [Substep 1]
+2. [Substep 2]
+3. [Substep 3]
+
+[If this step has user inputs, explain how to gather them]
+[If this step has file inputs, explain how to use them]
+
+## Output Format
+
+### [output_filename_1]
+
+[Description of what should be in this output file]
+
+**Structure**:
+```[file format]
+[Example or template of what the output should look like]
+```
+
+[Repeat for each output file]
+
+## Quality Criteria
+
+[List what makes this step's output high quality:
+- Completeness checks
+- Format requirements
+- Content requirements
+]
+
+- [Quality criterion 1]
+- [Quality criterion 2]
+- [Quality criterion 3]
+- When all criteria are met, include `<promise>✓ Quality Criteria Met</promise>` in your response
+
+## Context
+
+[Provide context from the job's overall description to help understand why this step matters and how it fits into the bigger picture]

deepwork/templates/default_policy.yml

@@ -0,0 +1,53 @@
+# DeepWork Policy Configuration
+#
+# Policies are automated guardrails that trigger when specific files change.
+# They help ensure documentation stays current, security reviews happen, etc.
+#
+# Use /deepwork_policy.define to create new policies interactively.
+#
+# Format:
+#   - name: "Friendly name for the policy"
+#     trigger: "glob/pattern/**/*"  # or array: ["pattern1", "pattern2"]
+#     safety: "pattern/**/*"        # optional - if these also changed, skip the policy
+#     compare_to: "base"            # optional: "base" (default), "default_tip", or "prompt"
+#     instructions: |
+#       Multi-line instructions for the AI agent...
+#
+# Example policies (uncomment and customize):
+#
+# - name: "README Documentation"
+#   trigger: "src/**/*"
+#   safety: "README.md"
+#   instructions: |
+#     Source code has been modified. Please review README.md for accuracy:
+#     1. Verify the project overview reflects current functionality
+#     2. Check that usage examples are still correct
+#     3. Ensure installation/setup instructions remain valid
+#
+# - name: "API Documentation Sync"
+#   trigger: "src/api/**/*"
+#   safety: "docs/api/**/*.md"
+#   instructions: |
+#     API code has changed. Please verify that API documentation is up to date:
+#     - New or changed endpoints
+#     - Modified request/response schemas
+#     - Updated authentication requirements
+#
+# - name: "Security Review for Auth Changes"
+#   trigger:
+#     - "src/auth/**/*"
+#     - "src/security/**/*"
+#   instructions: |
+#     Authentication or security code has been changed. Please:
+#     1. Review for hardcoded credentials or secrets
+#     2. Check input validation on user inputs
+#     3. Verify access control logic is correct
+#
+# - name: "Test Coverage for New Code"
+#   trigger: "src/**/*.py"
+#   safety: "tests/**/*.py"
+#   instructions: |
+#     New source code was added. Please ensure appropriate test coverage:
+#     1. Add unit tests for new functions/methods
+#     2. Update integration tests if behavior changed
+#     3. Verify all new code paths are tested

{deepwork-0.1.1.dist-info → deepwork-0.2.0.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: deepwork
-Version: 0.1.1
+Version: 0.2.0
 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
@@ -97,6 +97,7 @@ This will:
 - Generate core DeepWork jobs
 - Install DeepWork jobs for your AI assistant
 - Configure hooks for your AI assistant to enable policies
+- Create a `.deepwork.policy.yml` template file with example policies
 
 ## Quick Start
 

{deepwork-0.1.1.dist-info → deepwork-0.2.0.dist-info}/RECORD

@@ -1,6 +1,6 @@
 deepwork/__init__.py,sha256=vcMnJioxhfoL6kGh4FM51Vk9UoLnQ76g6Ms7XDUItYA,748
 deepwork/cli/__init__.py,sha256=3SqmfcP2xqutiCYAbajFDJTjr2pOLydqTN0NN-FTsIE,33
-deepwork/cli/install.py,sha256=hT7J-bxT6fEVIJb6fkMRTNvb76ycrZpovhdDItHWpTs,9935
+deepwork/cli/install.py,sha256=EnsegIjj-ZYkXMGER0iJXHuN2vVzFhzDUbNLL0ZU5bk,11366
 deepwork/cli/main.py,sha256=m6tVnfSy03azI9Ky6ySEMat_UdLEMzVT3SsRKQWigvA,471
 deepwork/cli/sync.py,sha256=lGgT9Tz_vPQx4z4Bkqk5LfkcT2hTn9nPvdWJVSeKhmM,6303
 deepwork/core/__init__.py,sha256=1g869QuwsYzNjQONneng2OMc6HKt-tlBCaxJbMMfoho,36
@@ -15,11 +15,18 @@ deepwork/hooks/evaluate_policies.py,sha256=hGi6lDcldGj7MYoUqViB9ObtTRrUHJvkjJeNJ
 deepwork/schemas/__init__.py,sha256=PpydKb_oaTv8lYapN_nV-Tl_OUCoSM_okvsEJ8gNTpI,41
 deepwork/schemas/job_schema.py,sha256=MpcUsk2pH7y-uNANFTeNlTDwyKwALAAf57VmJeK-JwE,8755
 deepwork/schemas/policy_schema.py,sha256=Y6P3YkiEza-W8WwqjTBinNCPreCgMz2OUShmVGx4OBo,3099
-deepwork/standard_jobs/deepwork_jobs/job.yml,sha256=ICxPlhK6wK4yZTmGazaOTRYLGrtPpZu1f-L8SzZj9bk,5753
-deepwork/standard_jobs/deepwork_jobs/steps/define.md,sha256=X1-ckzLk3FUUfuEFfH-W3eemTgfqvCp0NQNNve8LXlM,13707
-deepwork/standard_jobs/deepwork_jobs/steps/implement.md,sha256=79cXdxmGrdrgvx-NIcgW4nB7wbPjEdw4BpgWAtOhLOc,14823
-deepwork/standard_jobs/deepwork_jobs/steps/learn.md,sha256=_PnqSgi-zqHma6GzQkADig4Y5BpWFDFQMIVQuWGmYRs,11338
+deepwork/standard_jobs/deepwork_jobs/AGENTS.md,sha256=Y6I4jZ8DfN0RFY3UF5bgQRZvL7wQD9P0lgE7EZM6CGI,2252
+deepwork/standard_jobs/deepwork_jobs/job.yml,sha256=aY2V-ReMuZ2VxqVT14H1euX_cB9ZvWibAzO81oXI-o8,5924
+deepwork/standard_jobs/deepwork_jobs/make_new_job.sh,sha256=JArfFU9lEaJPRsXRL3rU1IMt2p6Bq0s2C9f98aJ7Mxg,3878
+deepwork/standard_jobs/deepwork_jobs/steps/define.md,sha256=6CYM7LB1Vx7tD76QP65s2wdTCcPk15ZVFLx6TZndbyg,12819
+deepwork/standard_jobs/deepwork_jobs/steps/implement.md,sha256=Wh7ZJGNSyejSgICPFzhbTBaH2bF288YGWqkhKQEmyH4,10313
+deepwork/standard_jobs/deepwork_jobs/steps/learn.md,sha256=yyB6ManHblOOxEM_Odbx0tvPVFVwqlmnwxiC7lZ7txU,10185
 deepwork/standard_jobs/deepwork_jobs/steps/supplemental_file_references.md,sha256=uKDEwB3TxMLK-Zim3QQfkvaW5W6AVWHjWnH25aY6wCw,1478
+deepwork/standard_jobs/deepwork_jobs/templates/agents.md.template,sha256=SUJL862C6-DnT9lK3sNIZ5T2wVgXN4YRph4FrKtFnLo,739
+deepwork/standard_jobs/deepwork_jobs/templates/job.yml.example,sha256=roRi6sIGFGmPCkoVW26HfuTBjAO8-pPsxI5-Gfg3rc0,2361
+deepwork/standard_jobs/deepwork_jobs/templates/job.yml.template,sha256=3I-VQvqXVJNZ_Vb5Ik28JsrEbGKbyLTZcuKxdEmV5s0,1789
+deepwork/standard_jobs/deepwork_jobs/templates/step_instruction.md.example,sha256=HXcjVaQz2HsDiA4ClnIeLvysVOGrFJ_5Tr-pm6dhdwc,2706
+deepwork/standard_jobs/deepwork_jobs/templates/step_instruction.md.template,sha256=6n9jFFuda4r549Oo-LBPKixFD3NvDl5MwEg5V7ItQBg,1286
 deepwork/standard_jobs/deepwork_policy/job.yml,sha256=6pxyEiHZ7fThd4CjpkkROKXGlRqaH4odinLc-ttfork,1377
 deepwork/standard_jobs/deepwork_policy/hooks/capture_prompt_work_tree.sh,sha256=D6Ozo9oDqsL7YBh-ebQK1S8ED9hfIi_0Z8khFjC6wZY,973
 deepwork/standard_jobs/deepwork_policy/hooks/global_hooks.yml,sha256=AS8wzWz7Q4s7iUdhjUwjm9t91Z7QZZw3JCBH81IqKRg,166
@@ -27,6 +34,7 @@ deepwork/standard_jobs/deepwork_policy/hooks/policy_stop_hook.sh,sha256=HFLTheh3
 deepwork/standard_jobs/deepwork_policy/hooks/user_prompt_submit.sh,sha256=TxwYb7kBW-cfHmcQoruJBjCTWvdWbQVQIMplNgzMuOs,498
 deepwork/standard_jobs/deepwork_policy/steps/define.md,sha256=p16fcPSc_6g4WvBzCBJ5l32Uaasp8lew5e6LaDPjpNI,7430
 deepwork/templates/__init__.py,sha256=APvjx_u7eRUerw9yA_fJ1ZqCzYA-FWUCV9HCz0RgjOc,50
+deepwork/templates/default_policy.yml,sha256=nOJtFzV6SPDwNvzNcDKL-679CTXq6hgIBTaxnUKSdVs,2049
 deepwork/templates/claude/command-job-step.md.jinja,sha256=hrOR6WqUVJ8aX_qIptVUuGd4BAe439Dx6gMv-MeCk40,5795
 deepwork/templates/gemini/command-job-step.toml.jinja,sha256=UlhljjJlwNO9D_NrG6MNZ7IKozrdjy2DkPkj9E7hKxU,4196
 deepwork/utils/__init__.py,sha256=AtvE49IFI8Rg36O4cNIlzB-oxvkW3apFgXExn8GSk6s,38
@@ -34,8 +42,8 @@ deepwork/utils/fs.py,sha256=94OUvUrqGebjHVtnjd5vXL6DalKNdpRu-iAPsHvAPjI,3499
 deepwork/utils/git.py,sha256=J4tAB1zE6-WMAEHbarevhmSvvPLkeKBpiRv1UxUVwYk,3748
 deepwork/utils/validation.py,sha256=SyFg9fIu1JCDMbssQgJRCTUNToDNcINccn8lje-tjts,851
 deepwork/utils/yaml_utils.py,sha256=X8c9yEqxEgw5CdPQ23f1Wz8SSP783MMGKyGV_2SKaNU,2454
-deepwork-0.1.1.dist-info/METADATA,sha256=SFGiVAzLj3ZVcGNDTHD0g2Xsv5_QUl5gaBQ6SAJhXS0,11146
-deepwork-0.1.1.dist-info/WHEEL,sha256=WLgqFyCfm_KASv4WHyYy0P3pM_m7J5L9k2skdKLirC8,87
-deepwork-0.1.1.dist-info/entry_points.txt,sha256=RhJBySzm619kh-yIdsAyfFXInAlY8Jm-39FLIBcOj2s,51
-deepwork-0.1.1.dist-info/licenses/LICENSE.md,sha256=W0EtJVYf0cQ_awukOCW1ETwNSpV2RKqnAGfoOjyz_K8,4126
-deepwork-0.1.1.dist-info/RECORD,,
+deepwork-0.2.0.dist-info/METADATA,sha256=z00l55xdxJKzjQxc0d7m293oGNaEAnfa0gzkPOi1UGk,11216
+deepwork-0.2.0.dist-info/WHEEL,sha256=WLgqFyCfm_KASv4WHyYy0P3pM_m7J5L9k2skdKLirC8,87
+deepwork-0.2.0.dist-info/entry_points.txt,sha256=RhJBySzm619kh-yIdsAyfFXInAlY8Jm-39FLIBcOj2s,51
+deepwork-0.2.0.dist-info/licenses/LICENSE.md,sha256=W0EtJVYf0cQ_awukOCW1ETwNSpV2RKqnAGfoOjyz_K8,4126
+deepwork-0.2.0.dist-info/RECORD,,