Add export-job command for sharing jobs across Claude projects

[Copilot]

Jobs are currently project-scoped in .deepwork/jobs/, requiring installation in each project. Users need a way to make jobs available globally across all Claude projects.

Changes

New CLI Command

• deepwork export-job <job_name> copies job from project to global Claude settings
• Locations: .deepwork/jobs/ → ~/.deepwork/jobs/, .claude/skills/ → ~/.claude/skills/
• Automatically handles: job definition, step instructions, doc specs, hooks, permissions
• Safety: prompts for confirmation on overwrite (skip with --force)

Implementation (src/deepwork/cli/export_job.py)

• Validates job exists in project before export
• Recursively copies job directory and referenced doc specs
• Generates skills using existing SkillGenerator and ClaudeAdapter
• Syncs hooks via sync_hooks_to_platform to global settings.json
• Updates global permissions for DeepWork operations and skill invocations

Tests (tests/integration/test_export_job.py)

• 6 integration tests covering export flow, overwrites, doc specs, error handling

Usage

# Export a job to global settings
deepwork export-job my_workflow

# Force overwrite without confirmation
deepwork export-job my_workflow --force

Once exported, /my_workflow is available in any Claude project without per-project installation.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Allow job to be transferred to global clause</issue_title>
<issue_description>Users may want to share jobs to the global Claude settings</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Allow job to be transferred to global claude #148

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.