taskplane 0.19.0 → 0.20.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -100,7 +100,6 @@ Copy this template when creating a new task. Replace all `[bracketed]` fields.
100
100
  - [ ] "Must Update" docs modified
101
101
  - [ ] "Check If Affected" docs reviewed
102
102
  - [ ] Discoveries logged in STATUS.md
103
- - [ ] `.DONE` created in this folder
104
103
 
105
104
  ## Documentation Requirements
106
105
 
@@ -115,7 +114,6 @@ Copy this template when creating a new task. Replace all `[bracketed]` fields.
115
114
  - [ ] All steps complete
116
115
  - [ ] All tests passing
117
116
  - [ ] Documentation updated
118
- - [ ] `.DONE` created
119
117
 
120
118
  ## Git Commit Convention
121
119
 
@@ -208,7 +206,6 @@ this from PROMPT.md.
208
206
  - [ ] "Must Update" docs modified
209
207
  - [ ] "Check If Affected" docs reviewed
210
208
  - [ ] Discoveries logged
211
- - [ ] `.DONE` created
212
209
 
213
210
  ---
214
211
 
@@ -19,7 +19,22 @@ completing each step before moving to the next.
19
19
  4. Within that step, find the **first unchecked checkbox** (`- [ ]`)
20
20
  5. Resume from there — do NOT redo checked items (`- [x]`)
21
21
  6. When a step's items are all checked, proceed to the next incomplete step
22
- 7. If all steps are complete, report completion
22
+ 7. If all steps are complete, update STATUS.md **Status** field to `✅ Complete`
23
+ and **Current Step** to the last step name — this is your final action
24
+
25
+ ## CRITICAL: Never Exit Without Updating STATUS.md
26
+
27
+ **Every turn MUST end with a tool call.** Do NOT produce a text-only response
28
+ and stop — the task-runner interprets that as "session complete" and will
29
+ terminate your process. If you have nothing left to do:
30
+
31
+ 1. Read STATUS.md to verify all checkboxes are checked
32
+ 2. Update the Status field to `✅ Complete`
33
+ 3. Commit your final changes
34
+
35
+ **After running tests:** Immediately update STATUS.md checkboxes for the
36
+ testing step BEFORE producing any summary. Check off each item as it passes.
37
+ Do NOT run tests and then stop — always checkpoint the results first.
23
38
 
24
39
  ## Checkpoint Discipline (CRITICAL)
25
40
 
@@ -1,99 +1,98 @@
1
- # Task: EXAMPLE-001 — Hello World
2
-
3
- **Created:** {{date}}
4
- **Size:** S
5
-
6
- ## Review Level: 0 (None)
7
-
8
- **Assessment:** Trivial single-file task to verify Taskplane is working.
9
- **Score:** 0/8 — Blast radius: 0, Pattern novelty: 0, Security: 0, Reversibility: 0
10
-
11
- ## Canonical Task Folder
12
-
13
- ```
14
- {{tasks_root}}/EXAMPLE-001-hello-world/
15
- ├── PROMPT.md ← This file (immutable above --- divider)
16
- ├── STATUS.md ← Execution state (worker updates this)
17
- ├── .reviews/ ← Reviewer output (task-runner creates this)
18
- └── .DONE ← Created when complete
19
- ```
20
-
21
- ## Mission
22
-
23
- Create a simple `hello-taskplane.md` file in the project root to verify that
24
- Taskplane task execution is working correctly. This is a smoke test — if the
25
- worker can read this prompt, create the file, checkpoint progress, and mark the
26
- task done, the installation is healthy.
27
-
28
- ## Expected File Content
29
-
30
- `hello-taskplane.md` should include:
31
-
32
- - A title line (for example: `# Hello from Taskplane`)
33
- - A line containing the task ID: `EXAMPLE-001`
34
- - A line containing today's date
35
-
36
- ## Dependencies
37
-
38
- - **None**
39
-
40
- ## Context to Read First
41
-
42
- _No additional context needed._
43
-
44
- ## Environment
45
-
46
- - **Workspace:** Project root
47
- - **Services required:** None
48
-
49
- ## File Scope
50
-
51
- - `hello-taskplane.md`
52
-
53
- ## Steps
54
-
55
- ### Step 0: Preflight
56
-
57
- - [ ] Verify this PROMPT.md is readable
58
- - [ ] Verify STATUS.md exists in the same folder
59
-
60
- ### Step 1: Create Hello File
61
-
62
- - [ ] Create `hello-taskplane.md` in the project root
63
- - [ ] Add a title plus lines containing today's date and task ID `EXAMPLE-001`
64
-
65
- ### Step 2: Verification
66
-
67
- - [ ] Verify `hello-taskplane.md` exists and matches the expected content
68
-
69
- ### Step 3: Delivery
70
-
71
- - [ ] `.DONE` created in this folder
72
-
73
- ## Documentation Requirements
74
-
75
- **Must Update:** None
76
- **Check If Affected:** None
77
-
78
- ## Completion Criteria
79
-
80
- - [ ] `hello-taskplane.md` exists in the project root
81
- - [ ] `hello-taskplane.md` includes a title, task ID (`EXAMPLE-001`), and current date
82
- - [ ] `.DONE` exists in the task folder
83
-
84
- ## Git Commit Convention
85
-
86
- - **Implementation:** `feat(EXAMPLE-001): description`
87
- - **Checkpoints:** `checkpoint: EXAMPLE-001 description`
88
-
89
- ## Do NOT
90
-
91
- - Modify any existing project files
92
- - Create files outside the project root
93
- - Over-engineer this — it's a smoke test
94
-
95
- ---
96
-
97
- ## Amendments (Added During Execution)
98
-
99
- <!-- Workers add amendments here if issues discovered during execution. -->
1
+ # Task: EXAMPLE-001 — Hello World
2
+
3
+ **Created:** {{date}}
4
+ **Size:** S
5
+
6
+ ## Review Level: 0 (None)
7
+
8
+ **Assessment:** Trivial single-file task to verify Taskplane is working.
9
+ **Score:** 0/8 — Blast radius: 0, Pattern novelty: 0, Security: 0, Reversibility: 0
10
+
11
+ ## Canonical Task Folder
12
+
13
+ ```
14
+ {{tasks_root}}/EXAMPLE-001-hello-world/
15
+ ├── PROMPT.md ← This file (immutable above --- divider)
16
+ ├── STATUS.md ← Execution state (worker updates this)
17
+ ├── .reviews/ ← Reviewer output (task-runner creates this)
18
+ └── .DONE ← Created when complete
19
+ ```
20
+
21
+ ## Mission
22
+
23
+ Create a simple `hello-taskplane.md` file in the project root to verify that
24
+ Taskplane task execution is working correctly. This is a smoke test — if the
25
+ worker can read this prompt, create the file, checkpoint progress, and mark the
26
+ task done, the installation is healthy.
27
+
28
+ ## Expected File Content
29
+
30
+ `hello-taskplane.md` should include:
31
+
32
+ - A title line (for example: `# Hello from Taskplane`)
33
+ - A line containing the task ID: `EXAMPLE-001`
34
+ - A line containing today's date
35
+
36
+ ## Dependencies
37
+
38
+ - **None**
39
+
40
+ ## Context to Read First
41
+
42
+ _No additional context needed._
43
+
44
+ ## Environment
45
+
46
+ - **Workspace:** Project root
47
+ - **Services required:** None
48
+
49
+ ## File Scope
50
+
51
+ - `hello-taskplane.md`
52
+
53
+ ## Steps
54
+
55
+ ### Step 0: Preflight
56
+
57
+ - [ ] Verify this PROMPT.md is readable
58
+ - [ ] Verify STATUS.md exists in the same folder
59
+
60
+ ### Step 1: Create Hello File
61
+
62
+ - [ ] Create `hello-taskplane.md` in the project root
63
+ - [ ] Add a title plus lines containing today's date and task ID `EXAMPLE-001`
64
+
65
+ ### Step 2: Verification
66
+
67
+ - [ ] Verify `hello-taskplane.md` exists and matches the expected content
68
+
69
+ ### Step 3: Delivery
70
+
71
+
72
+
73
+ ## Documentation Requirements
74
+
75
+ **Must Update:** None
76
+ **Check If Affected:** None
77
+
78
+ ## Completion Criteria
79
+
80
+ - [ ] `hello-taskplane.md` exists in the project root
81
+ - [ ] `hello-taskplane.md` includes a title, task ID (`EXAMPLE-001`), and current date
82
+
83
+ ## Git Commit Convention
84
+
85
+ - **Implementation:** `feat(EXAMPLE-001): description`
86
+ - **Checkpoints:** `checkpoint: EXAMPLE-001 description`
87
+
88
+ ## Do NOT
89
+
90
+ - Modify any existing project files
91
+ - Create files outside the project root
92
+ - Over-engineer this it's a smoke test
93
+
94
+ ---
95
+
96
+ ## Amendments (Added During Execution)
97
+
98
+ <!-- Workers add amendments here if issues discovered during execution. -->
@@ -1,73 +1,73 @@
1
- # EXAMPLE-001: Hello World — Status
2
-
3
- **Current Step:** Not Started
4
- **Status:** 🔵 Ready for Execution
5
- **Last Updated:** {{date}}
6
- **Review Level:** 0
7
- **Review Counter:** 0
8
- **Iteration:** 0
9
- **Size:** S
10
-
11
- ---
12
-
13
- ### Step 0: Preflight
14
- **Status:** ⬜ Not Started
15
-
16
- - [ ] Verify PROMPT.md is readable
17
- - [ ] Verify STATUS.md exists
18
-
19
- ---
20
-
21
- ### Step 1: Create Hello File
22
- **Status:** ⬜ Not Started
23
-
24
- - [ ] Create `hello-taskplane.md` in project root
25
- - [ ] Add title, date, and task ID (EXAMPLE-001)
26
-
27
- ---
28
-
29
- ### Step 2: Verification
30
- **Status:** ⬜ Not Started
31
-
32
- - [ ] Verify file exists and matches expected content
33
-
34
- ---
35
-
36
- ### Step 3: Delivery
37
- **Status:** ⬜ Not Started
38
-
39
- - [ ] `.DONE` created
40
-
41
- ---
42
-
43
- ## Reviews
44
-
45
- | # | Type | Step | Verdict | File |
46
- |---|------|------|---------|------|
47
-
48
- ---
49
-
50
- ## Discoveries
51
-
52
- | Discovery | Disposition | Location |
53
- |-----------|-------------|----------|
54
-
55
- ---
56
-
57
- ## Execution Log
58
-
59
- | Timestamp | Action | Outcome |
60
- |-----------|--------|---------|
61
- | {{date}} | Task staged | PROMPT.md and STATUS.md created |
62
-
63
- ---
64
-
65
- ## Blockers
66
-
67
- *None*
68
-
69
- ---
70
-
71
- ## Notes
72
-
73
- *This is an example task created by `taskplane init`. Delete it after verifying your setup works.*
1
+ # EXAMPLE-001: Hello World — Status
2
+
3
+ **Current Step:** Not Started
4
+ **Status:** 🔵 Ready for Execution
5
+ **Last Updated:** {{date}}
6
+ **Review Level:** 0
7
+ **Review Counter:** 0
8
+ **Iteration:** 0
9
+ **Size:** S
10
+
11
+ ---
12
+
13
+ ### Step 0: Preflight
14
+ **Status:** ⬜ Not Started
15
+
16
+ - [ ] Verify PROMPT.md is readable
17
+ - [ ] Verify STATUS.md exists
18
+
19
+ ---
20
+
21
+ ### Step 1: Create Hello File
22
+ **Status:** ⬜ Not Started
23
+
24
+ - [ ] Create `hello-taskplane.md` in project root
25
+ - [ ] Add title, date, and task ID (EXAMPLE-001)
26
+
27
+ ---
28
+
29
+ ### Step 2: Verification
30
+ **Status:** ⬜ Not Started
31
+
32
+ - [ ] Verify file exists and matches expected content
33
+
34
+ ---
35
+
36
+ ### Step 3: Delivery
37
+ **Status:** ⬜ Not Started
38
+
39
+
40
+
41
+ ---
42
+
43
+ ## Reviews
44
+
45
+ | # | Type | Step | Verdict | File |
46
+ |---|------|------|---------|------|
47
+
48
+ ---
49
+
50
+ ## Discoveries
51
+
52
+ | Discovery | Disposition | Location |
53
+ |-----------|-------------|----------|
54
+
55
+ ---
56
+
57
+ ## Execution Log
58
+
59
+ | Timestamp | Action | Outcome |
60
+ |-----------|--------|---------|
61
+ | {{date}} | Task staged | PROMPT.md and STATUS.md created |
62
+
63
+ ---
64
+
65
+ ## Blockers
66
+
67
+ *None*
68
+
69
+ ---
70
+
71
+ ## Notes
72
+
73
+ *This is an example task created by `taskplane init`. Delete it after verifying your setup works.*
@@ -1,98 +1,97 @@
1
- # Task: EXAMPLE-002 — Parallel Smoke
2
-
3
- **Created:** {{date}}
4
- **Size:** S
5
-
6
- ## Review Level: 0 (None)
7
-
8
- **Assessment:** Trivial parallel-safe smoke task to demonstrate orchestrator lanes.
9
- **Score:** 0/8 — Blast radius: 0, Pattern novelty: 0, Security: 0, Reversibility: 0
10
-
11
- ## Canonical Task Folder
12
-
13
- ```
14
- {{tasks_root}}/EXAMPLE-002-parallel-smoke/
15
- ├── PROMPT.md ← This file (immutable above --- divider)
16
- ├── STATUS.md ← Execution state (worker updates this)
17
- ├── .reviews/ ← Reviewer output (task-runner creates this)
18
- └── .DONE ← Created when complete
19
- ```
20
-
21
- ## Mission
22
-
23
- Create a simple `hello-taskplane-2.md` file in the project root. This task is
24
- intentionally independent from EXAMPLE-001 so both can run in parallel when
25
- using `/orch`.
26
-
27
- ## Expected File Content
28
-
29
- `hello-taskplane-2.md` should include:
30
-
31
- - A title line (for example: `# Parallel Hello from Taskplane`)
32
- - A line containing the task ID: `EXAMPLE-002`
33
- - A short note that this task is parallel-safe
34
-
35
- ## Dependencies
36
-
37
- - **None**
38
-
39
- ## Context to Read First
40
-
41
- _No additional context needed._
42
-
43
- ## Environment
44
-
45
- - **Workspace:** Project root
46
- - **Services required:** None
47
-
48
- ## File Scope
49
-
50
- - `hello-taskplane-2.md`
51
-
52
- ## Steps
53
-
54
- ### Step 0: Preflight
55
-
56
- - [ ] Verify this PROMPT.md is readable
57
- - [ ] Verify STATUS.md exists in the same folder
58
-
59
- ### Step 1: Create Parallel Hello File
60
-
61
- - [ ] Create `hello-taskplane-2.md` in the project root
62
- - [ ] Add title plus lines containing task ID `EXAMPLE-002` and a parallel-safe note
63
-
64
- ### Step 2: Verification
65
-
66
- - [ ] Verify `hello-taskplane-2.md` exists and matches the expected content
67
-
68
- ### Step 3: Delivery
69
-
70
- - [ ] `.DONE` created in this folder
71
-
72
- ## Documentation Requirements
73
-
74
- **Must Update:** None
75
- **Check If Affected:** None
76
-
77
- ## Completion Criteria
78
-
79
- - [ ] `hello-taskplane-2.md` exists in the project root
80
- - [ ] `hello-taskplane-2.md` includes a title, task ID (`EXAMPLE-002`), and a parallel-safe note
81
- - [ ] `.DONE` exists in the task folder
82
-
83
- ## Git Commit Convention
84
-
85
- - **Implementation:** `feat(EXAMPLE-002): description`
86
- - **Checkpoints:** `checkpoint: EXAMPLE-002 description`
87
-
88
- ## Do NOT
89
-
90
- - Modify any existing project files
91
- - Create files outside the project root
92
- - Add dependencies between EXAMPLE-001 and EXAMPLE-002
93
-
94
- ---
95
-
96
- ## Amendments (Added During Execution)
97
-
98
- <!-- Workers add amendments here if issues discovered during execution. -->
1
+ # Task: EXAMPLE-002 — Parallel Smoke
2
+
3
+ **Created:** {{date}}
4
+ **Size:** S
5
+
6
+ ## Review Level: 0 (None)
7
+
8
+ **Assessment:** Trivial parallel-safe smoke task to demonstrate orchestrator lanes.
9
+ **Score:** 0/8 — Blast radius: 0, Pattern novelty: 0, Security: 0, Reversibility: 0
10
+
11
+ ## Canonical Task Folder
12
+
13
+ ```
14
+ {{tasks_root}}/EXAMPLE-002-parallel-smoke/
15
+ ├── PROMPT.md ← This file (immutable above --- divider)
16
+ ├── STATUS.md ← Execution state (worker updates this)
17
+ ├── .reviews/ ← Reviewer output (task-runner creates this)
18
+ └── .DONE ← Created when complete
19
+ ```
20
+
21
+ ## Mission
22
+
23
+ Create a simple `hello-taskplane-2.md` file in the project root. This task is
24
+ intentionally independent from EXAMPLE-001 so both can run in parallel when
25
+ using `/orch`.
26
+
27
+ ## Expected File Content
28
+
29
+ `hello-taskplane-2.md` should include:
30
+
31
+ - A title line (for example: `# Parallel Hello from Taskplane`)
32
+ - A line containing the task ID: `EXAMPLE-002`
33
+ - A short note that this task is parallel-safe
34
+
35
+ ## Dependencies
36
+
37
+ - **None**
38
+
39
+ ## Context to Read First
40
+
41
+ _No additional context needed._
42
+
43
+ ## Environment
44
+
45
+ - **Workspace:** Project root
46
+ - **Services required:** None
47
+
48
+ ## File Scope
49
+
50
+ - `hello-taskplane-2.md`
51
+
52
+ ## Steps
53
+
54
+ ### Step 0: Preflight
55
+
56
+ - [ ] Verify this PROMPT.md is readable
57
+ - [ ] Verify STATUS.md exists in the same folder
58
+
59
+ ### Step 1: Create Parallel Hello File
60
+
61
+ - [ ] Create `hello-taskplane-2.md` in the project root
62
+ - [ ] Add title plus lines containing task ID `EXAMPLE-002` and a parallel-safe note
63
+
64
+ ### Step 2: Verification
65
+
66
+ - [ ] Verify `hello-taskplane-2.md` exists and matches the expected content
67
+
68
+ ### Step 3: Delivery
69
+
70
+
71
+
72
+ ## Documentation Requirements
73
+
74
+ **Must Update:** None
75
+ **Check If Affected:** None
76
+
77
+ ## Completion Criteria
78
+
79
+ - [ ] `hello-taskplane-2.md` exists in the project root
80
+ - [ ] `hello-taskplane-2.md` includes a title, task ID (`EXAMPLE-002`), and a parallel-safe note
81
+
82
+ ## Git Commit Convention
83
+
84
+ - **Implementation:** `feat(EXAMPLE-002): description`
85
+ - **Checkpoints:** `checkpoint: EXAMPLE-002 description`
86
+
87
+ ## Do NOT
88
+
89
+ - Modify any existing project files
90
+ - Create files outside the project root
91
+ - Add dependencies between EXAMPLE-001 and EXAMPLE-002
92
+
93
+ ---
94
+
95
+ ## Amendments (Added During Execution)
96
+
97
+ <!-- Workers add amendments here if issues discovered during execution. -->