@jiggai/recipes 0.2.11

package/docs/shared-context.md

@@ -0,0 +1,47 @@
+# Shared context conventions (team workspaces)
+
+This is a **file-first** coordination convention for scaffolded teams.
+
+## Goals
+- Reduce cross-agent messaging; coordinate via shared files.
+- Prevent shared context from becoming a junk drawer.
+- Make work auditable: read → act → write loops.
+
+## Directory layout
+Team workspaces include:
+
+- `notes/plan.md` — curated plan / priorities (lead-owned)
+- `notes/status.md` — current snapshot (short, updated frequently)
+- `shared-context/` — shared context + append-only inputs
+  - `priorities.md` — curated priorities (lead-owned)
+  - `agent-outputs/` — append-only outputs from non-lead roles
+  - `feedback/` — QA findings / feedback
+  - `kpis/` — metrics
+  - `calendar/` — optional notes
+
+Back-compat:
+- `shared/` may exist as a legacy folder. Prefer `shared-context/`.
+
+## Curator model
+- **Lead** curates:
+  - `notes/plan.md`
+  - `shared-context/priorities.md`
+- **Non-lead roles** should not edit curated files.
+  - Append instead to `shared-context/agent-outputs/` (or `feedback/`).
+
+## Read → Act → Write
+Every role should:
+1) **Read** plan/status + ticket before acting
+2) **Act** (small, safe changes)
+3) **Write back**
+   - update ticket
+   - add 3–5 bullets to `notes/status.md`
+   - append detailed outputs to `shared-context/agent-outputs/`
+
+## Migration guidance (existing teams)
+Safe migration:
+1) Create `shared-context/` and starter subdirs.
+2) Add `shared-context/priorities.md` (create-only; do not overwrite).
+3) Update agent instructions to reference shared-context and curator model.
+
+No existing files need to be deleted or renamed.

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

@@ -0,0 +1,65 @@
+# Verify built-in team recipes (scaffold + cron jobs)
+
+This checklist verifies that each built-in **team** recipe scaffolds correctly and that any recipe-defined cron jobs reconcile safely.
+
+## Prereqs
+- You have OpenClaw installed and `openclaw` is on PATH.
+- Set recipes cron installation behavior in config (safe default is `prompt`).
+  - `cronInstallation: prompt` ⇒ asks before installing cron jobs
+  - `cronInstallation: on` ⇒ installs cron jobs (enabled state still depends on `enabledByDefault`)
+  - `cronInstallation: off` ⇒ skips cron reconciliation
+
+## Teams to verify
+- product-team
+- research-team
+- writing-team
+- social-team
+- customer-support-team
+- development-team
+
+## Commands
+
+### Scaffold each team
+
+> Note: `--team-id` must end with `-team`.
+
+For each recipe id `<rid>` above:
+
+```bash
+openclaw recipes scaffold-team <rid> --team-id <rid>-team --apply-config
+```
+
+### Verify scaffold output
+
+For each `~/.openclaw/workspace-<rid>-team/` ensure:
+- `notes/plan.md` exists
+- `notes/status.md` exists
+- `shared-context/priorities.md` exists
+- `shared-context/agent-outputs/` exists
+- `work/backlog/`, `work/in-progress/`, `work/testing/`, `work/done/` exist
+
+### Verify cron reconciliation behavior
+
+1) With `cronInstallation: prompt`:
+   - Re-run scaffold-team and confirm you are prompted.
+   - Answer **No** and verify that installed jobs are created **disabled** (or not created, depending on implementation).
+
+2) With `cronInstallation: on`:
+   - Re-run scaffold-team and verify recipe cron jobs are installed.
+
+3) Confirm jobs are listed:
+
+```bash
+openclaw cron list
+```
+
+4) Optionally force-run a job:
+
+```bash
+openclaw cron run <jobId>
+```
+
+## What to record
+- Any recipe that fails to scaffold
+- Any cron job install/update errors
+- Any cron job that runs but fails (include logs / error output)