deepwork_jobs.implement

Generate step instruction files and sync slash commands from job.yml.

1|Updated Jun 30, 2025
One-click install
npx skills add https://github.com/EONMUN/EONMUN --skill deepwork-jobs-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deepwork_jobs.implement
Source: https://github.com/EONMUN/EONMUN/tree/main/.claude/skills/deepwork_jobs.implement
Command: npx skills add https://github.com/EONMUN/EONMUN --skill deepwork-jobs-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of step instruction files and the synchronization of slash commands from a job.yml specification, enabling consistent DeepWork job implementation.

Core Features & Use Cases

  • Generate comprehensive step instruction files for each defined job step.
  • Sync slash commands based on the validated job.yml to keep tooling up to date.
  • Validate prerequisites (job.yml location and schema) before proceeding to implementation.

Quick Start

Use this skill after a job.yml has been reviewed to generate the step docs and register the associated commands.

Frequently Asked Questions about deepwork_jobs.implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate step instruction files from a job.yml specification?

You can automate step instruction file generation and slash command synchronization from a validated job.yml specification. This process automatically creates a structured .deepwork/jobs/[job_name]/ directory hierarchy and updates corresponding CLI commands.

What is the process to sync slash commands for DeepWork workflow implementations?

Syncing slash commands for DeepWork workflows involves executing a deepwork sync operation after generating step docs from a validated job.yml. This updates the CLI and skill commands to match the newly defined multi-step job specifications.

Do I need a pre-reviewed job.yml before automating DeepWork job implementation?

Yes, a pre-reviewed job.yml specification is required before automating DeepWork job implementation. The automation skill validates the job.yml location and schema as prerequisites before proceeding to generate step docs and sync commands.

How does validating a job.yml schema help automate multi-step AI jobs?

Validating a job.yml schema enforces a structured workflow by ensuring the job specification meets required formats before generation. It guarantees that step docs and slash commands are accurately synchronized without structural errors.

What are the limitations of using slash command automation for workflow step instructions?

The automation requires a pre-reviewed job.yml file and applies specifically to DeepWork workflow implementations defining multi-step AI jobs. It cannot generate instructions or sync commands without passing the initial job.yml location and schema validation checks.