@jiggai/recipes 0.4.17 → 0.4.18

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

@@ -1,524 +0,0 @@
----
-id: law-firm-team
-name: Law Firm Team
-version: 0.1.0
-description: A legal practice team (intake, research, drafting, compliance, 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 (Law Firm): triage intake/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 (Law Firm): make progress on in-progress matters and update notes/status.md."
-    enabledByDefault: false
-requiredSkills: []
-team:
-  teamId: law-firm-team
-agents:
-  - role: lead
-    name: Managing Attorney / Lead
-    tools:
-      profile: "coding"
-      allow: ["group:fs", "group:web", "group:runtime"]
-      deny: ["exec"]
-  - role: intake
-    name: Client Intake / Paralegal
-    tools:
-      profile: "coding"
-      allow: ["group:fs", "group:web"]
-      deny: ["exec"]
-  - role: researcher
-    name: Legal Researcher
-    tools:
-      profile: "coding"
-      allow: ["group:fs", "group:web"]
-      deny: ["exec"]
-  - role: drafter
-    name: Briefs & Contracts Drafter
-    tools:
-      profile: "coding"
-      allow: ["group:fs", "group:web"]
-      deny: ["exec"]
-  - role: compliance
-    name: Compliance / Risk
-    tools:
-      profile: "coding"
-      allow: ["group:fs", "group:web"]
-      deny: ["exec"]
-  - role: ops
-    name: Practice Ops
-    tools:
-      profile: "coding"
-      allow: ["group:fs", "group:web"]
-      deny: ["exec"]
-
-templates:
-  sharedContext.memoryPolicy: |
-    # Team Memory Policy (File-first)
-
-    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 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).
-    - `shared-context/agent-outputs/` is **append-only** logs/output.
-
-    ## End-of-session checklist (everyone)
-    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`.
-    4) Append logs/output to `shared-context/agent-outputs/`.
-
-  sharedContext.plan: |
-    # Plan (lead-curated)
-
-    - (empty)
-
-  sharedContext.status: |
-    # Status (append-only)
-
-    - (empty)
-
-  sharedContext.memoryPlan: |
-    # Memory Plan (Team)
-
-    This team is file-first. Chat is not the system of record.
-
-    ## Source of truth
-    - Tickets (`work/*/*.md`) are the source of truth for a unit of work.
-
-    ## Team knowledge memory (Kitchen UI)
-    - `shared-context/memory/team.jsonl` (append-only)
-    - `shared-context/memory/pinned.jsonl` (append-only, curated/high-signal)
-
-    Policy:
-    - Lead may pin to `pinned.jsonl`.
-    - Non-leads propose memory items via ticket comments or role outputs; lead pins.
-
-    ## Per-role continuity memory (agent startup)
-    - `roles/<role>/MEMORY.md` (curated long-term)
-    - `roles/<role>/memory/YYYY-MM-DD.md` (daily log)
-
-    ## Plan vs status (team coordination)
-    - `notes/plan.md` + `shared-context/priorities.md` are lead-curated
-    - `notes/status.md` is append-only roll-up (everyone appends)
-
-    ## Outputs / artifacts
-    - `roles/<role>/agent-outputs/` (append-only)
-    - `shared-context/agent-outputs/` (optional team-level)
-
-    ## Role work loop contract (safe-idle)
-    - 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/`.
-
-  sharedContext.priorities: |
-    # Priorities (lead-curated)
-
-    - (empty)
-
-  sharedContext.agentOutputsReadme: |
-    # Agent Outputs (append-only)
-
-    Put raw logs, command output, and investigation notes here.
-    Prefer filenames like: `YYYY-MM-DD-topic.md`.
-
-  lead.tools: |
-    # TOOLS.md
-
-    # Agent-local notes (paths, conventions, env quirks).
-
-  tools: |
-    # TOOLS.md
-
-    # Agent-local notes (paths, conventions, env quirks).
-
-  status: |
-    # STATUS.md
-
-    - (empty)
-
-  notes: |
-    # NOTES.md
-
-    - (empty)
-
-  lead.soul: |
-    # SOUL.md
-
-    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/`.
-  intake.soul: |
-    # SOUL.md
-
-    You run client intake for {{teamId}}.
-
-    You turn messy narratives into structured fact patterns and issue lists.
-
-  intake.agents: |
-    # AGENTS.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
-
-    You are the Legal Researcher on {{teamId}}.
-
-    You find controlling authority and summarize it accurately.
-
-  researcher.agents: |
-    # AGENTS.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
-
-    You draft briefs, motions, contracts, and letters for {{teamId}}.
-
-    You write clean, consistent documents that match the client’s goals and constraints.
-
-  drafter.agents: |
-    # AGENTS.md
-
-    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
-
-    You focus on compliance and risk for {{teamId}}.
-
-    You identify obligations, conflicts, and failure modes; you propose mitigations.
-
-  compliance.agents: |
-    # AGENTS.md
-
-    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
-
-    You run practice operations for {{teamId}}.
-
-    You keep matters organized and deadlines visible.
-
-  ops.agents: |
-    # AGENTS.md
-
-    Output:
-    - Matter indexes → work/matters/<matter>/INDEX.md
-    - Deadline trackers → notes/status.md updates
-    - Templates/playbooks → shared-context/playbooks/
-
-
-
-  # Auto-added blanks to ensure every role can scaffold every declared file.
-
-  # --- role: lead ---
-  lead.status: |
-    # STATUS.md
-    
-    - (empty)
-
-  lead.notes: |
-    # NOTES.md
-    
-    - (empty)
-
-
-  # --- role: intake ---
-  intake.tools: |
-    # TOOLS.md
-    
-    - (empty)
-
-  intake.status: |
-    # STATUS.md
-    
-    - (empty)
-
-  intake.notes: |
-    # NOTES.md
-    
-    - (empty)
-
-
-  # --- role: researcher ---
-  researcher.tools: |
-    # TOOLS.md
-    
-    - (empty)
-
-  researcher.status: |
-    # STATUS.md
-    
-    - (empty)
-
-  researcher.notes: |
-    # NOTES.md
-    
-    - (empty)
-
-
-  # --- role: drafter ---
-  drafter.tools: |
-    # TOOLS.md
-    
-    - (empty)
-
-  drafter.status: |
-    # STATUS.md
-    
-    - (empty)
-
-  drafter.notes: |
-    # NOTES.md
-    
-    - (empty)
-
-
-  # --- role: compliance ---
-  compliance.tools: |
-    # TOOLS.md
-    
-    - (empty)
-
-  compliance.status: |
-    # STATUS.md
-    
-    - (empty)
-
-  compliance.notes: |
-    # NOTES.md
-    
-    - (empty)
-
-
-  # --- role: ops ---
-  ops.tools: |
-    # TOOLS.md
-    
-    - (empty)
-
-  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
-
-
-  # Memory / continuity (team-level)
-  - path: notes/memory-policy.md
-    template: sharedContext.memoryPolicy
-    mode: createOnly
-  - path: notes/plan.md
-    template: sharedContext.plan
-    mode: createOnly
-  - path: notes/status.md
-    template: sharedContext.status
-    mode: createOnly
-  - path: shared-context/priorities.md
-    template: sharedContext.priorities
-    mode: createOnly
-  - path: shared-context/agent-outputs/README.md
-    template: sharedContext.agentOutputsReadme
-    mode: createOnly
-
-
-tools:
-  profile: "messaging"
-  allow: ["group:fs", "group:web"]
-  deny: ["exec"]
----
-
-# 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.
-