deepwork_jobs.implement

To generate step instruction files from a job.yml specification, run the deepwork_jobs.implement skill. It parses your validated job.yml, creates the required .deepwork/jobs/[job_name]/ directory structure, and outputs ready-to-run step instruction files using reference templates.

Syncing slash commands from a validated job.yml involves parsing the specification and making the corresponding commands available in Claude or DeepWork. This skill automates that synchronization immediately after generating the step instruction files.

Yes, you need a validated .deepwork/jobs/[job_name]/job.yml file present in your environment. The generation process requires this reviewed specification to ensure schema compliance and dependencies before creating the functional directory structure.

Stop_hook quality criteria apply during job.yml workflow generation by providing guidance and hooks that enforce quality checks. This ensures the generated step instructions and synced commands meet defined standards before the process completes.

Yes, you can use this workflow automation skill to validate a job.yml schema and dependencies. It parses and validates the job.yml to ensure full schema compliance before proceeding with the generation of step instruction files.

Step instruction files may not generate from the job.yml specification if the file is not present in the .deepwork/jobs/[job_name]/ directory, fails schema validation, or if required templates and stop_hook support are not accessible during the generation process.