Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions .claude/skills/deepwork/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,24 @@ Execute multi-step workflows with quality gate checkpoints.
4. Call `finished_step` with your outputs when done
5. Handle the response: `needs_work`, `next_step`, or `workflow_complete`

## Creating New Jobs

<important>
You MUST create new DeepWork jobs by starting the `new_job` workflow via the DeepWork
MCP tools. Follow the guidance from the DeepWork MCP server as you go through the
workflow — it will walk you through each step.
</important>

To create a new job, use the MCP tools:

1. Call `get_workflows` to confirm the `deepwork_jobs` job is available
2. Call `start_workflow` with:
- `job_name`: `"deepwork_jobs"`
- `workflow_name`: `"new_job"`
- `goal`: a description of what the new job should accomplish
- `instance_id`: a short name for the new job (e.g., `"code_review"`)
3. Follow the instructions returned by the MCP tools as you progress through the workflow

## Intent Parsing

When the user invokes `/deepwork`, parse their intent:
Expand Down
18 changes: 18 additions & 0 deletions src/deepwork/templates/claude/skill-deepwork.md.jinja
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,24 @@ Execute multi-step workflows with quality gate checkpoints.
4. Call `finished_step` with your outputs when done
5. Handle the response: `needs_work`, `next_step`, or `workflow_complete`

## Creating New Jobs

<important>
You MUST create new DeepWork jobs by starting the `new_job` workflow via the DeepWork
MCP tools. Follow the guidance from the DeepWork MCP server as you go through the
workflow — it will walk you through each step.
</important>

To create a new job, use the MCP tools:

1. Call `get_workflows` to confirm the `deepwork_jobs` job is available
2. Call `start_workflow` with:
- `job_name`: `"deepwork_jobs"`
- `workflow_name`: `"new_job"`
- `goal`: a description of what the new job should accomplish
- `instance_id`: a short name for the new job (e.g., `"code_review"`)
3. Follow the instructions returned by the MCP tools as you progress through the workflow

## Intent Parsing

When the user invokes `/deepwork`, parse their intent:
Expand Down