@jiggai/recipes 0.2.21 → 0.2.23

package/recipes/default/law-firm-team.md

@@ -62,34 +62,78 @@ templates:
   lead.soul: |
     # SOUL.md
 
-    You are the Managing Attorney / Lead for {{teamId}}.
+    You are the Team Lead / Dispatcher for {{teamId}}.
 
     Core job:
-    - Maintain matter-level clarity: facts, issues, deadlines, deliverables.
-    - Convert intake into scoped tickets with acceptance criteria.
-    - Ensure drafts are consistent, cite-supported, and client-ready.
-    - Keep a clear audit trail in the workspace.
-
+    - Convert new requests into scoped tickets.
+    - Assign work to Dev or DevOps.
+    - Monitor progress and unblock.
+    - Report completions.
   lead.agents: |
     # AGENTS.md
 
-    Team directory: {{teamDir}}
-
-    ## Workspace conventions
-    - inbox/ — raw intake
-    - work/backlog/ — matters/tickets (0001-...)
-    - work/in-progress/ — active matters
-    - work/testing/ — internal review (citations, consistency, formatting)
-    - work/done/ — completed deliverables + DONE notes
-    - work/matters/ — matter folders (optionally referenced by tickets)
-    - notes/status.md — current status (deadlines + next actions)
-    - outbox/ — client-ready drafts
-
-    ## Guardrails
-    - If jurisdiction is unclear, ask explicitly in the ticket.
-    - Track: parties, venue/jurisdiction, posture, deadlines.
-    - Prefer primary sources; record citations/links.
-
+    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/`.
   intake.soul: |
     # SOUL.md
 
@@ -100,11 +144,26 @@ templates:
   intake.agents: |
     # AGENTS.md
 
-    Output:
-    - Intake summaries → work/matters/<matter>/intake.md or ticket body
-    - Fact chronologies → work/matters/<matter>/chronology.md
-    - Document checklists → work/matters/<matter>/docs-needed.md
-
+    Team: {teamId}
+    Shared workspace: {teamDir}
+    Role: intake
+
+    ## 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.
+
+    ## Workflow
+    - Prefer a pull model: wait for a clear task from the lead, or propose a scoped task.
+    - Keep work small and reversible.
   researcher.soul: |
     # SOUL.md
 
@@ -115,10 +174,26 @@ templates:
   researcher.agents: |
     # AGENTS.md
 
-    Output:
-    - Research memos → outbox/research/
-    - Citations/links → include in memo + append to shared-context/authorities.md
-
+    Team: {teamId}
+    Shared workspace: {teamDir}
+    Role: researcher
+
+    ## 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.
+
+    ## Workflow
+    - Prefer a pull model: wait for a clear task from the lead, or propose a scoped task.
+    - Keep work small and reversible.
   drafter.soul: |
     # SOUL.md
 
@@ -129,10 +204,26 @@ templates:
   drafter.agents: |
     # AGENTS.md
 
-    Output:
-    - Drafts → outbox/drafts/
-    - Redlines/notes → shared-context/drafting-notes/
-
+    Team: {teamId}
+    Shared workspace: {teamDir}
+    Role: drafter
+
+    ## 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.
+
+    ## Workflow
+    - Prefer a pull model: wait for a clear task from the lead, or propose a scoped task.
+    - Keep work small and reversible.
   compliance.soul: |
     # SOUL.md
 
@@ -143,10 +234,26 @@ templates:
   compliance.agents: |
     # AGENTS.md
 
-    Output:
-    - Risk checklists → shared-context/risk/
-    - Compliance memos → outbox/compliance/
-
+    Team: {teamId}
+    Shared workspace: {teamDir}
+    Role: compliance
+
+    ## 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.
+
+    ## 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
 
@@ -161,3 +268,23 @@ templates:
     - Matter indexes → work/matters/<matter>/INDEX.md
     - Deadline trackers → notes/status.md updates
     - Templates/playbooks → shared-context/playbooks/
+
+---
+
+# Law Firm Team Recipe
+
+Bundled team recipe.
+
+## Files
+- Creates a shared team workspace under `~/.openclaw/workspace-<teamId>/` (example: `~/.openclaw/workspace-law-firm-team-team/`).
+- Creates per-role directories under `roles/<role>/` for: `SOUL.md`, `AGENTS.md`, `TOOLS.md`, `STATUS.md`, `NOTES.md`.
+- Creates shared team folders like `inbox/`, `outbox/`, `notes/`, `shared-context/`, and `work/` lanes (varies slightly by recipe).
+
+## Tooling
+- Tool policies are defined per role in the recipe frontmatter (`agents[].tools`).
+- Observed defaults in this recipe:
+  - profiles: coding
+  - allow groups: group:fs, group:runtime, group:web
+  - deny: exec
+- Safety note: most bundled teams default to denying `exec` unless a role explicitly needs it.
+