@jiggai/recipes 0.3.1 → 0.3.3

package/README.md

@@ -6,7 +6,9 @@
 
 ClawRecipes is an OpenClaw plugin that provides **CLI-first recipes** for scaffolding specialist agents and teams from Markdown.
 
-If you like durable workflows: ClawRecipes is built around a **file-first team workspace** (inbox/backlog/in-progress/testing/done) that plays nicely with git.
+If you like durable workflows, ClawRecipes is built around a **file-first team workspace** (inbox/backlog/in-progress/testing/done) that plays nicely with git.
+
+For those who prefer a beautiful user interface, install **[ClawKitchen](https://github.com/JIGGAI/ClawKitchen)** — our latest plugin where you can add, remove, update, and fully manage your teams in one place. It includes an agile workflow board, a goal tracker, and cron management for convenience.
 
 ## Quickstart
 ### 1) Install
@@ -54,16 +56,6 @@ openclaw recipes dispatch \
   --owner lead
 ```
 
-## License
-
-ClawRecipes is licensed under **Apache-2.0**.
-
-Attribution requirement (practical): if you redistribute ClawRecipes (or a derivative work), you must retain the license and attribution notices (see `LICENSE` and `NOTICE`).
-
-Branding note: the license does not grant permission to use JIGGAI trademarks except as required for reasonable and customary attribution. See `TRADEMARK.md`.
-
-Contributions: we welcome PRs. By contributing, you agree that your contributions are licensed under the project’s Apache-2.0 license.
-
 ## Commands (high level)
 - `openclaw recipes list|show|status`
 - `openclaw recipes scaffold` (agent → `workspace-<agentId>` + writes workspace recipe `~/.openclaw/workspace/recipes/<agentId>.md` by default)
@@ -118,7 +110,9 @@ Run:
 - `npm run test:smoke` (or `npm run scaffold:smoke`)
 
 Notes:
-- Creates a temporary `workspace-smoke-<timestamp>-team` under `~/.openclaw/` and then deletes it.
+- Creates a temporary `workspace-smoke-<timestamp>-team` under `~/.openclaw/`.
+- If it does not delete cleanly (crash/interrupt), run cleanup:
+  - `openclaw recipes cleanup-workspaces --prefix smoke- --yes`
 - Exits non-zero on mismatch.
 - Requires OpenClaw and workspace config.
 
@@ -180,9 +174,20 @@ Most users should focus on:
 - running the file-first workflow (dispatch → backlog → in-progress → testing → done)
 
 ## Goals
-- Release Clawmarket, https://github.com/JIGGAI/ClawMarket, public url https://clawkitchen.ai
-- Release ClawKitchen, https://github.com/JIGGAI/ClawKitchen
-- Merge at least 1 community pull request
+- ~~Release Clawmarket, https://github.com/JIGGAI/ClawMarket, public url https://clawkitchen.ai~~
+- ~~Release ClawKitchen, https://github.com/JIGGAI/ClawKitchen~~
+- ~~Merge at least 1 community pull request~~
 - Daily shipping/pull requests of ClawRecipes features
 - Improve recipes with more detailed agent files
-- Add ability to install skills for agents through ClawKitchen
+- Add ability to install skills for agents through ClawKitchen
+- Integrate ClawKitchen with ClawMarket to pull new recipes
+
+## License
+
+ClawRecipes is licensed under **Apache-2.0**.
+
+Attribution requirement (practical): if you redistribute ClawRecipes (or a derivative work), you must retain the license and attribution notices (see `LICENSE` and `NOTICE`).
+
+Branding note: the license does not grant permission to use JIGGAI trademarks except as required for reasonable and customary attribution. See `TRADEMARK.md`.
+
+Contributions: we welcome PRs. By contributing, you agree that your contributions are licensed under the project’s Apache-2.0 license.

package/docs/verify-built-in-team-recipes.md

@@ -59,6 +59,15 @@ openclaw cron list
 openclaw cron run <jobId>
 ```
 
+## Cleanup (important)
+These verification commands create temporary `workspace-<teamId>` directories.
+
+After you finish (or between runs), clean up test workspaces so they don’t accumulate:
+
+```bash
+openclaw recipes cleanup-workspaces --prefix smoke- --prefix qa- --prefix tmp- --prefix test- --yes
+```
+
 ## What to record
 - Any recipe that fails to scaffold
 - Any cron job install/update errors

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jiggai/recipes",
-  "version": "0.3.1",
+  "version": "0.3.3",
   "description": "ClawRecipes plugin for OpenClaw (markdown recipes -> scaffold agents/teams)",
   "main": "index.ts",
   "type": "commonjs",

package/recipes/default/development-team.md

@@ -1,40 +1,23 @@
 ---
 id: development-team
 name: Development Team
-version: 0.2.1
+version: 0.2.0
 description: A small engineering team with a shared workspace (lead, dev, devops, test) using file-first tickets.
 kind: team
 cronJobs:
   - id: lead-triage-loop
     name: "Lead triage loop"
-    schedule: "*/30 8-23 * * 1-5"
-    agentId: "{{teamId}}-lead"
-    channel: "last"
-    message: "Lead triage loop (automated). Goal: keep tickets moving. Steps: run ticket hygiene; inspect board; pull next actionable work into in-progress; assign owners; write updates to tickets (## Comments) and notes/status.md. If lowest-numbered in-progress is hard-blocked, advance the next unblocked ticket (or pull from backlog)."
-    enabledByDefault: false
+    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. Anti-stuck: if lowest in-progress is HARD BLOCKED, advance the next unblocked ticket (or pull from backlog). If in-progress is stale (>12h no dated update), comment or move it back."
+    enabledByDefault: true
   - id: execution-loop
     name: "Execution loop"
-    schedule: "*/30 8-23 * * 1-5"
-    agentId: "{{teamId}}-lead"
-    channel: "last"
-    message: "Execution loop (automated). Goal: make concrete progress on the lowest-numbered in-progress ticket. Run ticket hygiene; perform repo lint/build checks (avoid noisy tests unless defined); update ticket + notes/status.md. Send a message only when there is a material change."
-    enabledByDefault: false
-  - id: pr-watcher
-    name: "PR watcher"
-    schedule: "*/30 8-23 * * 1-5"
-    agentId: "{{teamId}}-lead"
-    channel: "last"
-    message: "PR watcher (automated). Goal: watch ticket-linked PR URLs; summarize failing checks; if merged, move tickets to done with a short completion report. Requires GitHub access/auth on the controller."
-    enabledByDefault: false
-
-  - id: testing-lane-loop
-    name: "Testing lane loop"
-    schedule: "*/30 0-1,7-23 * * *"
+    schedule: "*/30 7-23 * * 1-5"
     timezone: "America/New_York"
-    agentId: "{{teamId}}-test"
-    channel: "last"
-    message: "Testing lane loop (automated). Goal: drain work/testing reliably. For each ticket in work/testing: follow the ticket's '## Verification steps'; record results under ## Comments; if it passes, complete the ticket; if it fails, write a clear repro + fix request and hand back to dev; if blocked on an unmerged PR/deploy, note and skip. Also keep notes/status.md current (3–5 bullets)."
+    message: "Automated execution loop: make progress on in-progress tickets, keep changes small/safe, and update notes/status.md."
     enabledByDefault: false
+  # pr-watcher omitted (enable only when a real PR integration exists)
 requiredSkills: []
 team:
   teamId: development-team
@@ -81,7 +64,6 @@ templates:
 
     Team: {{teamId}}
     Shared workspace: {{teamDir}}
-    Role: lead
 
     ## Guardrails (read → act → write)
 
@@ -90,26 +72,24 @@ templates:
        - `notes/plan.md`
        - `notes/status.md`
        - `shared-context/priorities.md`
-       - the current ticket
-
-    During work (every loop):
-    1) Run hygiene:
-       - `./scripts/ticket-hygiene.sh`
+       - the relevant ticket(s)
 
     After you act:
     1) Write back:
-       - Update the ticket with decisions/assignments and a dated entry under `## Comments`.
-       - Keep `notes/status.md` current (add 3–5 bullets per active ticket).
-       - Append detailed logs/output to `shared-context/agent-outputs/` (append-only).
+       - Update tickets with decisions/assignments.
+       - Keep `notes/status.md` current (3–5 bullets per active ticket).
 
     ## Curator model
 
-    You curate:
+    You are the curator of:
     - `notes/plan.md`
     - `shared-context/priorities.md`
 
-    Other agents should not edit curated files; they append to:
+    Everyone else should append to:
     - `shared-context/agent-outputs/` (append-only)
+    - `shared-context/feedback/`
+
+    Your job is to periodically distill those inputs into the curated files.
 
     ## File-first workflow (tickets)
 
@@ -121,9 +101,29 @@ templates:
     - `work/in-progress/` — tickets currently being executed
     - `work/testing/` — tickets awaiting QA verification
     - `work/done/` — completed tickets + completion notes
-
-    Handoff to QA (keeps assignment stubs consistent):
-    - `openclaw recipes handoff --team-id {{teamId}} --ticket <NNNN> --yes`
+    - `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.
+    - The developer pulls the lowest-numbered ticket assigned to them.
+
+    ### Ticket format
+    See `TICKETS.md` in the team root. Every ticket should include:
+    - Context
+    - Requirements
+    - Acceptance criteria
+    - Owner (dev/devops)
+    - Status
+
+    ### Your responsibilities
+    - For every new request in `inbox/`, create a normalized ticket in `work/backlog/`.
+    - Curate `notes/plan.md` and `shared-context/priorities.md`.
+    - Keep `notes/status.md` updated.
+    - When work is ready for QA, move the ticket to `work/testing/` and assign it to the tester.
+    - Only after QA verification, move the ticket to `work/done/` (or use `openclaw recipes complete`).
+    - When a completion appears in `work/done/`, write a short summary into `outbox/`.
 
   dev.soul: |
     # SOUL.md
@@ -134,32 +134,48 @@ templates:
   dev.agents: |
     # AGENTS.md
 
-    Team: {{teamId}}
     Shared workspace: {{teamDir}}
-    Role: dev
 
     ## Guardrails (read → act → write)
 
-    Before you change anything, read:
-    - `notes/plan.md`
-    - `notes/status.md`
-    - `shared-context/priorities.md`
-    - the current ticket
+    Before you change anything:
+    1) Read:
+       - `notes/plan.md`
+       - `notes/status.md`
+       - `shared-context/priorities.md`
+       - the current ticket you’re working on
+
+    While working:
+    - Keep changes small and safe.
+    - Prefer file-first coordination over chat.
+
+    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).
+       - Append detailed output to `shared-context/agent-outputs/` (append-only).
+
+    Curator model:
+    - Lead curates `notes/plan.md` and `shared-context/priorities.md`.
+    - You should NOT edit curated files; propose changes via `agent-outputs/`.
+
+    ## How you work (pull system)
+
+    1) Look in `work/in-progress/` for any ticket already assigned to you.
+       - If present: continue it.
 
-    Quick hygiene around stage moves:
-    - `./scripts/ticket-hygiene-dev.sh`
+    2) Otherwise, pick the next ticket from `work/backlog/`:
+       - Choose the lowest-numbered `0001-...md` ticket assigned to `dev`.
 
-    After you act, write back:
-    - Update the ticket with what you did + verification steps.
-    - Check/respond in the ticket’s `## Comments` section (especially if you were pinged).
-    - Add 3–5 bullets to `notes/status.md`.
-    - Append detailed logs/output to `shared-context/agent-outputs/` (append-only).
+    3) Move the ticket file from `work/backlog/` → `work/in-progress/`.
 
-    ## Pull system
+    4) Do the work.
+
+    5) Write a completion report into `work/done/` with:
+       - What changed
+       - How to test
+       - Any follow-ups
 
-    - Continue any ticket already assigned to you in `work/in-progress/`.
-    - Otherwise pull the lowest-numbered assigned ticket from `work/backlog/` and move it to `work/in-progress/`.
-    - Keep changes small and reversible.
   devops.soul: |
     # SOUL.md
 
@@ -169,26 +185,44 @@ templates:
   devops.agents: |
     # AGENTS.md
 
-    Team: {teamId}
-    Shared workspace: {teamDir}
-    Role: devops
+    Shared workspace: {{teamDir}}
 
     ## Guardrails (read → act → write)
-    Before you act:
+
+    Before you change anything:
     1) Read:
        - `notes/plan.md`
        - `notes/status.md`
-       - relevant ticket(s) in `work/in-progress/`
-       - any relevant shared context under `shared-context/`
+       - `shared-context/priorities.md`
+       - the current ticket you’re working on
 
-    After you act:
+    After you finish a work session:
     1) Write back:
-       - Put outputs in the agreed folder (usually `outbox/` or a ticket file).
-       - Update the ticket with what you did and where the artifact is.
+       - Update the ticket with what you did + verification steps.
+       - Add **3–5 bullets** to `notes/status.md`.
+       - Append detailed output/logs to `shared-context/agent-outputs/` (append-only).
+
+    Curator model:
+    - Lead curates `notes/plan.md` and `shared-context/priorities.md`.
+    - You should NOT edit curated files; propose changes via `agent-outputs/`.
+
+    ## How you work (pull system)
+
+    1) Look in `work/in-progress/` for any ticket already assigned to you.
+       - If present: continue it.
+
+    2) Otherwise, pick the next ticket from `work/backlog/`:
+       - Choose the lowest-numbered `0001-...md` ticket assigned to `devops`.
+
+    3) Move the ticket file from `work/backlog/` → `work/in-progress/`.
+
+    4) Do the work.
+
+    5) Write a completion report into `work/done/` with:
+       - What changed
+       - How to verify
+       - Rollback notes (if applicable)
 
-    ## Workflow
-    - Prefer a pull model: wait for a clear task from the lead, or propose a scoped task.
-    - Keep work small and reversible.
   lead.tools: |
     # TOOLS.md
 
@@ -247,30 +281,68 @@ templates:
   test.agents: |
     # AGENTS.md
 
-    Team: {{teamId}}
     Shared workspace: {{teamDir}}
-    Role: test
 
     ## Guardrails (read → act → write)
 
-    Before you verify anything, read:
-    - `notes/plan.md`
-    - `notes/status.md`
-    - `shared-context/priorities.md`
-    - the ticket in `work/testing/`
+    Before verifying:
+    1) Read:
+       - `notes/plan.md`
+       - `notes/status.md`
+       - `shared-context/priorities.md`
+       - the ticket under test
 
-    After you verify, write back:
-    - Record QA verification (preferred): create `work/testing/<ticket>.testing-verified.md`.
-      - Alternative: add a clear `## QA verification` section in the ticket.
-    - If failing: write a concise bug note, then move the ticket back to `work/in-progress/` and assign to the right owner.
-    - Check/respond in the ticket’s `## Comments` section.
-    - Add 3–5 bullets to `notes/status.md`.
-    - Append detailed logs/output to `shared-context/agent-outputs/` (append-only).
+    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).
+       - Append detailed findings to `shared-context/feedback/` or `shared-context/agent-outputs/`.
 
-    ## Testing lane workflow
+    Curator model:
+    - Lead curates `notes/plan.md` and `shared-context/priorities.md`.
+    - You should NOT edit curated files; propose changes via feedback/outputs.
+
+    ## How you work
+
+    1) Look in `work/testing/` for tickets assigned to you.
+
+    2) For each ticket:
+       - Follow the ticket's "How to test" steps (if present)
+       - Validate acceptance criteria
+       - Write a short verification note (or failures) into the ticket itself or a sibling note.
+
+    3) If it passes:
+       - Move the ticket to `work/done/` (or ask the lead to do it).
+
+    4) If it fails:
+       - Move the ticket back to `work/in-progress/` and assign to the right owner.
+
+    ## Cleanup after testing
+
+    If your test involved creating temporary resources (e.g., scaffolding test teams, creating test workspaces), **clean them up** after verification:
+
+    1) Remove test workspaces:
+       ```bash
+       rm -rf ~/.openclaw/workspace-<test-team-id>
+       ```
+
+    2) Remove test agents from config (agents whose id starts with the test team id):
+       - Edit `~/.openclaw/openclaw.json` and remove entries from `agents.list[]`
+       - Or wait for `openclaw recipes remove-team` (once available)
+
+    3) Remove any cron jobs created for the test team:
+       ```bash
+       openclaw cron list --all --json | grep "<test-team-id>"
+       openclaw cron remove <jobId>
+       ```
+
+    4) Restart the gateway if you modified config:
+       ```bash
+       openclaw gateway restart
+       ```
+
+    **Naming convention:** When scaffolding test teams, use a prefix like `qa-<ticketNum>-` (e.g., `qa-0017-social-team`) so cleanup is easier.
 
-    - Work from `work/testing/`.
-    - Follow the ticket’s “How to test” steps and validate acceptance criteria.
   test.tools: |
     # TOOLS.md
 
@@ -328,4 +400,3 @@ Scaffolds a shared team workspace and four namespaced agents (lead/dev/devops/te
   - allow groups: group:automation, group:fs, group:runtime, group:web
   - deny: (none)
 - Safety note: most bundled teams default to denying `exec` unless a role explicitly needs it.
-

package/recipes/default/stock-trader-team.md

@@ -2,292 +2,334 @@
 id: stock-trader-team
 name: Stock Trader Team
 version: 0.1.0
-description: A trading support team (research, signals, risk, journaling, ops) coordinated via a shared workspace.
+description: A trading support team (research, signals, risk, journaling, ops) coordinated
+  via a shared workspace.
 kind: team
 cronJobs:
-  - id: lead-triage-loop
-    name: "Lead triage loop"
-    schedule: "*/30 7-23 * * 1-5"
-    timezone: "America/New_York"
-    message: "Automated lead triage loop (Stock Trader): triage research/tickets, assign work, and update notes/status.md."
-    enabledByDefault: false
-  - id: execution-loop
-    name: "Execution loop"
-    schedule: "*/30 7-23 * * 1-5"
-    timezone: "America/New_York"
-    message: "Automated execution loop (Stock Trader): make progress on in-progress tickets and update notes/status.md."
-    enabledByDefault: false
+- id: lead-triage-loop
+  name: Lead triage loop
+  schedule: '*/30 7-23 * * 1-5'
+  timezone: America/New_York
+  message: 'Automated lead triage loop (Stock Trader): triage research/tickets, assign
+    work, and update notes/status.md.'
+  enabledByDefault: false
+- id: execution-loop
+  name: Execution loop
+  schedule: '*/30 7-23 * * 1-5'
+  timezone: America/New_York
+  message: 'Automated execution loop (Stock Trader): make progress on in-progress
+    tickets and update notes/status.md.'
+  enabledByDefault: false
 requiredSkills: []
 team:
   teamId: stock-trader-team
 agents:
-  - role: lead
-    name: Head Trader / Lead
-    tools:
-      profile: "coding"
-      allow: ["group:fs", "group:web", "group:runtime"]
-      deny: ["exec"]
-  - role: researcher
-    name: Market Researcher
-    tools:
-      profile: "coding"
-      allow: ["group:fs", "group:web"]
-      deny: ["exec"]
-  - role: signals
-    name: Signals & Watchlists
-    tools:
-      profile: "coding"
-      allow: ["group:fs", "group:web"]
-      deny: ["exec"]
-  - role: risk
-    name: Risk Manager
-    tools:
-      profile: "coding"
-      allow: ["group:fs", "group:web"]
-      deny: ["exec"]
-  - role: journal
-    name: Trade Journaler
-    tools:
-      profile: "coding"
-      allow: ["group:fs"]
-      deny: ["exec"]
-  - role: ops
-    name: Trading Ops
-    tools:
-      profile: "coding"
-      allow: ["group:fs", "group:web"]
-      deny: ["exec"]
-
+- role: lead
+  name: Head Trader / Lead
+  tools:
+    profile: coding
+    allow:
+    - group:fs
+    - group:web
+    - group:runtime
+    deny:
+    - exec
+- role: researcher
+  name: Market Researcher
+  tools:
+    profile: coding
+    allow:
+    - group:fs
+    - group:web
+    deny:
+    - exec
+- role: signals
+  name: Signals & Watchlists
+  tools:
+    profile: coding
+    allow:
+    - group:fs
+    - group:web
+    deny:
+    - exec
+- role: risk
+  name: Risk Manager
+  tools:
+    profile: coding
+    allow:
+    - group:fs
+    - group:web
+    deny:
+    - exec
+- role: journal
+  name: Trade Journaler
+  tools:
+    profile: coding
+    allow:
+    - group:fs
+    deny:
+    - exec
+- role: ops
+  name: Trading Ops
+  tools:
+    profile: coding
+    allow:
+    - group:fs
+    - group:web
+    deny:
+    - exec
 templates:
-  lead.soul: |
-    # SOUL.md
+  lead.soul: '# SOUL.md
+
+
+    You are the Team Lead / Dispatcher for {{{teamId}}}.
 
-    You are the Team Lead / Dispatcher for {{teamId}}.
 
     Core job:
+
     - Convert new requests into scoped tickets.
+
     - Assign work to Dev or DevOps.
+
     - Monitor progress and unblock.
+
     - Report completions.
-  lead.agents: |
-    # AGENTS.md
-
-    Team: {{teamId}}
-    Shared workspace: {{teamDir}}
-
-    ## Guardrails (read → act → write)
-
-    Before you act:
-    1) Read:
-       - `notes/plan.md`
-       - `notes/status.md`
-       - `shared-context/priorities.md`
-       - the relevant ticket(s)
-
-    After you act:
-    1) Write back:
-       - Update tickets with decisions/assignments.
-       - Keep `notes/status.md` current (3–5 bullets per active ticket).
-
-    ## Curator model
-
-    You are the curator of:
-    - `notes/plan.md`
-    - `shared-context/priorities.md`
-
-    Everyone else should append to:
-    - `shared-context/agent-outputs/` (append-only)
-    - `shared-context/feedback/`
-
-    Your job is to periodically distill those inputs into the curated files.
-
-    ## File-first workflow (tickets)
-
-    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
-
-    ### Ticket numbering (critical)
-    - Backlog tickets MUST be named `0001-...md`, `0002-...md`, etc.
-    - The developer pulls the lowest-numbered ticket assigned to them.
-
-    ### Ticket format
-    See `TICKETS.md` in the team root. Every ticket should include:
-    - Context
-    - Requirements
-    - Acceptance criteria
-    - Owner (dev/devops)
-    - Status
-
-    ### Your responsibilities
-    - For every new request in `inbox/`, create a normalized ticket in `work/backlog/`.
-    - Curate `notes/plan.md` and `shared-context/priorities.md`.
-    - Keep `notes/status.md` updated.
-    - When work is ready for QA, move the ticket to `work/testing/` and assign it to the tester.
-    - Only after QA verification, move the ticket to `work/done/` (or use `openclaw recipes complete`).
-    - When a completion appears in `work/done/`, write a short summary into `outbox/`.
-  researcher.soul: |
-    # SOUL.md
-
-    You are the Market Researcher on {{teamId}}.
 
-    You track macro/sector themes and summarize what matters.
+    '
+  lead.agents: "# AGENTS.md\n\nTeam: {{{teamId}}}\nShared workspace: {{{teamDir}}}\n\
+    \n## Guardrails (read \u2192 act \u2192 write)\n\nBefore you act:\n1) Read:\n\
+    \   - `notes/plan.md`\n   - `notes/status.md`\n   - `shared-context/priorities.md`\n\
+    \   - the relevant ticket(s)\n\nAfter you act:\n1) Write back:\n   - Update tickets\
+    \ with decisions/assignments.\n   - Keep `notes/status.md` current (3\u20135 bullets\
+    \ per active ticket).\n\n## Curator model\n\nYou are the curator of:\n- `notes/plan.md`\n\
+    - `shared-context/priorities.md`\n\nEveryone else should append to:\n- `shared-context/agent-outputs/`\
+    \ (append-only)\n- `shared-context/feedback/`\n\nYour job is to periodically distill\
+    \ those inputs into the curated files.\n\n## File-first workflow (tickets)\n\n\
+    Source of truth is the shared team workspace.\n\nFolders:\n- `inbox/` \u2014 raw\
+    \ incoming requests (append-only)\n- `work/backlog/` \u2014 normalized tickets,\
+    \ filename-ordered (`0001-...md`)\n- `work/in-progress/` \u2014 tickets currently\
+    \ being executed\n- `work/testing/` \u2014 tickets awaiting QA verification\n\
+    - `work/done/` \u2014 completed tickets + completion notes\n- `notes/plan.md`\
+    \ \u2014 current plan / priorities (curated)\n- `notes/status.md` \u2014 current\
+    \ status snapshot\n- `shared-context/` \u2014 shared context + append-only outputs\n\
+    \n### Ticket numbering (critical)\n- Backlog tickets MUST be named `0001-...md`,\
+    \ `0002-...md`, etc.\n- The developer pulls the lowest-numbered ticket assigned\
+    \ to them.\n\n### Ticket format\nSee `TICKETS.md` in the team root. Every ticket\
+    \ should include:\n- Context\n- Requirements\n- Acceptance criteria\n- Owner (dev/devops)\n\
+    - Status\n\n### Your responsibilities\n- For every new request in `inbox/`, create\
+    \ a normalized ticket in `work/backlog/`.\n- Curate `notes/plan.md` and `shared-context/priorities.md`.\n\
+    - Keep `notes/status.md` updated.\n- When work is ready for QA, move the ticket\
+    \ to `work/testing/` and assign it to the tester.\n- Only after QA verification,\
+    \ move the ticket to `work/done/` (or use `openclaw recipes complete`).\n- When\
+    \ a completion appears in `work/done/`, write a short summary into `outbox/`.\n"
+  researcher.soul: '# SOUL.md
+
+
+    You are the Market Researcher on {{{teamId}}}.
 
-  researcher.agents: |
-    # AGENTS.md
 
-    Team: {teamId}
-    Shared workspace: {teamDir}
-    Role: researcher
+    You track macro/sector themes and summarize what matters.
 
-    ## Guardrails (read → act → write)
-    Before you act:
-    1) Read:
-       - `notes/plan.md`
-       - `notes/status.md`
-       - relevant ticket(s) in `work/in-progress/`
-       - any relevant shared context under `shared-context/`
+    '
+  researcher.agents: "# AGENTS.md\n\nTeam: {{teamId}}\nShared workspace: {{teamDir}}\n\
+    Role: researcher\n\n## Guardrails (read \u2192 act \u2192 write)\nBefore you act:\n\
+    1) Read:\n   - `notes/plan.md`\n   - `notes/status.md`\n   - relevant ticket(s)\
+    \ in `work/in-progress/`\n   - any relevant shared context under `shared-context/`\n\
+    \nAfter you act:\n1) Write back:\n   - Put outputs in the agreed folder (usually\
+    \ `outbox/` or a ticket file).\n   - Update the ticket with what you did and where\
+    \ the artifact is.\n\n## Workflow\n- Prefer a pull model: wait for a clear task\
+    \ from the lead, or propose a scoped task.\n- Keep work small and reversible.\n"
+  signals.soul: '# SOUL.md
 
-    After you act:
-    1) Write back:
-       - Put outputs in the agreed folder (usually `outbox/` or a ticket file).
-       - Update the ticket with what you did and where the artifact is.
 
-    ## Workflow
-    - Prefer a pull model: wait for a clear task from the lead, or propose a scoped task.
-    - Keep work small and reversible.
-  signals.soul: |
-    # SOUL.md
+    You maintain signals, screeners, and watchlists for {{{teamId}}}.
 
-    You maintain signals, screeners, and watchlists for {{teamId}}.
 
     You produce concise entries: ticker, setup, catalyst, invalidation.
 
-  signals.agents: |
-    # AGENTS.md
+    '
+  signals.agents: "# AGENTS.md\n\nTeam: {{teamId}}\nShared workspace: {{teamDir}}\n\
+    Role: signals\n\n## Guardrails (read \u2192 act \u2192 write)\nBefore you act:\n\
+    1) Read:\n   - `notes/plan.md`\n   - `notes/status.md`\n   - relevant ticket(s)\
+    \ in `work/in-progress/`\n   - any relevant shared context under `shared-context/`\n\
+    \nAfter you act:\n1) Write back:\n   - Put outputs in the agreed folder (usually\
+    \ `outbox/` or a ticket file).\n   - Update the ticket with what you did and where\
+    \ the artifact is.\n\n## Workflow\n- Prefer a pull model: wait for a clear task\
+    \ from the lead, or propose a scoped task.\n- Keep work small and reversible.\n"
+  risk.soul: '# SOUL.md
 
-    Team: {teamId}
-    Shared workspace: {teamDir}
-    Role: signals
 
-    ## Guardrails (read → act → write)
-    Before you act:
-    1) Read:
-       - `notes/plan.md`
-       - `notes/status.md`
-       - relevant ticket(s) in `work/in-progress/`
-       - any relevant shared context under `shared-context/`
+    You are the Risk Manager on {{{teamId}}}.
 
-    After you act:
-    1) Write back:
-       - Put outputs in the agreed folder (usually `outbox/` or a ticket file).
-       - Update the ticket with what you did and where the artifact is.
 
-    ## Workflow
-    - Prefer a pull model: wait for a clear task from the lead, or propose a scoped task.
-    - Keep work small and reversible.
-  risk.soul: |
-    # SOUL.md
+    You enforce position sizing, stop rules, and drawdown controls.
 
-    You are the Risk Manager on {{teamId}}.
+    '
+  risk.agents: "# AGENTS.md\n\nTeam: {{teamId}}\nShared workspace: {{teamDir}}\nRole:\
+    \ risk\n\n## Guardrails (read \u2192 act \u2192 write)\nBefore you act:\n1) Read:\n\
+    \   - `notes/plan.md`\n   - `notes/status.md`\n   - relevant ticket(s) in `work/in-progress/`\n\
+    \   - any relevant shared context under `shared-context/`\n\nAfter you act:\n\
+    1) Write back:\n   - Put outputs in the agreed folder (usually `outbox/` or a\
+    \ ticket file).\n   - Update the ticket with what you did and where the artifact\
+    \ is.\n\n## Workflow\n- Prefer a pull model: wait for a clear task from the lead,\
+    \ or propose a scoped task.\n- Keep work small and reversible.\n"
+  journal.soul: '# SOUL.md
 
-    You enforce position sizing, stop rules, and drawdown controls.
 
-  risk.agents: |
-    # AGENTS.md
+    You are the Trade Journaler on {{{teamId}}}.
 
-    Team: {teamId}
-    Shared workspace: {teamDir}
-    Role: risk
 
-    ## Guardrails (read → act → write)
-    Before you act:
-    1) Read:
-       - `notes/plan.md`
-       - `notes/status.md`
-       - relevant ticket(s) in `work/in-progress/`
-       - any relevant shared context under `shared-context/`
+    You keep a clean daily log and capture lessons learned.
 
-    After you act:
-    1) Write back:
-       - Put outputs in the agreed folder (usually `outbox/` or a ticket file).
-       - Update the ticket with what you did and where the artifact is.
+    '
+  journal.agents: "# AGENTS.md\n\nTeam: {{teamId}}\nShared workspace: {{teamDir}}\n\
+    Role: journal\n\n## Guardrails (read \u2192 act \u2192 write)\nBefore you act:\n\
+    1) Read:\n   - `notes/plan.md`\n   - `notes/status.md`\n   - relevant ticket(s)\
+    \ in `work/in-progress/`\n   - any relevant shared context under `shared-context/`\n\
+    \nAfter you act:\n1) Write back:\n   - Put outputs in the agreed folder (usually\
+    \ `outbox/` or a ticket file).\n   - Update the ticket with what you did and where\
+    \ the artifact is.\n\n## Workflow\n- Prefer a pull model: wait for a clear task\
+    \ from the lead, or propose a scoped task.\n- Keep work small and reversible.\n"
+  ops.soul: '# SOUL.md
 
-    ## Workflow
-    - Prefer a pull model: wait for a clear task from the lead, or propose a scoped task.
-    - Keep work small and reversible.
-  journal.soul: |
-    # SOUL.md
 
-    You are the Trade Journaler on {{teamId}}.
+    You run trading ops for {{{teamId}}}.
 
-    You keep a clean daily log and capture lessons learned.
 
-  journal.agents: |
-    # AGENTS.md
+    You keep calendars, checklists, and tooling notes tidy.
 
-    Team: {teamId}
-    Shared workspace: {teamDir}
-    Role: journal
+    '
+  ops.agents: "# AGENTS.md\n\nOutput:\n- Calendar/cadence checklists \u2192 work/playbook/cadence.md\n\
+    - Tooling notes \u2192 shared-context/tooling/\n"
+  lead.tools: '# TOOLS.md
 
-    ## Guardrails (read → act → write)
-    Before you act:
-    1) Read:
-       - `notes/plan.md`
-       - `notes/status.md`
-       - relevant ticket(s) in `work/in-progress/`
-       - any relevant shared context under `shared-context/`
 
-    After you act:
-    1) Write back:
-       - Put outputs in the agreed folder (usually `outbox/` or a ticket file).
-       - Update the ticket with what you did and where the artifact is.
+    # Agent-local notes for lead (paths, conventions, env quirks).
 
-    ## Workflow
-    - Prefer a pull model: wait for a clear task from the lead, or propose a scoped task.
-    - Keep work small and reversible.
-  ops.soul: |
-    # SOUL.md
+    '
+  lead.status: '# STATUS.md
 
-    You run trading ops for {{teamId}}.
 
-    You keep calendars, checklists, and tooling notes tidy.
+    - (empty)
 
-  ops.agents: |
-    # AGENTS.md
+    '
+  lead.notes: '# NOTES.md
 
-    Output:
-    - Calendar/cadence checklists → work/playbook/cadence.md
-    - Tooling notes → shared-context/tooling/
 
-files:
-  - path: SOUL.md
-    template: soul
-    mode: createOnly
-  - path: AGENTS.md
-    template: agents
-    mode: createOnly
-  - path: TOOLS.md
-    template: tools
-    mode: createOnly
-  - path: STATUS.md
-    template: status
-    mode: createOnly
-  - path: NOTES.md
-    template: notes
-    mode: createOnly
+    - (empty)
+
+    '
+  researcher.tools: '# TOOLS.md
+
+
+    # Agent-local notes for researcher (paths, conventions, env quirks).
+
+    '
+  researcher.status: '# STATUS.md
+
+
+    - (empty)
+
+    '
+  researcher.notes: '# NOTES.md
+
+
+    - (empty)
+
+    '
+  signals.tools: '# TOOLS.md
+
+
+    # Agent-local notes for signals (paths, conventions, env quirks).
+
+    '
+  signals.status: '# STATUS.md
+
+
+    - (empty)
 
+    '
+  signals.notes: '# NOTES.md
+
+
+    - (empty)
+
+    '
+  risk.tools: '# TOOLS.md
+
+
+    # Agent-local notes for risk (paths, conventions, env quirks).
+
+    '
+  risk.status: '# STATUS.md
+
+
+    - (empty)
+
+    '
+  risk.notes: '# NOTES.md
+
+
+    - (empty)
+
+    '
+  journal.tools: '# TOOLS.md
+
+
+    # Agent-local notes for journal (paths, conventions, env quirks).
+
+    '
+  journal.status: '# STATUS.md
+
+
+    - (empty)
+
+    '
+  journal.notes: '# NOTES.md
+
+
+    - (empty)
+
+    '
+  ops.tools: '# TOOLS.md
+
+
+    # Agent-local notes for ops (paths, conventions, env quirks).
+
+    '
+  ops.status: '# STATUS.md
+
+
+    - (empty)
+
+    '
+  ops.notes: '# NOTES.md
+
+
+    - (empty)
+
+    '
+files:
+- path: SOUL.md
+  template: soul
+  mode: createOnly
+- path: AGENTS.md
+  template: agents
+  mode: createOnly
+- path: TOOLS.md
+  template: tools
+  mode: createOnly
+- path: STATUS.md
+  template: status
+  mode: createOnly
+- path: NOTES.md
+  template: notes
+  mode: createOnly
 tools:
-  profile: "messaging"
-  allow: ["group:fs", "group:web"]
+  profile: messaging
+  allow:
+  - group:fs
+  - group:web
   deny: []
 ---
 
@@ -308,4 +350,3 @@ Bundled team recipe.
   - deny: exec
 - Safety note: most bundled teams default to denying `exec` unless a role explicitly needs it.
 
-

package/src/handlers/team.ts

@@ -39,15 +39,16 @@ async function ensureTeamDirectoryStructure(
   ]);
 }
 
-async function writeTeamBootstrapFiles(
-  teamId: string,
-  teamDir: string,
-  sharedContextDir: string,
-  notesDir: string,
-  goalsDir: string,
-  overwrite: boolean,
-  opts?: { qaChecklist?: boolean }
-) {
+async function writeTeamBootstrapFiles(opts: {
+  teamId: string;
+  teamDir: string;
+  sharedContextDir: string;
+  notesDir: string;
+  goalsDir: string;
+  overwrite: boolean;
+  qaChecklist?: boolean;
+}) {
+  const { teamId, teamDir, sharedContextDir, notesDir, goalsDir, overwrite, qaChecklist } = opts;
   const mode = overwrite ? "overwrite" : "createOnly";
   await ensureDir(goalsDir);
   await writeFileSafely(
@@ -68,7 +69,7 @@ async function writeTeamBootstrapFiles(
     mode
   );
 
-  if (opts?.qaChecklist) {
+  if (qaChecklist) {
     await writeFileSafely(
       path.join(notesDir, "QA_CHECKLIST.md"),
       `# QA Checklist — ${teamId}\n\nUse this when verifying a ticket before moving it from work/testing/ → work/done/.\n\n## Checklist\n- [ ] Repro steps verified\n- [ ] Acceptance criteria met\n- [ ] No regressions in adjacent flows\n- [ ] Notes/screenshots attached (if relevant)\n\n## Verified by\n- QA: (name)\n- Date: (YYYY-MM-DD)\n\n## Links\n- Ticket: (path or URL)\n- PR/Commit: (optional)\n`,
@@ -184,7 +185,6 @@ export async function handleScaffoldTeam(
   await ensureDir(recipesDir);
   const overwriteRecipe = !!options.overwriteRecipe;
   const autoIncrement = !!options.autoIncrement;
-
   const explicitRecipeId = typeof options.recipeIdExplicit === "string" ? String(options.recipeIdExplicit).trim() : "";
   const baseRecipeId = explicitRecipeId || teamId;
   const workspaceRecipeId = await pickRecipeId({
@@ -201,7 +201,6 @@ export async function handleScaffoldTeam(
       `Workspace recipe already exists: recipes/${id}.md. Choose --recipe-id (e.g. ${suggestions.join(", ")}) or --auto-increment or --overwrite-recipe.`,
   });
   await writeWorkspaceRecipeFile(loaded, recipesDir, workspaceRecipeId, overwriteRecipe);
-
   const rolesDir = path.join(teamDir, "roles");
   const notesDir = path.join(teamDir, "notes");
   const workDir = path.join(teamDir, "work");
@@ -209,12 +208,17 @@ export async function handleScaffoldTeam(
   const sharedContextDir = path.join(teamDir, "shared-context");
   const goalsDir = path.join(notesDir, "goals");
 
-  const hasTestRole = (recipe.agents ?? []).some((a) => String(a.role ?? '').toLowerCase() === 'test');
-  const qaChecklist = Boolean(recipe.qaChecklist ?? false) || hasTestRole;
-
+  const qaChecklist = Boolean(recipe.qaChecklist ?? false) || (recipe.agents ?? []).some((a) => String(a.role ?? "").toLowerCase() === "test");
   await ensureTeamDirectoryStructure(teamDir, sharedContextDir, notesDir, workDir);
-  await writeTeamBootstrapFiles(teamId, teamDir, sharedContextDir, notesDir, goalsDir, overwrite, { qaChecklist });
-
+  await writeTeamBootstrapFiles({
+    teamId,
+    teamDir,
+    sharedContextDir,
+    notesDir,
+    goalsDir,
+    overwrite,
+    qaChecklist,
+  });
   const results = await scaffoldTeamAgents(api, recipe, teamId, teamDir, rolesDir, overwrite);
   await writeTeamMetadataAndConfig({ api, teamId, teamDir, recipe, results, applyConfig: !!options.applyConfig, overwrite });
 

package/src/lib/agent-config.ts

@@ -16,7 +16,17 @@ export function upsertAgentInConfig(cfgObj: AgentsConfigMutable, snippet: AgentC
   const list = cfgObj.agents.list;
   const idx = list.findIndex((a) => a?.id === snippet.id);
   const prev = idx >= 0 ? list[idx] : {};
-  const prevTools = (prev as any)?.tools as undefined | { profile?: string; allow?: string[]; deny?: string[] };
+
+  const prevTools = (() => {
+    const v = (prev as { tools?: unknown } | null | undefined)?.tools;
+    if (!v || typeof v !== "object") return undefined;
+    const t = v as { profile?: unknown; allow?: unknown; deny?: unknown };
+    return {
+      profile: typeof t.profile === "string" ? t.profile : undefined,
+      allow: Array.isArray(t.allow) ? (t.allow as string[]) : undefined,
+      deny: Array.isArray(t.deny) ? (t.deny as string[]) : undefined,
+    } as { profile?: string; allow?: string[]; deny?: string[] };
+  })();
   const nextTools =
     snippet.tools === undefined
       ? prevTools

package/src/lib/workspace.ts

@@ -1,12 +1,25 @@
+import os from "node:os";
 import path from "node:path";
 import type { OpenClawPluginApi } from "openclaw/plugin-sdk";
 import { ensureDir } from "./fs-utils";
 import { ticketStageDir } from "./lanes";
 
+/**
+ * Resolve the OpenClaw workspace root.
+ *
+ * Priority:
+ *  1) config: agents.defaults.workspace
+ *  2) env: OPENCLAW_WORKSPACE
+ *  3) default: ~/.openclaw/workspace
+ */
 export function resolveWorkspaceRoot(api: OpenClawPluginApi): string {
   const root = api.config.agents?.defaults?.workspace;
-  if (!root) throw new Error("agents.defaults.workspace is not set in config");
-  return root;
+  if (root) return root;
+
+  const envRoot = process.env.OPENCLAW_WORKSPACE;
+  if (envRoot) return envRoot;
+
+  return path.join(os.homedir(), ".openclaw", "workspace");
 }
 
 export function resolveTeamDir(api: OpenClawPluginApi, teamId: string): string {