Skip to content

Conversation

@nhorton
Copy link
Contributor

@nhorton nhorton commented Jan 30, 2026

Summary

Enhanced the deepwork_jobs.define job creation process to support and guide users through defining multiple workflows within a single job. This allows jobs to expose different execution paths through the same set of steps, enabling use cases like quick summaries, full analyses, and refresh-only workflows.

Key Changes

  • New Step 2.5 in define.md: Added structured workflow organization guidance that asks users about different ways to use their steps and when to create multiple workflows

    • Includes decision criteria for when multiple workflows are beneficial
    • Provides clear examples of workflow definition format
    • Explains the difference between explicit and implicit workflows
    • Documents the exposed: true flag for standalone skills
  • Updated job specification documentation (job_spec.md):

    • Added "Valid Workflows" quality criteria to validate workflow definitions
    • Included comprehensive workflows section with examples showing how multiple workflows can share steps
    • Added validation rule Cleanup #6 for workflow step ID references
    • Updated complete job example to demonstrate multi-workflow usage
  • Enhanced example and template files:

    • Updated job.yml.example to demonstrate a competitive research job with three workflows (full_analysis, quick_summary, refresh_research)
    • Updated job.yml.template with optional workflows section and inline documentation
    • Added comment noting the example demonstrates multiple workflows
  • Updated CHANGELOG.md: Documented the new guidance and examples for multi-workflow job creation

Implementation Details

  • Workflows are optional; jobs without a workflows section use all steps as an implicit single workflow
  • Multiple workflows can share steps and define different execution paths
  • All step IDs referenced in workflows must exist in the steps section
  • The guidance maintains backward compatibility with existing single-workflow jobs

https://claude.ai/code/session_01Mr1h2fVSKeVP84FDWXx4UM

claude and others added 6 commits January 30, 2026 19:20
Update the define step and templates to support jobs with multiple
workflows. This allows a single job to define different execution
paths through the same set of steps (e.g., full_analysis vs.
quick_summary).

Changes:
- Add Step 2.5 in define.md to ask about workflow organization
- Update job.yml.template with workflows section
- Add multi-workflow example to job.yml.example
- Add Valid Workflows quality criterion to job_spec.md
- Update example dialog to show workflow discovery

https://claude.ai/code/session_01Mr1h2fVSKeVP84FDWXx4UM
Focus on the key use case: workflows are for when different parts
need to happen at different points in time (human review gates,
setup/teardown patterns, phased execution).

Remove verbose questions about workflow organization and simplify
the example dialog to show a single-workflow job (the common case).

https://claude.ai/code/session_01Mr1h2fVSKeVP84FDWXx4UM
Demote from separate "Step 2.5" to a brief note alongside Browser
Automation in the existing Capability Considerations section.

https://claude.ai/code/session_01Mr1h2fVSKeVP84FDWXx4UM
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants