@jiggai/recipes 0.3.0 → 0.3.2

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: "coding"
-  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/recipes/default/writing-team.md

@@ -291,7 +291,7 @@ files:
     mode: createOnly
 
 tools:
-  profile: "coding"
+  profile: "messaging"
   allow: ["group:fs", "group:web"]
 ---
 # Writing Team Recipe