Skip to content

Add terminology section to DeepWork skill documentation #216

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nhorton merged 2 commits into from
Feb 17, 2026
Merged

Add terminology section to DeepWork skill documentation #216

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f007fb6
Add terminology section clarifying job/workflow relationship
claude Feb 16, 2026
2713aa6
Remove remaining quality criteria reference
nhorton Feb 17, 2026
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
7 changes: 7 additions & 0 deletions .claude/skills/deepwork/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,13 @@ description: "Start or continue DeepWork workflows using MCP tools"

Execute multi-step workflows with quality gate checkpoints.

## Terminology

A **job** is a collection of related **workflows**. For example, a "code_review" job
might contain workflows like "review_pr" and "review_diff". Users may use the terms
"job" and "workflow" somewhat interchangeably when describing the work they want done —
use context and the available workflows from `get_workflows` to determine the best match.

> **IMPORTANT**: Use the DeepWork MCP server tools. All workflow operations
> are performed through MCP tool calls and following the instructions they return,
> not by reading instructions from files.
Expand Down
5 changes: 0 additions & 5 deletions .deepwork/jobs/update_job_schema/job.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,11 +29,6 @@ common_job_info_provided_to_all_steps_at_runtime: |
- **MCP schemas**: `src/deepwork/mcp/schemas.py`
- **MCP tools**: `src/deepwork/mcp/tools.py`

## Quality Criteria Convention

When all quality criteria listed in a step's reviews are met, include
`<promise>✓ Quality Criteria Met</promise>` in your response.

workflows:
- name: run
summary: "Update the job.yml schema and propagate changes through all dependencies"
Expand Down
7 changes: 7 additions & 0 deletions .gemini/skills/deepwork/index.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,13 @@ description = "Start or continue DeepWork workflows using MCP tools"

Execute multi-step workflows with quality gate checkpoints.

## Terminology

A **job** is a collection of related **workflows**. For example, a "code_review" job
might contain workflows like "review_pr" and "review_diff". Users may use the terms
"job" and "workflow" somewhat interchangeably when describing the work they want done —
use context and the available workflows from `get_workflows` to determine the best match.

> **IMPORTANT**: Use the DeepWork MCP server tools. All workflow operations
> are performed through MCP tool calls and following the instructions they return,
> not by reading instructions from files.
Expand Down
18 changes: 9 additions & 9 deletions flake.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

7 changes: 7 additions & 0 deletions src/deepwork/templates/claude/skill-deepwork.md.jinja
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,13 @@ description: "Start or continue DeepWork workflows using MCP tools"

Execute multi-step workflows with quality gate checkpoints.

## Terminology

A **job** is a collection of related **workflows**. For example, a "code_review" job
might contain workflows like "review_pr" and "review_diff". Users may use the terms
"job" and "workflow" somewhat interchangeably when describing the work they want done —
use context and the available workflows from `get_workflows` to determine the best match.

> **IMPORTANT**: Use the DeepWork MCP server tools. All workflow operations
> are performed through MCP tool calls and following the instructions they return,
> not by reading instructions from files.
Expand Down
7 changes: 7 additions & 0 deletions src/deepwork/templates/gemini/skill-deepwork.md.jinja
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,13 @@ description = "Start or continue DeepWork workflows using MCP tools"

Execute multi-step workflows with quality gate checkpoints.

## Terminology

A **job** is a collection of related **workflows**. For example, a "code_review" job
might contain workflows like "review_pr" and "review_diff". Users may use the terms
"job" and "workflow" somewhat interchangeably when describing the work they want done —
use context and the available workflows from `get_workflows` to determine the best match.

> **IMPORTANT**: Use the DeepWork MCP server tools. All workflow operations
> are performed through MCP tool calls and following the instructions they return,
> not by reading instructions from files.
Expand Down