deepwork_jobs.define

Generate DeepWork job.yml specifications from structured workflow questions.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/ncrmro/deepwork-permanent-portfolio --skill deepwork-jobs-define-ncrmro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deepwork_jobs.define
Source: https://github.com/ncrmro/deepwork-permanent-portfolio/tree/main/.claude/skills/deepwork_jobs.define
Command: npx skills add https://github.com/ncrmro/deepwork-permanent-portfolio --skill deepwork-jobs-define-ncrmro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the creation of DeepWork job.yml specifications by guiding users through a structured questioning process to capture workflow requirements and convert them into a complete, implementable plan.

Core Features & Use Cases

  • Interactive, question-driven intake to capture goals, constraints, and success criteria for a new multi-step workflow.
  • Automatic generation of a full job.yml skeleton including steps, inputs, outputs, dependencies, and changelog.
  • Validation-ready output with optional doc spec references and clear field definitions to ensure consistency across teams.
  • Suitable for teams designing new workflows in product, data, research, or automation contexts.

Quick Start

Describe your multi-step workflow and I will generate a complete DeepWork job.yml.

Frequently Asked Questions about deepwork_jobs.define

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

FAQPage Schema
How do I create a structured multi-step workflow specification?

To create a structured multi-step workflow specification, you describe your process goals and constraints, and the system interactively generates an implementation-ready job.yml skeleton with defined inputs, outputs, dependencies, and validation rules.

What is a job.yml file used for in workflow automation?

A job.yml file in workflow automation defines a complete, structured multi-step workflow, capturing goals, inputs, outputs, dependencies, and changelog to ensure consistent execution and validation across product, research, and automation domains.

How do I define inputs, outputs, and dependencies for a new workflow?

You define inputs, outputs, and dependencies for a new workflow by answering structured intake questions about your process goals, which automatically translates your requirements into a validation-ready job.yml skeleton.

Can I use automated questioning to generate a validation-ready job skeleton?

Yes, you can use automated questioning to generate a validation-ready job skeleton by providing your workflow requirements through an interactive intake process that ensures the output adheres to the required schema.

Does the generated job.yml include documentation references and a changelog?

Yes, the generated job.yml includes a changelog and optional doc spec references to ensure clear field definitions and consistency across teams during future workflow refinements.

What is the best way to document multi-step workflows for automation teams?

The best way to document multi-step workflows for automation teams is using an interactive intake process that captures success criteria and constraints, outputting a complete job.yml with rich descriptions and validation-ready field definitions.