@jiggai/recipes 0.4.23 → 0.4.25

package/openclaw.plugin.json

@@ -2,7 +2,7 @@
   "id": "recipes",
   "name": "Recipes",
   "description": "Markdown recipes that scaffold agents and teams (workspace-local).",
-  "version": "0.4.23",
+  "version": "0.4.25",
   "configSchema": {
     "type": "object",
     "additionalProperties": false,

package/package.json

@@ -1,13 +1,16 @@
 {
   "name": "@jiggai/recipes",
-  "version": "0.4.23",
+  "version": "0.4.25",
   "description": "ClawRecipes plugin for OpenClaw (markdown recipes -> scaffold agents/teams)",
   "main": "index.ts",
   "type": "commonjs",
   "openclaw": {
     "extensions": [
       "./index.ts"
-    ]
+    ],
+    "compat": {
+      "pluginApi": "2026.3"
+    }
   },
   "publishConfig": {
     "access": "public"
@@ -34,7 +37,7 @@
     "lint:fix": "eslint src/ index.ts --fix",
     "smell-check": "node scripts/smell-check.mjs",
     "jscpd": "jscpd src/ index.ts --min-lines 8 --min-tokens 50",
-    "prepare": "husky",
+    "prepare": "husky || true",
     "check:plugin-version": "node scripts/check-openclaw-plugin-version.mjs",
     "prepack": "npm run -s sync:plugin-version && npm run -s check:plugin-version",
     "prepublishOnly": "npm run -s sync:plugin-version && npm run -s check:plugin-version",

package/recipes/default/business-team.md

@@ -9,13 +9,58 @@ cronJobs:
     name: "Lead triage loop"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
-    message: "Automated lead triage loop (Business Team): triage inbox/tickets, assign work, and update notes/status.md."
+    agentId: "{{teamId}}-lead"
+    timeoutSeconds: 1800
+    message: "Lead triage loop (Business Team): triage inbox/tickets, assign work, and update notes/status.md. Complete all pending triage before finishing."
+    enabledByDefault: false
+
+  - id: ops-work-loop
+    name: "Operations work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-ops"
+    timeoutSeconds: 1800
+    message: "Work loop: check for operations-assigned work. If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/ops/agent-outputs/."
+    enabledByDefault: false
+  - id: sales-work-loop
+    name: "Sales work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-sales"
+    timeoutSeconds: 1800
+    message: "Work loop: check for sales-assigned work. If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/sales/agent-outputs/."
+    enabledByDefault: false
+  - id: marketing-work-loop
+    name: "Marketing work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-marketing"
+    timeoutSeconds: 1800
+    message: "Work loop: check for marketing-assigned work. If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/marketing/agent-outputs/."
+    enabledByDefault: false
+  - id: finance-work-loop
+    name: "Finance work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-finance"
+    timeoutSeconds: 1800
+    message: "Work loop: check for finance-assigned work. If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/finance/agent-outputs/."
+    enabledByDefault: false
+  - id: analyst-work-loop
+    name: "Analyst work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-analyst"
+    timeoutSeconds: 1800
+    message: "Work loop: check for analytics-assigned work. If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/analyst/agent-outputs/."
     enabledByDefault: false
   - id: execution-loop
     name: "Execution loop"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
-    message: "Automated execution loop (Business Team): make progress on in-progress tickets and update notes/status.md."
+    agentId: "{{teamId}}-lead"
+    timeoutSeconds: 1800
+    message: "Execution loop (Business Team): complete in-progress tickets and update notes/status.md. Finish each ticket fully before moving on."
     enabledByDefault: false
 requiredSkills: []
 team:
@@ -117,9 +162,10 @@ templates:
     - `roles/<role>/agent-outputs/` (append-only)
     - `../shared-context/agent-outputs/` (team-level, read/write from role via `../`)
 
-    ## Role work loop contract (safe-idle)
+    ## Role work loop contract
     - No-op unless explicit queued work exists for the role.
-    - If work happens, write back in order: ticket → `../notes/status.md` → `roles/<role>/agent-outputs/`.
+    - If work exists, complete it fully. If too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains.
+    - Write back in order: ticket → `../notes/status.md` → `roles/<role>/agent-outputs/`.
 
   sharedContext.priorities: |
     # Priorities (lead-curated)

package/recipes/default/customer-support-team.md

@@ -9,13 +9,42 @@ cronJobs:
     name: "Lead triage loop"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
-    message: "Automated lead triage loop: triage inbox/tickets, assign work, and update notes/status.md."
+    agentId: "{{teamId}}-lead"
+    timeoutSeconds: 1800
+    message: "Lead triage loop (Customer Support Team): triage inbox/tickets, assign work, and update notes/status.md. Complete all pending triage before finishing."
+    enabledByDefault: false
+
+  - id: triage-work-loop
+    name: "Triage work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-triage"
+    timeoutSeconds: 1800
+    message: "Work loop: check for triage-assigned tickets (categorize, route, escalate). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/triage/agent-outputs/."
+    enabledByDefault: false
+  - id: resolver-work-loop
+    name: "Resolver work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-resolver"
+    timeoutSeconds: 1800
+    message: "Work loop: check for resolver-assigned tickets (investigate, resolve, follow up). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/resolver/agent-outputs/."
+    enabledByDefault: false
+  - id: kb-writer-work-loop
+    name: "KB Writer work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-kb-writer"
+    timeoutSeconds: 1800
+    message: "Work loop: check for knowledge-base work (document solutions, update FAQs, maintain docs). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/kb-writer/agent-outputs/."
     enabledByDefault: false
   - id: execution-loop
     name: "Execution loop"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
-    message: "Automated execution loop: make progress on in-progress tickets, keep changes small/safe, and update notes/status.md."
+    agentId: "{{teamId}}-lead"
+    timeoutSeconds: 1800
+    message: "Execution loop (Customer Support Team): complete in-progress tickets and update notes/status.md. Finish each ticket fully before moving on."
     enabledByDefault: false
   # pr-watcher omitted (enable only when a real PR integration exists)
 requiredSkills: []
@@ -106,9 +135,10 @@ templates:
     - `roles/<role>/agent-outputs/` (append-only)
     - `../shared-context/agent-outputs/` (team-level, read/write from role via `../`)
 
-    ## Role work loop contract (safe-idle)
+    ## Role work loop contract
     - No-op unless explicit queued work exists for the role.
-    - If work happens, write back in order: ticket → `../notes/status.md` → `roles/<role>/agent-outputs/`.
+    - If work exists, complete it fully. If too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains.
+    - Write back in order: ticket → `../notes/status.md` → `roles/<role>/agent-outputs/`.
 
   sharedContext.priorities: |
     # Priorities (lead-curated)

package/recipes/default/development-team.md

@@ -10,8 +10,9 @@ cronJobs:
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
     agentId: "{{teamId}}-lead"
+    timeoutSeconds: 1800
     message: |
-      Automated lead triage loop: triage inbox/tickets, assign work, and update notes/status.md.
+      Lead triage loop: triage inbox/tickets, assign work, and update notes/status.md. Complete all pending triage before finishing.
 
       QA-gated PR rule:
       - Dev/DevOps must NOT open PRs.
@@ -35,8 +36,9 @@ cronJobs:
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
     agentId: "{{teamId}}-dev"
+    timeoutSeconds: 1800
     message: |
-      Safe-idle loop: work dev-assigned tickets.
+      Work loop: check for dev-assigned tickets. If you have one, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece (not a fragment) and update the ticket with what's done and what remains. Always leave work in a clean, consistent state.
 
       Constraints:
       - Do NOT open PRs. Dev hands off to QA by moving ticket to work/testing and setting Owner=test.
@@ -49,7 +51,8 @@ cronJobs:
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
     agentId: "{{teamId}}-devops"
-    message: "Safe-idle loop: check for devops-assigned tickets/runs, make small progress, and write outputs under roles/devops/agent-outputs/."
+    timeoutSeconds: 1800
+    message: "Work loop: check for devops-assigned tickets/runs. If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/devops/agent-outputs/."
     enabledByDefault: true
 
   - id: test-work-loop
@@ -57,8 +60,9 @@ cronJobs:
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
     agentId: "{{teamId}}-test"
+    timeoutSeconds: 1800
     message: |
-      Safe-idle loop: drain work/testing tickets assigned to test.
+      Work loop: drain work/testing tickets assigned to test. Complete each ticket's QA fully before moving on.
 
       Workflow:
       - On PASS: keep ticket in work/testing but set Owner=lead (ready-for-pr) and add a `QA: PASS` comment + evidence.
@@ -75,8 +79,9 @@ cronJobs:
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
     agentId: "{{teamId}}-lead"
+    timeoutSeconds: 1800
     message: |
-      Automated execution loop: make progress on in-progress tickets, keep changes small/safe, and update notes/status.md.
+      Execution loop: complete in-progress tickets and update notes/status.md. Finish each ticket fully before moving on. If a task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains.
 
       CWD guardrail (team root): run:
         cd "$(bash ../../scripts/team-root.sh 2>/dev/null || bash ./scripts/team-root.sh)"
@@ -85,7 +90,7 @@ cronJobs:
       Guardrail: run ./scripts/ticket-hygiene-dev.sh each loop; if it fails, fix lane/status/owner mismatches before proceeding (assignment stubs are deprecated).
 
       LEAD-OWNED TICKETS RULE (must follow)
-      - Do NOT automatically move a ticket just because Owner=lead “expects backlog”.
+      - Do NOT automatically move a ticket just because Owner=lead "expects backlog".
       - If you encounter a lead-owned ticket in work/in-progress or work/testing that seems misassigned:
         - LEAVE IT IN PLACE.
         - Add a dated comment to the ticket explaining what you observed and what should change.
@@ -158,7 +163,7 @@ cronJobs:
 
   - id: backup-devteam-work
     name: "Backup dev-team work (every 3h, off-hours avoided)"
-    # Every 3h during 07:00–22:00 America/New_York (avoids 02:00–07:00 blackout)
+    # Every 3h during 07:00-22:00 America/New_York (avoids 02:00-07:00 blackout)
     schedule: "0 7,10,13,16,19,22 * * *"
     timezone: "America/New_York"
     agentId: "{{teamId}}-lead"
@@ -220,29 +225,29 @@ templates:
   sharedContext.memoryPolicy: |
     # Team Memory Policy (File-first)
 
-    Quick link: see `shared-context/MEMORY_PLAN.md` for the canonical “what goes where” map.
+    Quick link: see `shared-context/MEMORY_PLAN.md` for the canonical "what goes where" map.
 
     This team is run **file-first**. Chat is not the system of record.
 
-    ## Where memory lives (and what it’s for)
+    ## Where memory lives (and what it's for)
 
     ### 1) Team knowledge memory (Kitchen UI)
     - `shared-context/memory/team.jsonl` (append-only)
     - `shared-context/memory/pinned.jsonl` (append-only)
 
-    Kitchen’s Team Editor → Memory tab reads/writes these JSONL streams.
+    Kitchen's Team Editor → Memory tab reads/writes these JSONL streams.
 
     ### 2) Per-role continuity memory (agents)
     Each role keeps its own continuity memory:
     - `roles/<role>/memory/YYYY-MM-DD.md` (daily log)
     - `roles/<role>/MEMORY.md` (curated long-term memory)
 
-    These files are what the role agent uses to “remember” decisions and context across sessions.
+    These files are what the role agent uses to "remember" decisions and context across sessions.
 
     ## Where to write things
     - Ticket = source of truth for a unit of work.
     - `../notes/plan.md` + `../shared-context/priorities.md` are **lead-curated**.
-    - `../notes/status.md` is **append-only** and updated after each work session (3–5 bullets).
+    - `../notes/status.md` is **append-only** and updated after each work session (3-5 bullets).
 
     ## Outputs / artifacts
     - Role-level raw output (append-only): `roles/<role>/agent-outputs/`
@@ -250,10 +255,11 @@ templates:
 
     Guardrail: do **not** create or rely on `roles/<role>/shared-context/**`.
 
-    ## Role work loop contract (safe-idle)
-    When a role’s cron/heartbeat runs:
+    ## Role work loop contract
+    When a role's cron/heartbeat runs:
     - **No-op unless explicit queued work exists** for that role (ticket assigned/owned by role, or workflow run nodes assigned to the role agentId).
-    - If work happens, write back in this order:
+    - If work exists, **complete the ticket fully**. If the task is too large for one session, complete a meaningful self-contained piece (not a fragment) and update the ticket with what's done and what remains. Always leave work in a clean, consistent state.
+    - Write back in this order:
       1) Update the relevant ticket(s) (source of truth).
       2) Append 1–3 bullets to `../notes/status.md` (team roll-up).
       3) Write raw logs/artifacts under `roles/<role>/agent-outputs/` and reference them from the ticket.
@@ -266,11 +272,11 @@ templates:
     After meaningful work:
     1) Update the ticket with what changed + how to verify + rollback.
     2) Add a dated note in the ticket `## Comments`.
-    3) Append 3–5 bullets to `../notes/status.md`.
+    3) Append 3-5 bullets to `../notes/status.md`.
     4) Append logs/output to `roles/<role>/agent-outputs/`.
 
   tickets: |
-    # Tickets — {{teamId}}
+    # Tickets - {{teamId}}
 
     ## Workflow stages
     - backlog → in-progress → testing → done
@@ -280,7 +286,7 @@ templates:
     - test: verify + record PASS/FAIL
     - lead: creates PR **only after QA PASS**
 
-    ## “Ready for PR” (no extra lane)
+    ## "Ready for PR" (no extra lane)
     This team does **not** add a separate lane.
 
     Instead, a ticket is considered **ready for PR** when:
@@ -295,7 +301,7 @@ templates:
     - Move ticket to `work/testing/`
     - Set `Owner: test`
     - Ensure the ticket contains:
-      - verification steps (“How to test”)
+      - verification steps ("How to test")
       - links to branch/commit under `## PR-ready`
 
     ### Test → Lead (QA PASS)
@@ -324,7 +330,7 @@ templates:
 
 
   sharedContext.qaAccess: |
-    # QA Access — {{teamId}}
+    # QA Access - {{teamId}}
 
     This file exists to prevent QA tickets being bounced due to missing environment access.
 
@@ -381,9 +387,10 @@ templates:
     - `roles/<role>/agent-outputs/` (append-only)
     - `../shared-context/agent-outputs/` (team-level, read/write from role via `../`)
 
-    ## Role work loop contract (safe-idle)
+    ## Role work loop contract
     - No-op unless explicit queued work exists for the role.
-    - If work happens, write back in order: ticket → `../notes/status.md` → `roles/<role>/agent-outputs/`.
+    - If work exists, complete it fully. If too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains.
+    - Write back in order: ticket → `../notes/status.md` → `roles/<role>/agent-outputs/`.
 
   sharedContext.priorities: |
     # Priorities (lead-curated)
@@ -1013,7 +1020,7 @@ templates:
     After you act:
     1) Write back:
        - Update tickets with decisions/assignments.
-       - Keep `../notes/status.md` current (3–5 bullets per active ticket).
+       - Keep `../notes/status.md` current (3-5 bullets per active ticket).
 
     ## Curator model
 
@@ -1032,14 +1039,14 @@ templates:
     Source of truth is the shared team workspace.
 
     Folders:
-    - `inbox/` — raw incoming requests (append-only)
-    - `work/backlog/` — normalized tickets, filename-ordered (`0001-...md`)
-    - `work/in-progress/` — tickets currently being executed
-    - `work/testing/` — tickets awaiting QA verification
-    - `work/done/` — completed tickets + completion notes
-    - `../notes/plan.md` — current plan / priorities (curated)
-    - `../notes/status.md` — current status snapshot
-    - `shared-context/` — shared context + append-only outputs
+    - `inbox/` - raw incoming requests (append-only)
+    - `work/backlog/` - normalized tickets, filename-ordered (`0001-...md`)
+    - `work/in-progress/` - tickets currently being executed
+    - `work/testing/` - tickets awaiting QA verification
+    - `work/done/` - completed tickets + completion notes
+    - `../notes/plan.md` - current plan / priorities (curated)
+    - `../notes/status.md` - current status snapshot
+    - `shared-context/` - shared context + append-only outputs
 
     ### Ticket numbering (critical)
     - Backlog tickets MUST be named `0001-...md`, `0002-...md`, etc.
@@ -1092,7 +1099,7 @@ templates:
        - `../notes/plan.md`
        - `../notes/status.md`
        - `../shared-context/priorities.md`
-       - the current ticket you’re working on
+       - the current ticket you're working on
 
     Optional (team knowledge memory, Kitchen UI):
        - `shared-context/memory/pinned.jsonl`
@@ -1104,8 +1111,8 @@ templates:
 
     After you finish a work session (even if not done):
     1) Write back:
-       - Update the ticket with what you did and what’s next.
-       - Add **3–5 bullets** to `../notes/status.md` (what changed / what’s blocked).
+       - Update the ticket with what you did and what's next.
+       - Add **3-5 bullets** to `../notes/status.md` (what changed / what's blocked).
        - Append detailed output to `../shared-context/agent-outputs/` (append-only).
 
     Curator model:
@@ -1125,7 +1132,7 @@ templates:
     4) Do the work.
 
     5) Handoff to QA (required):
-       - Ensure the ticket has verification steps (“How to test”).
+       - Ensure the ticket has verification steps ("How to test").
        - Add a `## PR-ready` section with repo + branch + commit SHA (if known).
        - Move the ticket to `work/testing/`.
        - Set `Owner: test`.
@@ -1159,7 +1166,7 @@ templates:
        - `../notes/plan.md`
        - `../notes/status.md`
        - `../shared-context/priorities.md`
-       - the current ticket you’re working on
+       - the current ticket you're working on
 
     Optional (team knowledge memory, Kitchen UI):
        - `shared-context/memory/pinned.jsonl`
@@ -1168,7 +1175,7 @@ templates:
     After you finish a work session:
     1) Write back:
        - Update the ticket with what you did + verification steps.
-       - Add **3–5 bullets** to `../notes/status.md`.
+       - Add **3-5 bullets** to `../notes/status.md`.
        - Append detailed output/logs to `../shared-context/agent-outputs/` (append-only).
 
     Curator model:
@@ -1300,7 +1307,7 @@ templates:
 
     ## Core workflow (QA gated)
     - You verify work before any PR is created.
-    - If the ticket passes: keep it in `work/testing/` but set `Owner: lead` (this is the “ready for PR” state).
+    - If the ticket passes: keep it in `work/testing/` but set `Owner: lead` (this is the "ready for PR" state).
     - If it fails: move it back to `work/in-progress/` and set `Owner: dev`.
 
     ## Guardrails (read → act → write)
@@ -1323,7 +1330,7 @@ templates:
     After each verification pass:
     1) Write back:
        - Add a short verification note to the ticket (pass/fail + evidence).
-       - Add **3–5 bullets** to `../notes/status.md` (what’s verified / what’s blocked).
+       - Add **3-5 bullets** to `../notes/status.md` (what's verified / what's blocked).
        - Append detailed findings to `../shared-context/feedback/` or `../shared-context/agent-outputs/`.
 
     Curator model:
@@ -1342,7 +1349,7 @@ templates:
     3) If it passes:
        - Add a dated ticket comment: `QA: PASS` + evidence (links, logs, screenshots as applicable).
        - Keep the ticket in `work/testing/`.
-       - Set `Owner: lead` (this is the “ready for PR” state).
+       - Set `Owner: lead` (this is the "ready for PR" state).
 
     4) If it fails:
        - Add a dated ticket comment: `QA: FAIL` + repro + what to fix.

package/recipes/default/marketing-team.md

@@ -10,86 +10,98 @@ cronJobs:
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
     agentId: "{{teamId}}-lead"
-    message: "Automated lead triage loop (Marketing Team): triage inbox/tickets, assign work, and update notes/status.md."
+    timeoutSeconds: 1800
+    message: "Lead triage loop (Marketing Team): triage inbox/tickets, assign work, and update notes/status.md. Complete all pending triage before finishing."
     enabledByDefault: false
 
-  # Safe-idle role loops (enabled by default): roles do not "wake up" unless they have their own heartbeat schedule or cron.
+  # Safe-idle role loops: roles do not "wake up" unless they have their own cron.
   - id: seo-work-loop
     name: "SEO work loop (safe-idle)"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
     agentId: "{{teamId}}-seo"
-    message: "Safe-idle loop: check for SEO-assigned work (tickets/workflows), make small progress, and write outputs under roles/seo/agent-outputs/."
+    timeoutSeconds: 1800
+    message: "Work loop: check for SEO-assigned work (tickets/workflows). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/seo/agent-outputs/."
     enabledByDefault: false
   - id: copywriter-work-loop
     name: "Copywriter work loop (safe-idle)"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
     agentId: "{{teamId}}-copywriter"
-    message: "Safe-idle loop: check for copywriting-assigned work, make progress, and write outputs under roles/copywriter/agent-outputs/."
+    timeoutSeconds: 1800
+    message: "Work loop: check for copywriting-assigned work. If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/copywriter/agent-outputs/."
     enabledByDefault: false
   - id: ads-work-loop
     name: "Ads work loop (safe-idle)"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
     agentId: "{{teamId}}-ads"
-    message: "Safe-idle loop: check for ads-assigned work, make progress, and write outputs under roles/ads/agent-outputs/."
+    timeoutSeconds: 1800
+    message: "Work loop: check for ads-assigned work. If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/ads/agent-outputs/."
     enabledByDefault: false
   - id: social-work-loop
     name: "Social work loop (safe-idle)"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
     agentId: "{{teamId}}-social"
-    message: "Safe-idle loop: check for social/community-assigned work, make progress, and write outputs under roles/social/agent-outputs/."
+    timeoutSeconds: 1800
+    message: "Work loop: check for social/community-assigned work. If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/social/agent-outputs/."
     enabledByDefault: false
   - id: designer-work-loop
     name: "Designer work loop (safe-idle)"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
     agentId: "{{teamId}}-designer"
-    message: "Safe-idle loop: check for creative/design-assigned work, make progress, and write outputs under roles/designer/agent-outputs/."
+    timeoutSeconds: 1800
+    message: "Work loop: check for creative/design-assigned work. If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/designer/agent-outputs/."
     enabledByDefault: false
   - id: analyst-work-loop
     name: "Analyst work loop (safe-idle)"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
     agentId: "{{teamId}}-analyst"
-    message: "Safe-idle loop: check for analytics-assigned work, make progress, and write outputs under roles/analyst/agent-outputs/."
+    timeoutSeconds: 1800
+    message: "Work loop: check for analytics-assigned work. If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/analyst/agent-outputs/."
     enabledByDefault: false
   - id: video-work-loop
     name: "Video work loop (safe-idle)"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
     agentId: "{{teamId}}-video"
-    message: "Safe-idle loop: check for video-assigned work, make progress, and write outputs under roles/video/agent-outputs/."
+    timeoutSeconds: 1800
+    message: "Work loop: check for video-assigned work. If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/video/agent-outputs/."
     enabledByDefault: false
   - id: compliance-work-loop
     name: "Compliance work loop (safe-idle)"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
     agentId: "{{teamId}}-compliance"
-    message: "Safe-idle loop: check for compliance/brand-review work, make progress, and write outputs under roles/compliance/agent-outputs/."
+    timeoutSeconds: 1800
+    message: "Work loop: check for compliance/brand-review work. If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/compliance/agent-outputs/."
     enabledByDefault: false
   - id: offer-work-loop
     name: "Offer work loop (safe-idle)"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
     agentId: "{{teamId}}-offer"
-    message: "Safe-idle loop: check for offer/positioning work, make progress, and write outputs under roles/offer/agent-outputs/."
+    timeoutSeconds: 1800
+    message: "Work loop: check for offer/positioning work. If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/offer/agent-outputs/."
     enabledByDefault: false
   - id: funnel-work-loop
     name: "Funnel work loop (safe-idle)"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
     agentId: "{{teamId}}-funnel"
-    message: "Safe-idle loop: check for funnel/landing-page work, make progress, and write outputs under roles/funnel/agent-outputs/."
+    timeoutSeconds: 1800
+    message: "Work loop: check for funnel/landing-page work. If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/funnel/agent-outputs/."
     enabledByDefault: false
   - id: lifecycle-work-loop
     name: "Lifecycle work loop (safe-idle)"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
     agentId: "{{teamId}}-lifecycle"
-    message: "Safe-idle loop: check for lifecycle/email work, make progress, and write outputs under roles/lifecycle/agent-outputs/."
+    timeoutSeconds: 1800
+    message: "Work loop: check for lifecycle/email work. If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/lifecycle/agent-outputs/."
     enabledByDefault: false
 
   # NOTE: Workflow worker crons are NOT defined here.
@@ -104,7 +116,8 @@ cronJobs:
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
     agentId: "{{teamId}}-lead"
-    message: "Automated execution loop (Marketing Team): make progress on in-progress tickets and update notes/status.md."
+    timeoutSeconds: 1800
+    message: "Execution loop (Marketing Team): complete in-progress tickets and update notes/status.md. Finish each ticket fully before moving on."
     enabledByDefault: false
 requiredSkills: []
 team:

package/recipes/default/product-team.md

@@ -9,13 +9,50 @@ cronJobs:
     name: "Lead triage loop"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
-    message: "Automated lead triage loop: triage inbox/tickets, assign work, and update notes/status.md."
+    agentId: "{{teamId}}-lead"
+    timeoutSeconds: 1800
+    message: "Lead triage loop (Product Team): triage inbox/tickets, assign work, and update notes/status.md. Complete all pending triage before finishing."
+    enabledByDefault: false
+
+  - id: pm-work-loop
+    name: "Product Manager work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-pm"
+    timeoutSeconds: 1800
+    message: "Work loop: check for product-management work (specs, user stories, requirements). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/pm/agent-outputs/."
+    enabledByDefault: false
+  - id: designer-work-loop
+    name: "Designer work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-designer"
+    timeoutSeconds: 1800
+    message: "Work loop: check for design-assigned work (mockups, prototypes, design reviews). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/designer/agent-outputs/."
+    enabledByDefault: false
+  - id: engineer-work-loop
+    name: "Engineer work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-engineer"
+    timeoutSeconds: 1800
+    message: "Work loop: check for engineering-assigned tickets. If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/engineer/agent-outputs/."
+    enabledByDefault: false
+  - id: test-work-loop
+    name: "Test/QA work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-test"
+    timeoutSeconds: 1800
+    message: "Work loop: check for testing-assigned tickets (QA, verification, bug reports). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/test/agent-outputs/."
     enabledByDefault: false
   - id: execution-loop
     name: "Execution loop"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
-    message: "Automated execution loop: make progress on in-progress tickets, keep changes small/safe, and update notes/status.md."
+    agentId: "{{teamId}}-lead"
+    timeoutSeconds: 1800
+    message: "Execution loop (Product Team): complete in-progress tickets and update notes/status.md. Finish each ticket fully before moving on."
     enabledByDefault: false
   # pr-watcher omitted (enable only when a real PR integration exists)
 requiredSkills: []
@@ -112,9 +149,10 @@ templates:
     - `roles/<role>/agent-outputs/` (append-only)
     - `../shared-context/agent-outputs/` (team-level, read/write from role via `../`)
 
-    ## Role work loop contract (safe-idle)
+    ## Role work loop contract
     - No-op unless explicit queued work exists for the role.
-    - If work happens, write back in order: ticket → `../notes/status.md` → `roles/<role>/agent-outputs/`.
+    - If work exists, complete it fully. If too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains.
+    - Write back in order: ticket → `../notes/status.md` → `roles/<role>/agent-outputs/`.
 
   sharedContext.priorities: |
     # Priorities (lead-curated)

package/recipes/default/research-team.md

@@ -9,13 +9,42 @@ cronJobs:
     name: "Lead triage loop"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
-    message: "Automated lead triage loop: triage inbox/tickets, assign work, and update notes/status.md."
+    agentId: "{{teamId}}-lead"
+    timeoutSeconds: 1800
+    message: "Lead triage loop (Research Team): triage inbox/tickets, assign work, and update notes/status.md. Complete all pending triage before finishing."
+    enabledByDefault: false
+
+  - id: researcher-work-loop
+    name: "Researcher work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-researcher"
+    timeoutSeconds: 1800
+    message: "Work loop: check for research-assigned work (investigate, gather data, analyze). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/researcher/agent-outputs/."
+    enabledByDefault: false
+  - id: fact-checker-work-loop
+    name: "Fact Checker work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-fact-checker"
+    timeoutSeconds: 1800
+    message: "Work loop: check for fact-checking work (verify claims, check sources, flag issues). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/fact-checker/agent-outputs/."
+    enabledByDefault: false
+  - id: summarizer-work-loop
+    name: "Summarizer work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-summarizer"
+    timeoutSeconds: 1800
+    message: "Work loop: check for summarization work (distill findings, create briefs, write reports). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/summarizer/agent-outputs/."
     enabledByDefault: false
   - id: execution-loop
     name: "Execution loop"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
-    message: "Automated execution loop: make progress on in-progress tickets, keep changes small/safe, and update notes/status.md."
+    agentId: "{{teamId}}-lead"
+    timeoutSeconds: 1800
+    message: "Execution loop (Research Team): complete in-progress tickets and update notes/status.md. Finish each ticket fully before moving on."
     enabledByDefault: false
   # pr-watcher omitted (enable only when a real PR integration exists)
 requiredSkills: []
@@ -106,9 +135,10 @@ templates:
     - `roles/<role>/agent-outputs/` (append-only)
     - `../shared-context/agent-outputs/` (team-level, read/write from role via `../`)
 
-    ## Role work loop contract (safe-idle)
+    ## Role work loop contract
     - No-op unless explicit queued work exists for the role.
-    - If work happens, write back in order: ticket → `../notes/status.md` → `roles/<role>/agent-outputs/`.
+    - If work exists, complete it fully. If too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains.
+    - Write back in order: ticket → `../notes/status.md` → `roles/<role>/agent-outputs/`.
 
   sharedContext.priorities: |
     # Priorities (lead-curated)

package/recipes/default/social-team.md

@@ -9,13 +9,114 @@ cronJobs:
     name: "Lead triage loop"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
-    message: "Automated lead triage loop: triage inbox/tickets, assign work, and update notes/status.md."
+    agentId: "{{teamId}}-lead"
+    timeoutSeconds: 1800
+    message: "Lead triage loop (Social Media Team): triage inbox/tickets, assign work, and update notes/status.md. Complete all pending triage before finishing."
+    enabledByDefault: false
+
+  - id: research-work-loop
+    name: "Research work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-research"
+    timeoutSeconds: 1800
+    message: "Work loop: check for research-assigned work (trends, competitor analysis, audience insights). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/research/agent-outputs/."
+    enabledByDefault: false
+  - id: listening-work-loop
+    name: "Social Listening work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-listening"
+    timeoutSeconds: 1800
+    message: "Work loop: check for social-listening work (monitor mentions, sentiment, conversations). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/listening/agent-outputs/."
+    enabledByDefault: false
+  - id: social-seo-work-loop
+    name: "Social SEO work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-social-seo"
+    timeoutSeconds: 1800
+    message: "Work loop: check for social-SEO work (hashtag research, keyword optimization, discoverability). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/social-seo/agent-outputs/."
+    enabledByDefault: false
+  - id: editorial-work-loop
+    name: "Editorial work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-editorial"
+    timeoutSeconds: 1800
+    message: "Work loop: check for editorial work (content calendar, copy review, brand voice). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/editorial/agent-outputs/."
+    enabledByDefault: false
+  - id: community-work-loop
+    name: "Community work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-community"
+    timeoutSeconds: 1800
+    message: "Work loop: check for community work (engage, moderate, build relationships). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/community/agent-outputs/."
+    enabledByDefault: false
+  - id: distributor-work-loop
+    name: "Distributor work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-distributor"
+    timeoutSeconds: 1800
+    message: "Work loop: check for distribution work (schedule posts, cross-post, syndicate content). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/distributor/agent-outputs/."
+    enabledByDefault: false
+  - id: tiktok-work-loop
+    name: "TikTok work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-tiktok"
+    timeoutSeconds: 1800
+    message: "Work loop: check for TikTok-assigned work (create, post, optimize short-form video). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/tiktok/agent-outputs/."
+    enabledByDefault: false
+  - id: instagram-work-loop
+    name: "Instagram work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-instagram"
+    timeoutSeconds: 1800
+    message: "Work loop: check for Instagram-assigned work (stories, reels, posts, engagement). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/instagram/agent-outputs/."
+    enabledByDefault: false
+  - id: youtube-work-loop
+    name: "YouTube work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-youtube"
+    timeoutSeconds: 1800
+    message: "Work loop: check for YouTube-assigned work (video content, descriptions, community). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/youtube/agent-outputs/."
+    enabledByDefault: false
+  - id: facebook-work-loop
+    name: "Facebook work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-facebook"
+    timeoutSeconds: 1800
+    message: "Work loop: check for Facebook-assigned work (posts, groups, ads, engagement). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/facebook/agent-outputs/."
+    enabledByDefault: false
+  - id: x-work-loop
+    name: "X/Twitter work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-x"
+    timeoutSeconds: 1800
+    message: "Work loop: check for X/Twitter-assigned work (tweets, threads, engagement, spaces). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/x/agent-outputs/."
+    enabledByDefault: false
+  - id: linkedin-work-loop
+    name: "LinkedIn work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-linkedin"
+    timeoutSeconds: 1800
+    message: "Work loop: check for LinkedIn-assigned work (posts, articles, professional engagement). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/linkedin/agent-outputs/."
     enabledByDefault: false
   - id: execution-loop
     name: "Execution loop"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
-    message: "Automated execution loop: make progress on in-progress tickets, keep changes small/safe, and update notes/status.md."
+    agentId: "{{teamId}}-lead"
+    timeoutSeconds: 1800
+    message: "Execution loop (Social Media Team): complete in-progress tickets and update notes/status.md. Finish each ticket fully before moving on."
     enabledByDefault: false
   # pr-watcher omitted (enable only when a real PR integration exists)
 requiredSkills: []
@@ -119,9 +220,10 @@ templates:
     - `roles/<role>/agent-outputs/` (append-only)
     - `../shared-context/agent-outputs/` (team-level, read/write from role via `../`)
 
-    ## Role work loop contract (safe-idle)
+    ## Role work loop contract
     - No-op unless explicit queued work exists for the role.
-    - If work happens, write back in order: ticket → `../notes/status.md` → `roles/<role>/agent-outputs/`.
+    - If work exists, complete it fully. If too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains.
+    - Write back in order: ticket → `../notes/status.md` → `roles/<role>/agent-outputs/`.
 
   sharedContext.priorities: |
     # Priorities (lead-curated)

package/recipes/default/writing-team.md

@@ -9,13 +9,42 @@ cronJobs:
     name: "Lead triage loop"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
-    message: "Automated lead triage loop: triage inbox/tickets, assign work, and update notes/status.md."
+    agentId: "{{teamId}}-lead"
+    timeoutSeconds: 1800
+    message: "Lead triage loop (Writing Team): triage inbox/tickets, assign work, and update notes/status.md. Complete all pending triage before finishing."
+    enabledByDefault: false
+
+  - id: outliner-work-loop
+    name: "Outliner work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-outliner"
+    timeoutSeconds: 1800
+    message: "Work loop: check for outlining work (research, structure, create outlines). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/outliner/agent-outputs/."
+    enabledByDefault: false
+  - id: writer-work-loop
+    name: "Writer work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-writer"
+    timeoutSeconds: 1800
+    message: "Work loop: check for writing-assigned work (draft, revise, polish content). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/writer/agent-outputs/."
+    enabledByDefault: false
+  - id: editor-work-loop
+    name: "Editor work loop (safe-idle)"
+    schedule: "*/30 7-23 * * 1-5"
+    timezone: "America/New_York"
+    agentId: "{{teamId}}-editor"
+    timeoutSeconds: 1800
+    message: "Work loop: check for editing work (review, proofread, fact-check, ensure quality). If you have work, complete it fully. If the task is too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains. Write outputs under roles/editor/agent-outputs/."
     enabledByDefault: false
   - id: execution-loop
     name: "Execution loop"
     schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
-    message: "Automated execution loop: make progress on in-progress tickets, keep changes small/safe, and update notes/status.md."
+    agentId: "{{teamId}}-lead"
+    timeoutSeconds: 1800
+    message: "Execution loop (Writing Team): complete in-progress tickets and update notes/status.md. Finish each ticket fully before moving on."
     enabledByDefault: false
   # pr-watcher omitted (enable only when a real PR integration exists)
 requiredSkills: []
@@ -106,9 +135,10 @@ templates:
     - `roles/<role>/agent-outputs/` (append-only)
     - `../shared-context/agent-outputs/` (team-level, read/write from role via `../`)
 
-    ## Role work loop contract (safe-idle)
+    ## Role work loop contract
     - No-op unless explicit queued work exists for the role.
-    - If work happens, write back in order: ticket → `../notes/status.md` → `roles/<role>/agent-outputs/`.
+    - If work exists, complete it fully. If too large for one session, complete a meaningful self-contained piece and update the ticket with what's done and what remains.
+    - Write back in order: ticket → `../notes/status.md` → `roles/<role>/agent-outputs/`.
 
   sharedContext.priorities: |
     # Priorities (lead-curated)

package/src/handlers/cron.ts

@@ -64,7 +64,7 @@ type CronReconcileScope =
 
 function buildCronJobForCreate(
   scope: CronReconcileScope,
-  j: { id: string; name?: string; schedule?: string; timezone?: string; channel?: string; to?: string; agentId?: string; description?: string; message?: string; enabledByDefault?: boolean; delivery?: 'none' | 'announce' },
+  j: { id: string; name?: string; schedule?: string; timezone?: string; channel?: string; to?: string; agentId?: string; description?: string; message?: string; enabledByDefault?: boolean; delivery?: 'none' | 'announce'; timeoutSeconds?: number },
   wantEnabled: boolean
 ): Record<string, unknown> {
   const name =
@@ -90,10 +90,12 @@ function buildCronJobForCreate(
     wakeMode: "next-heartbeat",
     sessionTarget,
     schedule: { kind: "cron", expr: j.schedule, ...(j.timezone ? { tz: j.timezone } : {}) },
-    payload: effectiveAgentId ? { kind: "agentTurn", message: j.message } : { kind: "systemEvent", text: j.message },
+    payload: effectiveAgentId
+      ? { kind: "agentTurn", message: j.message, ...(j.timeoutSeconds ? { timeoutSeconds: j.timeoutSeconds } : {}) }
+      : { kind: "systemEvent", text: j.message },
     ...(j.delivery === 'none'
       ? { delivery: { mode: "none" } }
-      : j.channel || j.to
+      : j.delivery === 'announce' || j.channel || j.to
         ? {
             delivery: {
               mode: "announce",
@@ -102,12 +104,14 @@ function buildCronJobForCreate(
               bestEffort: true,
             },
           }
-        : {}),
+        : // Default to none — OpenClaw defaults isolated agentTurn crons to
+          // "announce" which errors when no channel target is available.
+          { delivery: { mode: "none" } }),
   };
 }
 
 function buildCronJobPatch(
-  j: { name?: string; schedule?: string; timezone?: string; channel?: string; to?: string; agentId?: string; description?: string; message?: string; delivery?: 'none' | 'announce' },
+  j: { name?: string; schedule?: string; timezone?: string; channel?: string; to?: string; agentId?: string; description?: string; message?: string; delivery?: 'none' | 'announce'; timeoutSeconds?: number },
   name: string
 ): CronJobPatch {
   const effectiveAgentId = typeof j.agentId === "string" && j.agentId.trim() ? j.agentId.trim() : undefined;
@@ -119,17 +123,23 @@ function buildCronJobPatch(
     sessionTarget: effectiveAgentId ? "isolated" : "main",
     wakeMode: "next-heartbeat",
     schedule: { kind: "cron", expr: j.schedule, ...(j.timezone ? { tz: j.timezone } : {}) },
-    payload: effectiveAgentId ? { kind: "agentTurn", message: j.message } : { kind: "systemEvent", text: j.message },
+    payload: effectiveAgentId
+      ? { kind: "agentTurn", message: j.message, ...(j.timeoutSeconds ? { timeoutSeconds: j.timeoutSeconds } : {}) }
+      : { kind: "systemEvent", text: j.message },
   };
   if (j.delivery === 'none') {
     patch.delivery = { mode: "none" };
-  } else if (j.channel || j.to) {
+  } else if (j.delivery === 'announce' || j.channel || j.to) {
     patch.delivery = {
       mode: "announce",
       ...(j.channel ? { channel: j.channel } : {}),
       ...(j.to ? { to: j.to } : {}),
       bestEffort: true,
     };
+  } else {
+    // Default to none — OpenClaw defaults isolated agentTurn crons to
+    // "announce" which errors when no channel target is available.
+    patch.delivery = { mode: "none" };
   }
   return patch;
 }

package/src/lib/recipe-frontmatter.ts

@@ -13,6 +13,8 @@ export type CronJobSpec = {
   enabledByDefault?: boolean;
   /** Delivery mode: "none" suppresses announce; "announce" delivers to chat. Omit to use gateway default. */
   delivery?: 'none' | 'announce';
+  /** Agent turn timeout in seconds. Sets how long the agent can run before being killed. */
+  timeoutSeconds?: number;
 };
 
 /** Raw input for a cron job from YAML (supports message/task/prompt for backward compat). */
@@ -30,6 +32,7 @@ type CronJobInput = {
   agentId?: unknown;
   enabledByDefault?: unknown;
   delivery?: unknown;
+  timeoutSeconds?: unknown;
 };
 
 export type RecipeFrontmatter = {
@@ -87,6 +90,7 @@ function buildCronJobSpec(j: CronJobInput, id: string): CronJobSpec {
     agentId: j.agentId != null ? String(j.agentId) : undefined,
     enabledByDefault: Boolean(j.enabledByDefault ?? false),
     delivery: j.delivery === 'none' || j.delivery === 'announce' ? j.delivery : undefined,
+    timeoutSeconds: typeof j.timeoutSeconds === 'number' && j.timeoutSeconds > 0 ? j.timeoutSeconds : undefined,
   };
 }
 

package/src/lib/workflows/workflow-worker.ts

@@ -515,8 +515,17 @@ export async function runWorkflowWorkerTick(api: OpenClawPluginApi, opts: {
     // by the runner/worker loop itself (they send a message + set awaiting state).
     const nextKind = String(nextNode.kind ?? '');
     if (nextKind === 'human_approval' || nextKind === 'start' || nextKind === 'end') {
-      // Re-enqueue onto the same agent so it can execute the next node deterministically.
-      await enqueueTask(teamDir, agentId, {
+      // Route approval nodes to the correct agent:
+      //   1. Explicit agentId on the node config (workflow author override)
+      //   2. Team lead (${teamId}-lead) — the natural orchestrator role
+      //   3. Fallback to the current agent (backwards compat)
+      const nextConfig = (nextNode as unknown as Record<string, unknown>)['config'];
+      const nextConfigObj = nextConfig && typeof nextConfig === 'object' && !Array.isArray(nextConfig)
+        ? (nextConfig as Record<string, unknown>) : {};
+      const explicitAgentId = String(nextConfigObj['agentId'] ?? '').trim();
+      const approvalAgentId = explicitAgentId || `${teamId}-lead` || agentId;
+
+      await enqueueTask(teamDir, approvalAgentId, {
         teamId,
         runId: task.runId,
         nodeId: nextNode.id,
@@ -528,7 +537,7 @@ export async function runWorkflowWorkerTick(api: OpenClawPluginApi, opts: {
         updatedAt: new Date().toISOString(),
         status: 'waiting_workers',
         nextNodeIndex: enqueueIdx,
-        events: [...cur.events, { ts: new Date().toISOString(), type: 'node.enqueued', nodeId: nextNode.id, agentId }],
+        events: [...cur.events, { ts: new Date().toISOString(), type: 'node.enqueued', nodeId: nextNode.id, agentId: approvalAgentId }],
       }));
 
       results.push({ taskId: task.id, runId: task.runId, nodeId: task.nodeId, status: 'ok' });