deepwork_jobs.implement

You can auto-generate step instruction files by running a deepwork implementation that parses and validates your job.yml, converting each defined step into a detailed markdown instruction file under the .deepwork/jobs directory.

The best way to scaffold a DeepWork job directory and sync slash commands is to use an automated workflow that creates the standard folder structure under .deepwork/jobs and triggers a deepwork sync to publish per-step skills under .claude/skills.

Command synchronization works by parsing the validated job.yml specification and triggering a deepwork sync that updates Claude slash commands, ensuring new steps are immediately available to run as registered skills under .claude/skills.

No, you do not need to manually create directories or step files. The implementation automatically handles directory scaffolding, generates per-step documentation, and publishes the per-step skills after you confirm the job.yml is ready.

You should use an automated workflow to generate job steps when finalizing a new DeepWork job after the define and review phases, ensuring consistency across artifacts and reducing manual setup errors during skill publishing.