You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix test for updated make_new_job.sh usage message
- Updated test to expect "Examples:" (plural) instead of "Example:"
- All 678 tests now passing
Co-authored-by: ncrmro <8276365+ncrmro@users.noreply.github.com>
Copy file name to clipboardExpand all lines: .claude/skills/deepwork_jobs.implement/SKILL.md
+40-17Lines changed: 40 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,31 +32,52 @@ Generate the DeepWork job directory structure and instruction files for each ste
32
32
33
33
Read the `job.yml` specification file and create all the necessary files to make the job functional, including directory structure and step instruction files. Then sync the commands to make them available.
34
34
35
-
### Step 1: Create Directory Structure Using Script
35
+
### Step 1: Determine Installation Scope
36
36
37
-
Run the `make_new_job.sh` script to create the standard directory structure:
37
+
**Ask the user where they want to install this job using structured questions:**
38
38
39
+
Present two options:
40
+
1.**Local** - Install in this project only (`.deepwork/jobs/`)
41
+
2.**Global** - Install for all projects in your user config (`~/.config/deepwork/jobs/`)
42
+
43
+
**Guidance for users:**
44
+
- Choose **local** if the job is specific to this project or you want to version control it
45
+
- Choose **global** if the job is reusable across multiple projects (e.g., a general "code review" or "documentation" workflow)
46
+
47
+
### Step 2: Create Directory Structure Using Script
48
+
49
+
Run the `make_new_job.sh` script to create the standard directory structure with the chosen scope:
**Note**: If the directory already exists (e.g., job.yml was created by define step), you can skip this step or manually create the additional directories:
-`~/.config/deepwork/jobs` (or `$XDG_CONFIG_HOME/deepwork/jobs`) for global scope
71
+
72
+
**Note**: If the directory already exists (e.g., job.yml was created by define step), you can skip this step or manually create the additional directories in the appropriate scope location.
73
+
74
+
### Step 3: Read and Validate the Specification
57
75
58
76
1.**Locate the job.yml file**
59
-
- Read `.deepwork/jobs/[job_name]/job.yml` from the review_job_spec step
Copy file name to clipboardExpand all lines: .deepwork/jobs/deepwork_jobs/steps/implement.md
+40-17Lines changed: 40 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,31 +8,52 @@ Generate the DeepWork job directory structure and instruction files for each ste
8
8
9
9
Read the `job.yml` specification file and create all the necessary files to make the job functional, including directory structure and step instruction files. Then sync the commands to make them available.
10
10
11
-
### Step 1: Create Directory Structure Using Script
11
+
### Step 1: Determine Installation Scope
12
12
13
-
Run the `make_new_job.sh` script to create the standard directory structure:
13
+
**Ask the user where they want to install this job using structured questions:**
14
14
15
+
Present two options:
16
+
1.**Local** - Install in this project only (`.deepwork/jobs/`)
17
+
2.**Global** - Install for all projects in your user config (`~/.config/deepwork/jobs/`)
18
+
19
+
**Guidance for users:**
20
+
- Choose **local** if the job is specific to this project or you want to version control it
21
+
- Choose **global** if the job is reusable across multiple projects (e.g., a general "code review" or "documentation" workflow)
22
+
23
+
### Step 2: Create Directory Structure Using Script
24
+
25
+
Run the `make_new_job.sh` script to create the standard directory structure with the chosen scope:
**Note**: If the directory already exists (e.g., job.yml was created by define step), you can skip this step or manually create the additional directories:
-`~/.config/deepwork/jobs` (or `$XDG_CONFIG_HOME/deepwork/jobs`) for global scope
47
+
48
+
**Note**: If the directory already exists (e.g., job.yml was created by define step), you can skip this step or manually create the additional directories in the appropriate scope location.
49
+
50
+
### Step 3: Read and Validate the Specification
33
51
34
52
1.**Locate the job.yml file**
35
-
- Read `.deepwork/jobs/[job_name]/job.yml` from the review_job_spec step
Copy file name to clipboardExpand all lines: .gemini/skills/deepwork_jobs/implement.toml
+40-17Lines changed: 40 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -32,31 +32,52 @@ Generate the DeepWork job directory structure and instruction files for each ste
32
32
33
33
Read the `job.yml` specification file and create all the necessary files to make the job functional, including directory structure and step instruction files. Then sync the commands to make them available.
34
34
35
-
### Step 1: Create Directory Structure Using Script
35
+
### Step 1: Determine Installation Scope
36
36
37
-
Run the `make_new_job.sh` script to create the standard directory structure:
37
+
**Ask the user where they want to install this job using structured questions:**
38
38
39
+
Present two options:
40
+
1. **Local** - Install in this project only (`.deepwork/jobs/`)
41
+
2. **Global** - Install for all projects in your user config (`~/.config/deepwork/jobs/`)
42
+
43
+
**Guidance for users:**
44
+
- Choose **local** if the job is specific to this project or you want to version control it
45
+
- Choose **global** if the job is reusable across multiple projects (e.g., a general "code review" or "documentation" workflow)
46
+
47
+
### Step 2: Create Directory Structure Using Script
48
+
49
+
Run the `make_new_job.sh` script to create the standard directory structure with the chosen scope:
**Note**: If the directory already exists (e.g., job.yml was created by define step), you can skip this step or manually create the additional directories:
- `~/.config/deepwork/jobs` (or `$XDG_CONFIG_HOME/deepwork/jobs`) for global scope
71
+
72
+
**Note**: If the directory already exists (e.g., job.yml was created by define step), you can skip this step or manually create the additional directories in the appropriate scope location.
73
+
74
+
### Step 3: Read and Validate the Specification
57
75
58
76
1. **Locate the job.yml file**
59
-
- Read `.deepwork/jobs/[job_name]/job.yml` from the review_job_spec step
0 commit comments