@jiggai/recipes 0.4.19 → 0.4.21

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.
Files changed (16) hide show
  1. package/docs/WORKFLOW_FIXES_2026-03-13.md +23 -0
  2. package/index.ts +130 -29
  3. package/openclaw.plugin.json +1 -1
  4. package/package.json +1 -1
  5. package/recipes/default/business-team.md +28 -28
  6. package/recipes/default/customer-support-team.md +26 -26
  7. package/recipes/default/development-team.md +46 -46
  8. package/recipes/default/marketing-team.md +87 -99
  9. package/recipes/default/product-team.md +28 -28
  10. package/recipes/default/research-team.md +26 -26
  11. package/recipes/default/social-team.md +44 -44
  12. package/recipes/default/workflow-runner-addon.md +3 -3
  13. package/recipes/default/writing-team.md +26 -26
  14. package/src/lib/workflows/workflow-queue.ts +116 -85
  15. package/src/lib/workflows/workflow-runner.ts +110 -123
  16. package/src/lib/workspace.ts +20 -0
package/recipes/default/product-team.md CHANGED
@@ -63,16 +63,16 @@ templates:
63
63
 
64
64
  ## Where to write things
65
65
  - Ticket = source of truth for a unit of work.
66
- - `notes/plan.md` + `shared-context/priorities.md` are **lead-curated**.
67
- - `notes/status.md` is **append-only** and updated after each work session (3–5 bullets).
68
- - `shared-context/agent-outputs/` is **append-only** logs/output.
66
+ - `../notes/plan.md` + `../shared-context/priorities.md` are **lead-curated**.
67
+ - `../notes/status.md` is **append-only** and updated after each work session (3–5 bullets).
68
+ - `../shared-context/agent-outputs/` is **append-only** logs/output.
69
69
 
70
70
  ## End-of-session checklist (everyone)
71
71
  After meaningful work:
72
72
  1) Update the ticket with what changed + how to verify + rollback.
73
73
  2) Add a dated note in the ticket `## Comments`.
74
- 3) Append 3–5 bullets to `notes/status.md`.
75
- 4) Append logs/output to `shared-context/agent-outputs/`.
74
+ 3) Append 3–5 bullets to `../notes/status.md`.
75
+ 4) Append logs/output to `../shared-context/agent-outputs/`.
76
76
 
77
77
  sharedContext.plan: |
78
78
  # Plan (lead-curated)
@@ -105,16 +105,16 @@ templates:
105
105
  - `roles/<role>/memory/YYYY-MM-DD.md` (daily log)
106
106
 
107
107
  ## Plan vs status (team coordination)
108
- - `notes/plan.md` + `shared-context/priorities.md` are lead-curated
109
- - `notes/status.md` is append-only roll-up (everyone appends)
108
+ - `../notes/plan.md` + `../shared-context/priorities.md` are lead-curated
109
+ - `../notes/status.md` is append-only roll-up (everyone appends)
110
110
 
111
111
  ## Outputs / artifacts
112
112
  - `roles/<role>/agent-outputs/` (append-only)
113
- - `shared-context/agent-outputs/` (optional team-level)
113
+ - `../shared-context/agent-outputs/` (team-level, read/write from role via `../`)
114
114
 
115
115
  ## Role work loop contract (safe-idle)
116
116
  - No-op unless explicit queued work exists for the role.
117
- - If work happens, write back in order: ticket → `notes/status.md` → `roles/<role>/agent-outputs/`.
117
+ - If work happens, write back in order: ticket → `../notes/status.md` → `roles/<role>/agent-outputs/`.
118
118
 
119
119
  sharedContext.priorities: |
120
120
  # Priorities (lead-curated)
@@ -147,24 +147,24 @@ templates:
147
147
 
148
148
  Before you act:
149
149
  1) Read:
150
- - `notes/plan.md`
151
- - `notes/status.md`
152
- - `shared-context/priorities.md`
150
+ - `../notes/plan.md`
151
+ - `../notes/status.md`
152
+ - `../shared-context/priorities.md`
153
153
  - the relevant ticket(s)
154
154
 
155
155
  After you act:
156
156
  1) Write back:
157
157
  - Update tickets with decisions/assignments.
158
- - Keep `notes/status.md` current (3–5 bullets per active ticket).
158
+ - Keep `../notes/status.md` current (3–5 bullets per active ticket).
159
159
 
160
160
  ## Curator model
161
161
 
162
162
  You are the curator of:
163
- - `notes/plan.md`
164
- - `shared-context/priorities.md`
163
+ - `../notes/plan.md`
164
+ - `../shared-context/priorities.md`
165
165
 
166
166
  Everyone else should append to:
167
- - `shared-context/agent-outputs/` (append-only)
167
+ - `../shared-context/agent-outputs/` (append-only)
168
168
  - `shared-context/feedback/`
169
169
 
170
170
  Your job is to periodically distill those inputs into the curated files.
@@ -179,8 +179,8 @@ templates:
179
179
  - `work/in-progress/` — tickets currently being executed
180
180
  - `work/testing/` — tickets awaiting QA verification
181
181
  - `work/done/` — completed tickets + completion notes
182
- - `notes/plan.md` — current plan / priorities (curated)
183
- - `notes/status.md` — current status snapshot
182
+ - `../notes/plan.md` — current plan / priorities (curated)
183
+ - `../notes/status.md` — current status snapshot
184
184
  - `shared-context/` — shared context + append-only outputs
185
185
 
186
186
  ### Ticket numbering (critical)
@@ -197,8 +197,8 @@ templates:
197
197
 
198
198
  ### Your responsibilities
199
199
  - For every new request in `inbox/`, create a normalized ticket in `work/backlog/`.
200
- - Curate `notes/plan.md` and `shared-context/priorities.md`.
201
- - Keep `notes/status.md` updated.
200
+ - Curate `../notes/plan.md` and `../shared-context/priorities.md`.
201
+ - Keep `../notes/status.md` updated.
202
202
  - When work is ready for QA, move the ticket to `work/testing/` and assign it to the tester.
203
203
  - Only after QA verification, move the ticket to `work/done/` (or use `openclaw recipes complete`).
204
204
  - When a completion appears in `work/done/`, write a short summary into `outbox/`.
@@ -219,8 +219,8 @@ templates:
219
219
  ## Guardrails (read → act → write)
220
220
  Before you act:
221
221
  1) Read:
222
- - `notes/plan.md`
223
- - `notes/status.md`
222
+ - `../notes/plan.md`
223
+ - `../notes/status.md`
224
224
  - relevant ticket(s) in `work/in-progress/`
225
225
  - any relevant shared context under `shared-context/`
226
226
 
@@ -249,8 +249,8 @@ templates:
249
249
  ## Guardrails (read → act → write)
250
250
  Before you act:
251
251
  1) Read:
252
- - `notes/plan.md`
253
- - `notes/status.md`
252
+ - `../notes/plan.md`
253
+ - `../notes/status.md`
254
254
  - relevant ticket(s) in `work/in-progress/`
255
255
  - any relevant shared context under `shared-context/`
256
256
 
@@ -279,8 +279,8 @@ templates:
279
279
  ## Guardrails (read → act → write)
280
280
  Before you act:
281
281
  1) Read:
282
- - `notes/plan.md`
283
- - `notes/status.md`
282
+ - `../notes/plan.md`
283
+ - `../notes/status.md`
284
284
  - relevant ticket(s) in `work/in-progress/`
285
285
  - any relevant shared context under `shared-context/`
286
286
 
@@ -309,8 +309,8 @@ templates:
309
309
  ## Guardrails (read → act → write)
310
310
  Before you act:
311
311
  1) Read:
312
- - `notes/plan.md`
313
- - `notes/status.md`
312
+ - `../notes/plan.md`
313
+ - `../notes/status.md`
314
314
  - relevant ticket(s) in `work/in-progress/`
315
315
  - any relevant shared context under `shared-context/`
316
316
 
package/recipes/default/research-team.md CHANGED
@@ -57,16 +57,16 @@ templates:
57
57
 
58
58
  ## Where to write things
59
59
  - Ticket = source of truth for a unit of work.
60
- - `notes/plan.md` + `shared-context/priorities.md` are **lead-curated**.
61
- - `notes/status.md` is **append-only** and updated after each work session (3–5 bullets).
62
- - `shared-context/agent-outputs/` is **append-only** logs/output.
60
+ - `../notes/plan.md` + `../shared-context/priorities.md` are **lead-curated**.
61
+ - `../notes/status.md` is **append-only** and updated after each work session (3–5 bullets).
62
+ - `../shared-context/agent-outputs/` is **append-only** logs/output.
63
63
 
64
64
  ## End-of-session checklist (everyone)
65
65
  After meaningful work:
66
66
  1) Update the ticket with what changed + how to verify + rollback.
67
67
  2) Add a dated note in the ticket `## Comments`.
68
- 3) Append 3–5 bullets to `notes/status.md`.
69
- 4) Append logs/output to `shared-context/agent-outputs/`.
68
+ 3) Append 3–5 bullets to `../notes/status.md`.
69
+ 4) Append logs/output to `../shared-context/agent-outputs/`.
70
70
 
71
71
  sharedContext.plan: |
72
72
  # Plan (lead-curated)
@@ -99,16 +99,16 @@ templates:
99
99
  - `roles/<role>/memory/YYYY-MM-DD.md` (daily log)
100
100
 
101
101
  ## Plan vs status (team coordination)
102
- - `notes/plan.md` + `shared-context/priorities.md` are lead-curated
103
- - `notes/status.md` is append-only roll-up (everyone appends)
102
+ - `../notes/plan.md` + `../shared-context/priorities.md` are lead-curated
103
+ - `../notes/status.md` is append-only roll-up (everyone appends)
104
104
 
105
105
  ## Outputs / artifacts
106
106
  - `roles/<role>/agent-outputs/` (append-only)
107
- - `shared-context/agent-outputs/` (optional team-level)
107
+ - `../shared-context/agent-outputs/` (team-level, read/write from role via `../`)
108
108
 
109
109
  ## Role work loop contract (safe-idle)
110
110
  - No-op unless explicit queued work exists for the role.
111
- - If work happens, write back in order: ticket → `notes/status.md` → `roles/<role>/agent-outputs/`.
111
+ - If work happens, write back in order: ticket → `../notes/status.md` → `roles/<role>/agent-outputs/`.
112
112
 
113
113
  sharedContext.priorities: |
114
114
  # Priorities (lead-curated)
@@ -141,24 +141,24 @@ templates:
141
141
 
142
142
  Before you act:
143
143
  1) Read:
144
- - `notes/plan.md`
145
- - `notes/status.md`
146
- - `shared-context/priorities.md`
144
+ - `../notes/plan.md`
145
+ - `../notes/status.md`
146
+ - `../shared-context/priorities.md`
147
147
  - the relevant ticket(s)
148
148
 
149
149
  After you act:
150
150
  1) Write back:
151
151
  - Update tickets with decisions/assignments.
152
- - Keep `notes/status.md` current (3–5 bullets per active ticket).
152
+ - Keep `../notes/status.md` current (3–5 bullets per active ticket).
153
153
 
154
154
  ## Curator model
155
155
 
156
156
  You are the curator of:
157
- - `notes/plan.md`
158
- - `shared-context/priorities.md`
157
+ - `../notes/plan.md`
158
+ - `../shared-context/priorities.md`
159
159
 
160
160
  Everyone else should append to:
161
- - `shared-context/agent-outputs/` (append-only)
161
+ - `../shared-context/agent-outputs/` (append-only)
162
162
  - `shared-context/feedback/`
163
163
 
164
164
  Your job is to periodically distill those inputs into the curated files.
@@ -173,8 +173,8 @@ templates:
173
173
  - `work/in-progress/` — tickets currently being executed
174
174
  - `work/testing/` — tickets awaiting QA verification
175
175
  - `work/done/` — completed tickets + completion notes
176
- - `notes/plan.md` — current plan / priorities (curated)
177
- - `notes/status.md` — current status snapshot
176
+ - `../notes/plan.md` — current plan / priorities (curated)
177
+ - `../notes/status.md` — current status snapshot
178
178
  - `shared-context/` — shared context + append-only outputs
179
179
 
180
180
  ### Ticket numbering (critical)
@@ -191,8 +191,8 @@ templates:
191
191
 
192
192
  ### Your responsibilities
193
193
  - For every new request in `inbox/`, create a normalized ticket in `work/backlog/`.
194
- - Curate `notes/plan.md` and `shared-context/priorities.md`.
195
- - Keep `notes/status.md` updated.
194
+ - Curate `../notes/plan.md` and `../shared-context/priorities.md`.
195
+ - Keep `../notes/status.md` updated.
196
196
  - When work is ready for QA, move the ticket to `work/testing/` and assign it to the tester.
197
197
  - Only after QA verification, move the ticket to `work/done/` (or use `openclaw recipes complete`).
198
198
  - When a completion appears in `work/done/`, write a short summary into `outbox/`.
@@ -216,8 +216,8 @@ templates:
216
216
  ## Guardrails (read → act → write)
217
217
  Before you act:
218
218
  1) Read:
219
- - `notes/plan.md`
220
- - `notes/status.md`
219
+ - `../notes/plan.md`
220
+ - `../notes/status.md`
221
221
  - relevant ticket(s) in `work/in-progress/`
222
222
  - any relevant shared context under `shared-context/`
223
223
 
@@ -246,8 +246,8 @@ templates:
246
246
  ## Guardrails (read → act → write)
247
247
  Before you act:
248
248
  1) Read:
249
- - `notes/plan.md`
250
- - `notes/status.md`
249
+ - `../notes/plan.md`
250
+ - `../notes/status.md`
251
251
  - relevant ticket(s) in `work/in-progress/`
252
252
  - any relevant shared context under `shared-context/`
253
253
 
@@ -276,8 +276,8 @@ templates:
276
276
  ## Guardrails (read → act → write)
277
277
  Before you act:
278
278
  1) Read:
279
- - `notes/plan.md`
280
- - `notes/status.md`
279
+ - `../notes/plan.md`
280
+ - `../notes/status.md`
281
281
  - relevant ticket(s) in `work/in-progress/`
282
282
  - any relevant shared context under `shared-context/`
283
283
 
package/recipes/default/social-team.md CHANGED
@@ -70,16 +70,16 @@ templates:
70
70
 
71
71
  ## Where to write things
72
72
  - Ticket = source of truth for a unit of work.
73
- - `notes/plan.md` + `shared-context/priorities.md` are **lead-curated**.
74
- - `notes/status.md` is **append-only** and updated after each work session (3–5 bullets).
75
- - `shared-context/agent-outputs/` is **append-only** logs/output.
73
+ - `../notes/plan.md` + `../shared-context/priorities.md` are **lead-curated**.
74
+ - `../notes/status.md` is **append-only** and updated after each work session (3–5 bullets).
75
+ - `../shared-context/agent-outputs/` is **append-only** logs/output.
76
76
 
77
77
  ## End-of-session checklist (everyone)
78
78
  After meaningful work:
79
79
  1) Update the ticket with what changed + how to verify + rollback.
80
80
  2) Add a dated note in the ticket `## Comments`.
81
- 3) Append 3–5 bullets to `notes/status.md`.
82
- 4) Append logs/output to `shared-context/agent-outputs/`.
81
+ 3) Append 3–5 bullets to `../notes/status.md`.
82
+ 4) Append logs/output to `../shared-context/agent-outputs/`.
83
83
 
84
84
  sharedContext.plan: |
85
85
  # Plan (lead-curated)
@@ -112,16 +112,16 @@ templates:
112
112
  - `roles/<role>/memory/YYYY-MM-DD.md` (daily log)
113
113
 
114
114
  ## Plan vs status (team coordination)
115
- - `notes/plan.md` + `shared-context/priorities.md` are lead-curated
116
- - `notes/status.md` is append-only roll-up (everyone appends)
115
+ - `../notes/plan.md` + `../shared-context/priorities.md` are lead-curated
116
+ - `../notes/status.md` is append-only roll-up (everyone appends)
117
117
 
118
118
  ## Outputs / artifacts
119
119
  - `roles/<role>/agent-outputs/` (append-only)
120
- - `shared-context/agent-outputs/` (optional team-level)
120
+ - `../shared-context/agent-outputs/` (team-level, read/write from role via `../`)
121
121
 
122
122
  ## Role work loop contract (safe-idle)
123
123
  - No-op unless explicit queued work exists for the role.
124
- - If work happens, write back in order: ticket → `notes/status.md` → `roles/<role>/agent-outputs/`.
124
+ - If work happens, write back in order: ticket → `../notes/status.md` → `roles/<role>/agent-outputs/`.
125
125
 
126
126
  sharedContext.priorities: |
127
127
  # Priorities (lead-curated)
@@ -154,24 +154,24 @@ templates:
154
154
 
155
155
  Before you act:
156
156
  1) Read:
157
- - `notes/plan.md`
158
- - `notes/status.md`
159
- - `shared-context/priorities.md`
157
+ - `../notes/plan.md`
158
+ - `../notes/status.md`
159
+ - `../shared-context/priorities.md`
160
160
  - the relevant ticket(s)
161
161
 
162
162
  After you act:
163
163
  1) Write back:
164
164
  - Update tickets with decisions/assignments.
165
- - Keep `notes/status.md` current (3–5 bullets per active ticket).
165
+ - Keep `../notes/status.md` current (3–5 bullets per active ticket).
166
166
 
167
167
  ## Curator model
168
168
 
169
169
  You are the curator of:
170
- - `notes/plan.md`
171
- - `shared-context/priorities.md`
170
+ - `../notes/plan.md`
171
+ - `../shared-context/priorities.md`
172
172
 
173
173
  Everyone else should append to:
174
- - `shared-context/agent-outputs/` (append-only)
174
+ - `../shared-context/agent-outputs/` (append-only)
175
175
  - `shared-context/feedback/`
176
176
 
177
177
  Your job is to periodically distill those inputs into the curated files.
@@ -186,8 +186,8 @@ templates:
186
186
  - `work/in-progress/` — tickets currently being executed
187
187
  - `work/testing/` — tickets awaiting QA verification
188
188
  - `work/done/` — completed tickets + completion notes
189
- - `notes/plan.md` — current plan / priorities (curated)
190
- - `notes/status.md` — current status snapshot
189
+ - `../notes/plan.md` — current plan / priorities (curated)
190
+ - `../notes/status.md` — current status snapshot
191
191
  - `shared-context/` — shared context + append-only outputs
192
192
 
193
193
  ### Ticket numbering (critical)
@@ -204,8 +204,8 @@ templates:
204
204
 
205
205
  ### Your responsibilities
206
206
  - For every new request in `inbox/`, create a normalized ticket in `work/backlog/`.
207
- - Curate `notes/plan.md` and `shared-context/priorities.md`.
208
- - Keep `notes/status.md` updated.
207
+ - Curate `../notes/plan.md` and `../shared-context/priorities.md`.
208
+ - Keep `../notes/status.md` updated.
209
209
  - When work is ready for QA, move the ticket to `work/testing/` and assign it to the tester.
210
210
  - Only after QA verification, move the ticket to `work/done/` (or use `openclaw recipes complete`).
211
211
  - When a completion appears in `work/done/`, write a short summary into `outbox/`.
@@ -231,8 +231,8 @@ templates:
231
231
  ## Guardrails (read → act → write)
232
232
  Before you act:
233
233
  1) Read:
234
- - `notes/plan.md`
235
- - `notes/status.md`
234
+ - `../notes/plan.md`
235
+ - `../notes/status.md`
236
236
  - relevant ticket(s) in `work/in-progress/`
237
237
  - any relevant shared context under `shared-context/`
238
238
 
@@ -266,8 +266,8 @@ templates:
266
266
  ## Guardrails (read → act → write)
267
267
  Before you act:
268
268
  1) Read:
269
- - `notes/plan.md`
270
- - `notes/status.md`
269
+ - `../notes/plan.md`
270
+ - `../notes/status.md`
271
271
  - relevant ticket(s) in `work/in-progress/`
272
272
  - any relevant shared context under `shared-context/`
273
273
 
@@ -301,8 +301,8 @@ templates:
301
301
  ## Guardrails (read → act → write)
302
302
  Before you act:
303
303
  1) Read:
304
- - `notes/plan.md`
305
- - `notes/status.md`
304
+ - `../notes/plan.md`
305
+ - `../notes/status.md`
306
306
  - relevant ticket(s) in `work/in-progress/`
307
307
  - any relevant shared context under `shared-context/`
308
308
 
@@ -336,8 +336,8 @@ templates:
336
336
  ## Guardrails (read → act → write)
337
337
  Before you act:
338
338
  1) Read:
339
- - `notes/plan.md`
340
- - `notes/status.md`
339
+ - `../notes/plan.md`
340
+ - `../notes/status.md`
341
341
  - relevant ticket(s) in `work/in-progress/`
342
342
  - any relevant shared context under `shared-context/`
343
343
 
@@ -371,8 +371,8 @@ templates:
371
371
  ## Guardrails (read → act → write)
372
372
  Before you act:
373
373
  1) Read:
374
- - `notes/plan.md`
375
- - `notes/status.md`
374
+ - `../notes/plan.md`
375
+ - `../notes/status.md`
376
376
  - relevant ticket(s) in `work/in-progress/`
377
377
  - any relevant shared context under `shared-context/`
378
378
 
@@ -406,8 +406,8 @@ templates:
406
406
  ## Guardrails (read → act → write)
407
407
  Before you act:
408
408
  1) Read:
409
- - `notes/plan.md`
410
- - `notes/status.md`
409
+ - `../notes/plan.md`
410
+ - `../notes/status.md`
411
411
  - relevant ticket(s) in `work/in-progress/`
412
412
  - any relevant shared context under `shared-context/`
413
413
 
@@ -441,8 +441,8 @@ templates:
441
441
  ## Guardrails (read → act → write)
442
442
  Before you act:
443
443
  1) Read:
444
- - `notes/plan.md`
445
- - `notes/status.md`
444
+ - `../notes/plan.md`
445
+ - `../notes/status.md`
446
446
  - relevant ticket(s) in `work/in-progress/`
447
447
  - any relevant shared context under `shared-context/`
448
448
 
@@ -476,8 +476,8 @@ templates:
476
476
  ## Guardrails (read → act → write)
477
477
  Before you act:
478
478
  1) Read:
479
- - `notes/plan.md`
480
- - `notes/status.md`
479
+ - `../notes/plan.md`
480
+ - `../notes/status.md`
481
481
  - relevant ticket(s) in `work/in-progress/`
482
482
  - any relevant shared context under `shared-context/`
483
483
 
@@ -511,8 +511,8 @@ templates:
511
511
  ## Guardrails (read → act → write)
512
512
  Before you act:
513
513
  1) Read:
514
- - `notes/plan.md`
515
- - `notes/status.md`
514
+ - `../notes/plan.md`
515
+ - `../notes/status.md`
516
516
  - relevant ticket(s) in `work/in-progress/`
517
517
  - any relevant shared context under `shared-context/`
518
518
 
@@ -546,8 +546,8 @@ templates:
546
546
  ## Guardrails (read → act → write)
547
547
  Before you act:
548
548
  1) Read:
549
- - `notes/plan.md`
550
- - `notes/status.md`
549
+ - `../notes/plan.md`
550
+ - `../notes/status.md`
551
551
  - relevant ticket(s) in `work/in-progress/`
552
552
  - any relevant shared context under `shared-context/`
553
553
 
@@ -581,8 +581,8 @@ templates:
581
581
  ## Guardrails (read → act → write)
582
582
  Before you act:
583
583
  1) Read:
584
- - `notes/plan.md`
585
- - `notes/status.md`
584
+ - `../notes/plan.md`
585
+ - `../notes/status.md`
586
586
  - relevant ticket(s) in `work/in-progress/`
587
587
  - any relevant shared context under `shared-context/`
588
588
 
@@ -616,8 +616,8 @@ templates:
616
616
  ## Guardrails (read → act → write)
617
617
  Before you act:
618
618
  1) Read:
619
- - `notes/plan.md`
620
- - `notes/status.md`
619
+ - `../notes/plan.md`
620
+ - `../notes/status.md`
621
621
  - relevant ticket(s) in `work/in-progress/`
622
622
  - any relevant shared context under `shared-context/`
623
623
 
package/recipes/default/workflow-runner-addon.md CHANGED
@@ -9,9 +9,9 @@ name: Workflow runner (team add-on)
9
9
  cronJobs:
10
10
  - id: workflow-runner-loop
11
11
  name: "{{teamId}} • workflow runner loop (runs queue)"
12
- schedule: "*/15 * * * * *"
12
+ schedule: "*/5 * * * *"
13
13
  agentId: "{{teamId}}-workflow-runner"
14
- enabledByDefault: true
14
+ enabledByDefault: false
15
15
  message: |
16
16
  [cron] Workflow runner loop (runs queue)
17
17
 
@@ -42,7 +42,7 @@ templates:
42
42
  ## How to operate
43
43
  - Prefer the CLI runner tick:
44
44
  `openclaw recipes workflows runner-tick --team-id {{teamId}} --concurrency 2 --lease-seconds 45`
45
- - If anything looks wrong (schema mismatch, repeated failures), STOP and write a note to notes/status.md.
45
+ - If anything looks wrong (schema mismatch, repeated failures), STOP and write a note to `../notes/status.md`.
46
46
 
47
47
  tools: |
48
48
  # TOOLS.md
package/recipes/default/writing-team.md CHANGED
@@ -57,16 +57,16 @@ templates:
57
57
 
58
58
  ## Where to write things
59
59
  - Ticket = source of truth for a unit of work.
60
- - `notes/plan.md` + `shared-context/priorities.md` are **lead-curated**.
61
- - `notes/status.md` is **append-only** and updated after each work session (3–5 bullets).
62
- - `shared-context/agent-outputs/` is **append-only** logs/output.
60
+ - `../notes/plan.md` + `../shared-context/priorities.md` are **lead-curated**.
61
+ - `../notes/status.md` is **append-only** and updated after each work session (3–5 bullets).
62
+ - `../shared-context/agent-outputs/` is **append-only** logs/output.
63
63
 
64
64
  ## End-of-session checklist (everyone)
65
65
  After meaningful work:
66
66
  1) Update the ticket with what changed + how to verify + rollback.
67
67
  2) Add a dated note in the ticket `## Comments`.
68
- 3) Append 3–5 bullets to `notes/status.md`.
69
- 4) Append logs/output to `shared-context/agent-outputs/`.
68
+ 3) Append 3–5 bullets to `../notes/status.md`.
69
+ 4) Append logs/output to `../shared-context/agent-outputs/`.
70
70
 
71
71
  sharedContext.plan: |
72
72
  # Plan (lead-curated)
@@ -99,16 +99,16 @@ templates:
99
99
  - `roles/<role>/memory/YYYY-MM-DD.md` (daily log)
100
100
 
101
101
  ## Plan vs status (team coordination)
102
- - `notes/plan.md` + `shared-context/priorities.md` are lead-curated
103
- - `notes/status.md` is append-only roll-up (everyone appends)
102
+ - `../notes/plan.md` + `../shared-context/priorities.md` are lead-curated
103
+ - `../notes/status.md` is append-only roll-up (everyone appends)
104
104
 
105
105
  ## Outputs / artifacts
106
106
  - `roles/<role>/agent-outputs/` (append-only)
107
- - `shared-context/agent-outputs/` (optional team-level)
107
+ - `../shared-context/agent-outputs/` (team-level, read/write from role via `../`)
108
108
 
109
109
  ## Role work loop contract (safe-idle)
110
110
  - No-op unless explicit queued work exists for the role.
111
- - If work happens, write back in order: ticket → `notes/status.md` → `roles/<role>/agent-outputs/`.
111
+ - If work happens, write back in order: ticket → `../notes/status.md` → `roles/<role>/agent-outputs/`.
112
112
 
113
113
  sharedContext.priorities: |
114
114
  # Priorities (lead-curated)
@@ -141,24 +141,24 @@ templates:
141
141
 
142
142
  Before you act:
143
143
  1) Read:
144
- - `notes/plan.md`
145
- - `notes/status.md`
146
- - `shared-context/priorities.md`
144
+ - `../notes/plan.md`
145
+ - `../notes/status.md`
146
+ - `../shared-context/priorities.md`
147
147
  - the relevant ticket(s)
148
148
 
149
149
  After you act:
150
150
  1) Write back:
151
151
  - Update tickets with decisions/assignments.
152
- - Keep `notes/status.md` current (3–5 bullets per active ticket).
152
+ - Keep `../notes/status.md` current (3–5 bullets per active ticket).
153
153
 
154
154
  ## Curator model
155
155
 
156
156
  You are the curator of:
157
- - `notes/plan.md`
158
- - `shared-context/priorities.md`
157
+ - `../notes/plan.md`
158
+ - `../shared-context/priorities.md`
159
159
 
160
160
  Everyone else should append to:
161
- - `shared-context/agent-outputs/` (append-only)
161
+ - `../shared-context/agent-outputs/` (append-only)
162
162
  - `shared-context/feedback/`
163
163
 
164
164
  Your job is to periodically distill those inputs into the curated files.
@@ -173,8 +173,8 @@ templates:
173
173
  - `work/in-progress/` — tickets currently being executed
174
174
  - `work/testing/` — tickets awaiting QA verification
175
175
  - `work/done/` — completed tickets + completion notes
176
- - `notes/plan.md` — current plan / priorities (curated)
177
- - `notes/status.md` — current status snapshot
176
+ - `../notes/plan.md` — current plan / priorities (curated)
177
+ - `../notes/status.md` — current status snapshot
178
178
  - `shared-context/` — shared context + append-only outputs
179
179
 
180
180
  ### Ticket numbering (critical)
@@ -191,8 +191,8 @@ templates:
191
191
 
192
192
  ### Your responsibilities
193
193
  - For every new request in `inbox/`, create a normalized ticket in `work/backlog/`.
194
- - Curate `notes/plan.md` and `shared-context/priorities.md`.
195
- - Keep `notes/status.md` updated.
194
+ - Curate `../notes/plan.md` and `../shared-context/priorities.md`.
195
+ - Keep `../notes/status.md` updated.
196
196
  - When work is ready for QA, move the ticket to `work/testing/` and assign it to the tester.
197
197
  - Only after QA verification, move the ticket to `work/done/` (or use `openclaw recipes complete`).
198
198
  - When a completion appears in `work/done/`, write a short summary into `outbox/`.
@@ -213,8 +213,8 @@ templates:
213
213
  ## Guardrails (read → act → write)
214
214
  Before you act:
215
215
  1) Read:
216
- - `notes/plan.md`
217
- - `notes/status.md`
216
+ - `../notes/plan.md`
217
+ - `../notes/status.md`
218
218
  - relevant ticket(s) in `work/in-progress/`
219
219
  - any relevant shared context under `shared-context/`
220
220
 
@@ -243,8 +243,8 @@ templates:
243
243
  ## Guardrails (read → act → write)
244
244
  Before you act:
245
245
  1) Read:
246
- - `notes/plan.md`
247
- - `notes/status.md`
246
+ - `../notes/plan.md`
247
+ - `../notes/status.md`
248
248
  - relevant ticket(s) in `work/in-progress/`
249
249
  - any relevant shared context under `shared-context/`
250
250
 
@@ -273,8 +273,8 @@ templates:
273
273
  ## Guardrails (read → act → write)
274
274
  Before you act:
275
275
  1) Read:
276
- - `notes/plan.md`
277
- - `notes/status.md`
276
+ - `../notes/plan.md`
277
+ - `../notes/status.md`
278
278
  - relevant ticket(s) in `work/in-progress/`
279
279
  - any relevant shared context under `shared-context/`
280
280