@jiggai/recipes 0.2.18 → 0.2.21

package/docs/BUNDLED_RECIPES.md

@@ -193,6 +193,102 @@ Default tool policy:
 - allows `group:runtime`
 - does not deny `exec`
 
+---
+
+# Teams
+
+## 11) `marketing-team` (team)
+**Use when:** you want a full marketing execution loop: SEO + copy + ads + social + design + analytics.
+
+Scaffold:
+```bash
+openclaw recipes scaffold-team marketing-team --team-id marketing-team-team --apply-config
+```
+
+Roles:
+- lead, seo, copywriter, ads, social, designer, analyst
+
+---
+
+# Vertical packs (bundled team recipes)
+
+## 12) `business-team` (team)
+**Use when:** you want a general-purpose business execution team.
+
+Scaffold:
+```bash
+openclaw recipes scaffold-team business-team --team-id business-team-team --apply-config
+```
+
+Roles:
+- lead, ops, sales, marketing, finance, analyst
+
+## 13) `law-firm-team` (team)
+**Use when:** you want a legal practice workflow: intake → research → drafting → compliance.
+
+Scaffold:
+```bash
+openclaw recipes scaffold-team law-firm-team --team-id law-firm-team-team --apply-config
+```
+
+Roles:
+- lead, intake, researcher, drafter, compliance, ops
+
+## 14) `clinic-team` (team)
+**Use when:** you want a clinic ops workflow: intake/scheduling/billing/compliance/patient education.
+
+Scaffold:
+```bash
+openclaw recipes scaffold-team clinic-team --team-id clinic-team-team --apply-config
+```
+
+Roles:
+- lead, intake, scheduler, billing, compliance, educator
+
+## 15) `construction-team` (team)
+**Use when:** you want a construction delivery workflow: PM/estimation/scheduling/safety/procurement.
+
+Scaffold:
+```bash
+openclaw recipes scaffold-team construction-team --team-id construction-team-team --apply-config
+```
+
+Roles:
+- lead, pm, estimator, scheduler, safety, procurement
+
+## 16) `financial-planner-team` (team)
+**Use when:** you want a financial planning practice workflow.
+
+Scaffold:
+```bash
+openclaw recipes scaffold-team financial-planner-team --team-id financial-planner-team-team --apply-config
+```
+
+Roles:
+- lead, advisor, analyst, tax, insurance, ops
+
+## 17) `stock-trader-team` (team)
+**Use when:** you want a trading workflow: research/signals/risk/journaling.
+
+Scaffold:
+```bash
+openclaw recipes scaffold-team stock-trader-team --team-id stock-trader-team-team --apply-config
+```
+
+Roles:
+- lead, researcher, signals, risk, journal, ops
+
+## 18) `crypto-trader-team` (team)
+**Use when:** you want a crypto trading workflow with onchain research.
+
+Scaffold:
+```bash
+openclaw recipes scaffold-team crypto-trader-team --team-id crypto-trader-team-team --apply-config
+```
+
+Roles:
+- lead, onchain, news, risk, ops, journal
+
 ## Copying and modifying bundled recipes
 A good workflow is:
 1) Inspect:

package/docs/TEAM_WORKFLOW.md

@@ -24,25 +24,67 @@ When you scaffold a team:
 1) **Intake**
 - New requests land in `inbox/`.
 
-2) **Plan**
+2) **(Optional) Nudge / automation**
+- A cron job can periodically ping the team lead to triage `inbox/` and keep work moving.
+
+3) **Plan / triage (lead)**
 - Convert the request into a numbered ticket in `work/backlog/`.
+- Fill out: Context, Requirements, Acceptance Criteria, Tasks, Owner, Status, and verification steps.
+- **Every ticket must include a `## Comments` section.** Agents must check/respond to comments on tickets they’re assigned to **or** where they are mentioned via `@<agentname>`.
 - Filename ordering is the priority queue.
 
-3) **Execute**
+4) **Execute (dev/devops)**
 - Move ticket file to `work/in-progress/` (or use `take`).
 - Do work; write artifacts into `shared/` or agent workspaces.
 
-4) **Test**
+5) **Test**
 - Move ticket to `work/testing/`.
 - Assign `Owner: test` (or explicitly tag the tester role) and include clear “Verification steps” in the ticket.
 - Tester verifies and either:
   - moves to `work/done/` (pass), or
   - bounces back to `work/in-progress/` with a bug note (fail)
 
-5) **Complete**
+6) **Complete**
 - Move ticket to `work/done/` (or use `complete`).
 - Add `Completed:` timestamp (automated by `complete` or `move-ticket --completed`).
 
+## Sub-agents + waking up the lead (important)
+Two concepts people often mix up:
+
+1) **Chatting with a role agent directly**
+- If an agent id exists (configured under `agents.list`), you can start a chat with it directly via UI/CLI.
+
+2) **Asking one agent (usually `main`) to wake/spawn/ping another agent**
+- This uses sub-agent/session tooling, and is gated by the requester’s allowlist.
+
+### Why the lead sometimes “never picks it up”
+Even if `openclaw recipes dispatch` created an inbox entry + backlog ticket, the lead won’t act unless:
+- a human opens the lead agent/chat, **or**
+- an automation loop runs (cron triage), **or**
+- `main` is allowed to message/spawn the lead agent.
+
+### Allowlisting other agents (subagents.allowAgents)
+To allow `main` to target team role agents (like `development-team-lead`), add this to your OpenClaw config:
+
+```json5
+{
+  agents: {
+    list: [
+      {
+        id: "main",
+        subagents: {
+          allowAgents: ["development-team-lead"], // or ["*"] for any configured agent
+        },
+      },
+    ],
+  },
+}
+```
+
+Then restart the gateway.
+
+Tip: use the `agents_list` tool to see what’s currently allowed.
+
 ## Dispatcher command
 The lead can convert a natural-language request into artifacts with:
 

package/index.ts

@@ -1330,7 +1330,7 @@ const recipesPlugin = {
 
             const inboxMd = `# Inbox — ${teamId}\n\nReceived: ${receivedIso}\n\n## Request\n${requestText}\n\n## Proposed work\n- Ticket: ${ticketNumStr}-${baseSlug}\n- Owner: ${owner}\n\n## Links\n- Ticket: ${path.relative(teamDir, ticketPath)}\n- Assignment: ${path.relative(teamDir, assignmentPath)}\n`;
 
-            const ticketMd = `# ${ticketNumStr}-${baseSlug}\n\nCreated: ${receivedIso}\nOwner: ${owner}\nStatus: queued\nInbox: ${path.relative(teamDir, inboxPath)}\nAssignment: ${path.relative(teamDir, assignmentPath)}\n\n## Context\n${requestText}\n\n## Requirements\n- (fill in)\n\n## Acceptance criteria\n- (fill in)\n\n## Tasks\n- [ ] (fill in)\n`;
+            const ticketMd = `# ${ticketNumStr}-${baseSlug}\n\nCreated: ${receivedIso}\nOwner: ${owner}\nStatus: queued\nInbox: ${path.relative(teamDir, inboxPath)}\nAssignment: ${path.relative(teamDir, assignmentPath)}\n\n## Context\n${requestText}\n\n## Requirements\n- (fill in)\n\n## Acceptance criteria\n- (fill in)\n\n## Tasks\n- [ ] (fill in)\n\n## Comments\n- (use this section for @mentions, questions, decisions, and dated replies)\n`;
 
             const assignmentMd = `# Assignment — ${ticketNumStr}-${baseSlug}\n\nCreated: ${receivedIso}\nAssigned: ${owner}\n\n## Goal\n${title}\n\n## Ticket\n${path.relative(teamDir, ticketPath)}\n\n## Notes\n- Created by: openclaw recipes dispatch\n`;
 
@@ -1353,6 +1353,25 @@ const recipesPlugin = {
               await writeFileSafely(inboxPath, inboxMd, "createOnly");
               await writeFileSafely(ticketPath, ticketMd, "createOnly");
               await writeFileSafely(assignmentPath, assignmentMd, "createOnly");
+
+              // Best-effort nudge: enqueue a system event for the team lead session.
+              // This does not spawn the lead; it ensures that when the lead session runs next,
+              // it sees the dispatch immediately.
+              try {
+                const leadAgentId = `${teamId}-lead`;
+                api.runtime.system.enqueueSystemEvent(
+                  [
+                    `Dispatch created new intake for team: ${teamId}`,
+                    `- Inbox: ${path.relative(teamDir, inboxPath)}`,
+                    `- Backlog: ${path.relative(teamDir, ticketPath)}`,
+                    `- Assignment: ${path.relative(teamDir, assignmentPath)}`,
+                    `Action: please triage/normalize the ticket (fill Requirements/AC/tasks) and move it through the workflow.`,
+                  ].join("\n"),
+                  { sessionKey: `agent:${leadAgentId}:main` },
+                );
+              } catch {
+                // ignore: dispatch should still succeed even if system event enqueue fails
+              }
             };
 
             if (options.yes) {
@@ -2343,14 +2362,22 @@ const recipesPlugin = {
 
             const planPath = path.join(notesDir, "plan.md");
             const statusPath = path.join(notesDir, "status.md");
+            const goalsIndexPath = path.join(notesDir, "GOALS.md");
+            const goalsDir = path.join(notesDir, "goals");
+            const goalsReadmePath = path.join(goalsDir, "README.md");
             const ticketsPath = path.join(teamDir, "TICKETS.md");
 
             const planMd = `# Plan — ${teamId}\n\n- (empty)\n`;
             const statusMd = `# Status — ${teamId}\n\n- (empty)\n`;
+            const goalsIndexMd = `# Goals — ${teamId}\n\nThis folder is the canonical home for goals.\n\n## How to use\n- Create one markdown file per goal under: notes/goals/\n- Add a link here for discoverability\n\n## Goals\n- (empty)\n`;
+            const goalsReadmeMd = `# Goals folder — ${teamId}\n\nCreate one markdown file per goal in this directory.\n\nRecommended file naming:\n- short, kebab-case, no leading numbers (e.g. \`reduce-support-backlog.md\`)\n\nLink goals from:\n- notes/GOALS.md\n`;
             const ticketsMd = `# Tickets — ${teamId}\n\n## Naming\n- Backlog tickets live in work/backlog/\n- In-progress tickets live in work/in-progress/\n- Testing tickets live in work/testing/\n- Done tickets live in work/done/\n- Filename ordering is the queue: 0001-..., 0002-...\n\n## Stages\n- backlog → in-progress → testing → done\n\n## QA handoff\n- When work is ready for QA: move the ticket to \`work/testing/\` and assign to test.\n\n## Required fields\nEach ticket should include:\n- Title\n- Context\n- Requirements\n- Acceptance criteria\n- Owner (dev/devops/lead/test)\n- Status (queued/in-progress/testing/done)\n\n## Example\n\n\`\`\`md\n# 0001-example-ticket\n\nOwner: dev\nStatus: queued\n\n## Context\n...\n\n## Requirements\n- ...\n\n## Acceptance criteria\n- ...\n\`\`\`\n`;
 
+            await ensureDir(goalsDir);
             await writeFileSafely(planPath, planMd, overwrite ? "overwrite" : "createOnly");
             await writeFileSafely(statusPath, statusMd, overwrite ? "overwrite" : "createOnly");
+            await writeFileSafely(goalsIndexPath, goalsIndexMd, overwrite ? "overwrite" : "createOnly");
+            await writeFileSafely(goalsReadmePath, goalsReadmeMd, overwrite ? "overwrite" : "createOnly");
             await writeFileSafely(ticketsPath, ticketsMd, overwrite ? "overwrite" : "createOnly");
 
             const agents = recipe.agents ?? [];

package/openclaw.plugin.json

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

package/package.json

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

package/recipes/default/business-team.md

@@ -0,0 +1,174 @@
+---
+id: business-team
+name: Business Team
+version: 0.1.0
+description: A small generalist business team (ops, sales, marketing, finance, analyst) that runs execution through 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 (Business Team): triage inbox/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 (Business Team): make progress on in-progress tickets and update notes/status.md."
+    enabledByDefault: false
+requiredSkills: []
+team:
+  teamId: business-team
+agents:
+  - role: lead
+    name: Business Ops Lead
+    tools:
+      profile: "coding"
+      allow: ["group:fs", "group:web", "group:runtime"]
+      deny: ["exec"]
+  - role: ops
+    name: Operations Manager
+    tools:
+      profile: "coding"
+      allow: ["group:fs", "group:web"]
+      deny: ["exec"]
+  - role: sales
+    name: Sales / Partnerships
+    tools:
+      profile: "coding"
+      allow: ["group:fs", "group:web"]
+      deny: ["exec"]
+  - role: marketing
+    name: Marketing / Growth
+    tools:
+      profile: "coding"
+      allow: ["group:fs", "group:web"]
+      deny: ["exec"]
+  - role: finance
+    name: Finance / Bookkeeping
+    tools:
+      profile: "coding"
+      allow: ["group:fs", "group:web"]
+      deny: ["exec"]
+  - role: analyst
+    name: Business Analyst
+    tools:
+      profile: "coding"
+      allow: ["group:fs", "group:web"]
+      deny: ["exec"]
+
+templates:
+  lead.soul: |
+    # SOUL.md
+
+    You are the Business Ops Lead / Dispatcher for {{teamId}}.
+
+    Core job:
+    - Convert incoming requests into scoped tickets.
+    - Assign to the right role (ops/sales/marketing/finance/analyst).
+    - Keep priorities clear and measurable.
+    - Maintain a single source of truth in the shared workspace.
+
+  lead.agents: |
+    # AGENTS.md
+
+    Team: {{teamId}}
+    Team directory: {{teamDir}}
+
+    ## Shared workspace
+    - inbox/ — incoming requests and raw notes
+    - work/backlog/ — normalized tickets (0001-...)
+    - work/in-progress/ — active tickets
+    - work/testing/ — reviews/verification
+    - work/done/ — completed tickets + DONE notes
+    - notes/plan.md — current plan (curated)
+    - notes/status.md — current status snapshot
+    - shared-context/ — shared references + append-only outputs
+    - outbox/ — final deliverables (emails/copy/plans)
+
+    ## Role routing
+    - ops → process, vendors, internal operations, SOPs
+    - sales → outreach sequences, CRM notes, partnership drafts
+    - marketing → positioning, campaigns, landing-page copy
+    - finance → pricing, forecasts, bookkeeping checklists
+    - analyst → research, competitive scans, metrics
+
+    ## Operating rhythm
+    1) Triage inbox/ → tickets.
+    2) Keep WIP small (max 1–2 active tickets per role).
+    3) Every work session updates notes/status.md.
+
+  ops.soul: |
+    # SOUL.md
+
+    You are the Operations Manager on {{teamId}}.
+
+    You create SOPs, checklists, and lightweight processes that remove friction.
+
+  ops.agents: |
+    # AGENTS.md
+
+    Output:
+    - SOPs/checklists → shared-context/sops/
+    - Vendor notes → shared-context/vendors/
+    - Operational plans → outbox/
+
+  sales.soul: |
+    # SOUL.md
+
+    You are Sales / Partnerships on {{teamId}}.
+
+    You write outreach, qualify leads, and draft partnership terms.
+
+  sales.agents: |
+    # AGENTS.md
+
+    Output:
+    - Outreach sequences → outbox/sales/
+    - Call notes → shared-context/sales/call-notes/
+    - Partnership drafts → outbox/partnerships/
+
+  marketing.soul: |
+    # SOUL.md
+
+    You are Marketing / Growth on {{teamId}}.
+
+    You create crisp positioning, campaigns, and landing-page copy that converts.
+
+  marketing.agents: |
+    # AGENTS.md
+
+    Output:
+    - Positioning/messaging → shared-context/marketing/
+    - Campaign plans → outbox/marketing/
+    - Landing page copy → outbox/marketing/landing-pages/
+
+  finance.soul: |
+    # SOUL.md
+
+    You are Finance / Bookkeeping on {{teamId}}.
+
+    You build simple, defensible pricing and forecasts; you keep a paper trail.
+
+  finance.agents: |
+    # AGENTS.md
+
+    Output:
+    - Pricing memos → outbox/finance/
+    - Forecasts → outbox/finance/
+    - Bookkeeping checklists → shared-context/finance/
+
+  analyst.soul: |
+    # SOUL.md
+
+    You are the Business Analyst on {{teamId}}.
+
+    You turn ambiguous questions into structured analysis with clear recommendations.
+
+  analyst.agents: |
+    # AGENTS.md
+
+    Output:
+    - Research briefs → outbox/research/
+    - Metrics definitions/dashboards notes → shared-context/metrics/

package/recipes/default/clinic-team.md

@@ -0,0 +1,157 @@
+---
+id: clinic-team
+name: Clinic Team
+version: 0.1.0
+description: A small clinic operations team (intake, scheduling, billing, compliance, patient education) 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 (Clinic Team): triage inbox/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 (Clinic Team): make progress on in-progress tickets and update notes/status.md."
+    enabledByDefault: false
+requiredSkills: []
+team:
+  teamId: clinic-team
+agents:
+  - role: lead
+    name: Clinic Administrator / Lead
+    tools:
+      profile: "coding"
+      allow: ["group:fs", "group:web", "group:runtime"]
+      deny: ["exec"]
+  - role: intake
+    name: Patient Intake / Front Desk
+    tools:
+      profile: "coding"
+      allow: ["group:fs", "group:web"]
+      deny: ["exec"]
+  - role: scheduler
+    name: Scheduling Coordinator
+    tools:
+      profile: "coding"
+      allow: ["group:fs", "group:web"]
+      deny: ["exec"]
+  - role: billing
+    name: Billing & Insurance
+    tools:
+      profile: "coding"
+      allow: ["group:fs", "group:web"]
+      deny: ["exec"]
+  - role: compliance
+    name: Compliance / Privacy
+    tools:
+      profile: "coding"
+      allow: ["group:fs", "group:web"]
+      deny: ["exec"]
+  - role: educator
+    name: Patient Education Writer
+    tools:
+      profile: "coding"
+      allow: ["group:fs", "group:web"]
+      deny: ["exec"]
+
+templates:
+  lead.soul: |
+    # SOUL.md
+
+    You are the Clinic Administrator / Lead for {{teamId}}.
+
+    Core job:
+    - Turn operational needs into clear tickets.
+    - Keep patient communications accurate, simple, and consistent.
+    - Maintain compliance/privacy hygiene in documentation.
+    - Keep throughput high (reduce delays, no dropped follow-ups).
+
+  lead.agents: |
+    # AGENTS.md
+
+    Team directory: {{teamDir}}
+
+    ## Shared workspace
+    - inbox/ — requests, phone/email summaries, operational issues
+    - work/backlog/ — tickets (0001-...)
+    - work/in-progress/ — active tickets
+    - work/testing/ — review/verification
+    - work/done/ — completed work + DONE notes
+    - work/patient-education/ — handouts, FAQs, after-visit summaries
+    - work/policies/ — internal policies (privacy, scheduling, billing)
+    - notes/status.md — daily status snapshot
+    - outbox/ — final artifacts to publish/send
+
+  intake.soul: |
+    # SOUL.md
+
+    You handle patient intake for {{teamId}}.
+
+    You produce clear summaries, required info checklists, and next-step instructions.
+
+  intake.agents: |
+    # AGENTS.md
+
+    Output:
+    - Intake templates → work/policies/intake/
+    - Call/email summaries → inbox/ (append-only) then ticketization
+
+  scheduler.soul: |
+    # SOUL.md
+
+    You coordinate scheduling for {{teamId}}.
+
+    You reduce no-shows and keep schedules accurate.
+
+  scheduler.agents: |
+    # AGENTS.md
+
+    Output:
+    - Scheduling scripts/templates → work/policies/scheduling/
+    - Reminder cadences → work/policies/scheduling/reminders.md
+
+  billing.soul: |
+    # SOUL.md
+
+    You manage billing and insurance workflows for {{teamId}}.
+
+    You produce step-by-step processes and clear patient-facing explanations.
+
+  billing.agents: |
+    # AGENTS.md
+
+    Output:
+    - Billing SOPs → work/policies/billing/
+    - Patient billing FAQs → work/patient-education/billing/
+
+  compliance.soul: |
+    # SOUL.md
+
+    You oversee compliance and privacy for {{teamId}}.
+
+    You flag risks and propose compliant alternatives.
+
+  compliance.agents: |
+    # AGENTS.md
+
+    Output:
+    - Privacy/compliance checklists → work/policies/compliance/
+    - Policy updates → work/policies/
+
+  educator.soul: |
+    # SOUL.md
+
+    You write patient education materials for {{teamId}}.
+
+    You write at an accessible reading level and include practical next steps.
+
+  educator.agents: |
+    # AGENTS.md
+
+    Output:
+    - Handouts/FAQs → work/patient-education/
+    - After-visit summaries → work/patient-education/after-visit/