@clawcipes/recipes 0.2.7 → 0.2.8

package/README.md

@@ -1,28 +1,35 @@
-# Clawcipes (OpenClaw Recipes Plugin)
+# Clawcipes (OpenClaw Recipes Plugin) — DEPRECATED
+
+> This package is deprecated. Use **@jiggai/clawrecipes** instead.
 
 <p align="center">
-  <img src="./clawcipes_cook.jpg" alt="Clawcipes logo" width="240" />
+  <img src="./clawrecipes_cook.jpg" alt="ClawRecipes logo" width="240" />
 </p>
 
-Clawcipes is an OpenClaw plugin that provides **CLI-first recipes** for scaffolding specialist agents and teams from Markdown.
+ClawRecipes is an OpenClaw plugin that provides **CLI-first recipes** for scaffolding specialist agents and teams from Markdown.
 
-If you like durable workflows: Clawcipes is built around a **file-first team workspace** (inbox/backlog/in-progress/testing/done) that plays nicely with git.
+If you like durable workflows: ClawRecipes is built around a **file-first team workspace** (inbox/backlog/in-progress/testing/done) that plays nicely with git.
 
 ## Quickstart
 ### 1) Install
 #### Option A (preferred): install from npm
-Once published:
 
 ```bash
-openclaw plugins install @clawcipes/recipes
+openclaw plugins install @jiggai/clawrecipes
 openclaw gateway restart
 openclaw plugins list
 ```
 
+#### Deprecated (do not use): install Clawcipes package
+```bash
+openclaw plugins install @clawcipes/recipes
+openclaw gateway restart
+```
+
 #### Option B: install from GitHub
 ```bash
-git clone https://github.com/rjdjohnston/clawcipes.git ~/clawcipes
-openclaw plugins install --link ~/clawcipes
+git clone https://github.com/JIGGAI/ClawRecipes.git ~/clawrecipes
+openclaw plugins install --link ~/clawrecipes
 openclaw gateway restart
 openclaw plugins list
 ```
@@ -35,7 +42,7 @@ openclaw recipes list
 ### 3) Scaffold a team
 ```bash
 openclaw recipes scaffold-team development-team \
-  --team-id development-team \
+  --team-id development-team-team \
   --overwrite \
   --apply-config
 ```
@@ -43,7 +50,7 @@ openclaw recipes scaffold-team development-team \
 ### 4) Dispatch a request into work artifacts
 ```bash
 openclaw recipes dispatch \
-  --team-id development-team \
+  --team-id development-team-team \
   --request "Add a new recipe for a customer-support team" \
   --owner lead
 ```
@@ -68,6 +75,7 @@ The plugin supports these config keys (with defaults):
 - `workspaceTeamsDir` (default: `teams`)
 - `autoInstallMissingSkills` (default: `false`)
 - `confirmAutoInstall` (default: `true`)
+- `cronInstallation` (default: `prompt`; values: `off|prompt|on`)
 
 Config schema is defined in `openclaw.plugin.json`.
 
@@ -97,9 +105,9 @@ Reference:
 - Recipe format: `docs/RECIPE_FORMAT.md`
 - Bundled recipes: `docs/BUNDLED_RECIPES.md`
 - Team workflow: `docs/TEAM_WORKFLOW.md`
-- Clawcipes Kitchen (UI): `docs/CLAWCIPES_KITCHEN.md`
+- ClawRecipes Kitchen (UI): `docs/CLAWCIPES_KITCHEN.md`
 
-(Also see: GitHub repo https://github.com/rjdjohnston/clawcipes)
+(Also see: GitHub repo https://github.com/JIGGAI/ClawRecipes)
 ## Notes / principles
 - Workspaces:
   - Standalone agents: `~/.openclaw/workspace-<agentId>/`
@@ -111,25 +119,21 @@ Reference:
 - Recipe template rendering is intentionally simple: `{{var}}` replacement only.
 
 ## Removing (uninstalling) a scaffolded team
-Clawcipes does not (yet) include a first-class `remove-team` command.
+ClawRecipes includes a safe uninstall command:
 
-To remove a scaffolded team created with `scaffold-team --apply-config`, do two things:
-
-1) Remove the team workspace (recommended: send to trash):
-```bash
-trash ~/.openclaw/workspace-<teamId>
-```
-
-2) Remove the agents from OpenClaw config:
-- Edit `~/.openclaw/openclaw.json`
-- Delete the matching entries under `agents.list[]` whose `id` starts with `<teamId>-`
-- Restart:
 ```bash
+openclaw recipes remove-team --team-id <teamId> --plan --json
+openclaw recipes remove-team --team-id <teamId> --yes
 openclaw gateway restart
 ```
 
+Notes:
+- The command is confirmation-gated by default (use `--yes` to apply).
+- Cron cleanup is conservative: it removes only cron jobs that are explicitly **stamped** with `recipes.teamId=<teamId>`.
+- If you need a manual fallback, you can still delete `~/.openclaw/workspace-<teamId>` and remove `<teamId>-*` agents from `agents.list[]` in `~/.openclaw/openclaw.json`.
+
 ## Links
-- GitHub: https://github.com/rjdjohnston/clawcipes
+- GitHub: https://github.com/JIGGAI/ClawRecipes
 - Docs:
   - Installation: `docs/INSTALLATION.md`
   - Commands: `docs/COMMANDS.md`
@@ -137,7 +141,7 @@ openclaw gateway restart
   - Team workflow: `docs/TEAM_WORKFLOW.md`
 
 ## What you should be developing (not this plugin)
-Clawcipes is meant to be *installed* and then used to build **agents + teams**.
+ClawRecipes is meant to be *installed* and then used to build **agents + teams**.
 
 Most users should focus on:
 - authoring recipes in their OpenClaw workspace (`<workspace>/recipes/*.md`)

package/docs/AGENTS_AND_SKILLS.md

@@ -1,6 +1,6 @@
-# Agents and skills (OpenClaw + Clawcipes)
+# Agents and skills (OpenClaw + ClawRecipes)
 
-This doc explains the mental model: **what an agent is**, how **skills/tools** work, and how Clawcipes helps you build agents + teams.
+This doc explains the mental model: **what an agent is**, how **skills/tools** work, and how ClawRecipes helps you build agents + teams.
 
 ## What is an agent?
 In OpenClaw, an **agent** is a configured assistant persona with:
@@ -9,7 +9,7 @@ In OpenClaw, an **agent** is a configured assistant persona with:
 - a **tool policy** (what tools it is allowed to use)
 - a **model** configuration (defaults come from OpenClaw)
 
-In Clawcipes, a **standalone** agent recipe scaffolds a dedicated workspace like:
+In ClawRecipes, a **standalone** agent recipe scaffolds a dedicated workspace like:
 
 ```
 ~/.openclaw/workspace-<agentId>/
@@ -38,7 +38,7 @@ In OpenClaw, skills are surfaced as tools the agent can use.
 ## Tool policies (allow/deny)
 Every agent can have a tool policy in OpenClaw config (written via `--apply-config` when scaffolding).
 
-Clawcipes recipes commonly use:
+ClawRecipes recipes commonly use:
 - `allow: ["group:fs", "group:web"]` for safe file + web access
 - `allow: ["group:runtime"]` when the agent needs to run local commands
 - `allow: ["group:automation"]` for automation-oriented tools
@@ -84,7 +84,7 @@ openclaw gateway restart
 > Tip: if you later re-run scaffold with `--apply-config`, the recipe’s tool policy may overwrite your manual edits. If you want a change to stick, encode it in the recipe.
 
 ## Installing skills (workspace-local)
-Clawcipes favors **workspace-local** installs so each OpenClaw workspace is self-contained.
+ClawRecipes favors **workspace-local** installs so each OpenClaw workspace is self-contained.
 
 ### Install a skill slug
 ```bash
@@ -112,7 +112,7 @@ openclaw recipes install <recipe-id>
 That installs the recipe’s declared skills.
 
 ### Removing a skill
-Clawcipes currently does **not** implement a remove command.
+ClawRecipes currently does **not** implement a remove command.
 
 To remove a workspace-local skill:
 - delete the folder: `<workspace>/skills/<skill-slug>`
@@ -121,23 +121,18 @@ To remove a workspace-local skill:
 (We can add `openclaw recipes uninstall <slug>` later if you want it to be first-class.)
 
 ## Removing (uninstalling) a scaffolded team
-Clawcipes does not (yet) include a first-class `remove-team` command.
+ClawRecipes includes a safe uninstall command:
 
-If you scaffolded a team with `scaffold-team --apply-config`, removal has two parts:
-
-1) Remove the team workspace (recommended: send to trash):
-```bash
-trash ~/.openclaw/workspace-<teamId>
-```
-
-2) Remove the agents from OpenClaw config:
-- Edit `~/.openclaw/openclaw.json`
-- Delete the matching entries under `agents.list[]` whose `id` starts with `<teamId>-`
-- Restart:
 ```bash
+openclaw recipes remove-team --team-id <teamId> --plan --json
+openclaw recipes remove-team --team-id <teamId> --yes
 openclaw gateway restart
 ```
 
+Notes:
+- Cron cleanup is conservative: it removes only cron jobs explicitly stamped with `recipes.teamId=<teamId>`.
+- You can still do it manually by deleting `~/.openclaw/workspace-<teamId>` and removing `<teamId>-*` entries from `agents.list[]` in `~/.openclaw/openclaw.json`.
+
 ## Teams: shared workspace + multiple agents
 A **team** recipe scaffolds a **shared workspace root** plus role folders:
 
@@ -197,7 +192,7 @@ openclaw recipes scaffold-team <recipeId> --team-id <teamId> --overwrite
 ```
 
 ### 2) The agent’s OpenClaw config (tool permissions, identity, model)
-When you scaffold with `--apply-config`, Clawcipes writes the agent entry into OpenClaw config:
+When you scaffold with `--apply-config`, ClawRecipes writes the agent entry into OpenClaw config:
 - `~/.openclaw/openclaw.json` → `agents.list[]`
 
 Re-run scaffold/scaffold-team with `--apply-config` any time you want the recipe’s tool policy (allow/deny) to be re-applied.

package/docs/BUNDLED_RECIPES.md

@@ -1,6 +1,6 @@
 # Bundled recipes
 
-Clawcipes ships with a few recipes in `recipes/default/`.
+ClawRecipes ships with a few recipes in `recipes/default/`.
 
 You can:
 - list them: `openclaw recipes list`

package/docs/CLAWCIPES_KITCHEN.md

@@ -1,6 +1,6 @@
-# Clawcipes Kitchen (UI)
+# ClawRecipes Kitchen (UI)
 
-Clawcipes Kitchen is our UI for managing Clawcipes workflows.
+ClawRecipes Kitchen is our UI for managing ClawRecipes workflows.
 
 ## What it’s for
 - Activity feed (high-level semantic events)
@@ -11,11 +11,11 @@ Clawcipes Kitchen is our UI for managing Clawcipes workflows.
 - Approvals inbox + routing (e.g., Telegram)
 
 ## Status
-Clawcipes Kitchen is under active development.
+ClawRecipes Kitchen is under active development.
 
 ## Relationship to the plugin
-- The **Clawcipes plugin** is CLI-first and works without any UI.
-- Clawcipes Kitchen is an optional UI companion for:
+- The **ClawRecipes plugin** is CLI-first and works without any UI.
+- ClawRecipes Kitchen is an optional UI companion for:
   - visibility (activity/search)
   - approvals
   - human review of plans and changes

package/docs/INSTALLATION.md

@@ -14,22 +14,22 @@ This repo is an **OpenClaw plugin** (not a standalone CLI). OpenClaw loads it an
 Once published, you can install directly via npm:
 
 ```bash
-openclaw plugins install @clawcipes/recipes
+openclaw plugins install @jiggai/clawrecipes
 openclaw gateway restart
 openclaw plugins list
 ```
 
 ### Option B: install from GitHub
 ```bash
-git clone https://github.com/rjdjohnston/clawcipes.git ~/clawcipes
-openclaw plugins install --link ~/clawcipes
+git clone https://github.com/JIGGAI/ClawRecipes.git ~/clawrecipes
+openclaw plugins install --link ~/clawrecipes
 openclaw gateway restart
 openclaw plugins list
 ```
 
 ### Option B: already cloned
 ```bash
-openclaw plugins install --link ~/clawcipes
+openclaw plugins install --link ~/clawrecipes
 openclaw gateway restart
 openclaw plugins list
 ```
@@ -49,7 +49,7 @@ openclaw recipes list
 If you pull a newer version from GitHub, restart the gateway so OpenClaw reloads the plugin:
 
 ```bash
-cd ~/clawcipes
+cd ~/clawrecipes
 git pull
 openclaw gateway restart
 ```

package/docs/RECIPE_FORMAT.md

@@ -83,7 +83,7 @@ agents:
 For team recipes, file templates are namespaced by role:
 - `lead.soul`, `dev.soul`, etc.
 
-If a `files[].template` key does not contain a `.`, Clawcipes prefixes it with `<role>.`.
+If a `files[].template` key does not contain a `.`, ClawRecipes prefixes it with `<role>.`.
 
 ## Cron jobs (optional)
 Recipes can optionally declare cron jobs to be reconciled during `scaffold` / `scaffold-team`.

package/docs/TEAM_WORKFLOW.md

@@ -1,6 +1,6 @@
 # Team workflow (file-first)
 
-Clawcipes’ differentiator is the **shared team workspace** + a simple, durable, file-first workflow.
+ClawRecipes’ differentiator is the **shared team workspace** + a simple, durable, file-first workflow.
 
 ## Team workspace structure
 When you scaffold a team:
@@ -34,7 +34,10 @@ When you scaffold a team:
 
 4) **Test**
 - Move ticket to `work/testing/`.
-- Optionally assign to a tester/lead for verification.
+- 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**
 - Move ticket to `work/done/` (or use `complete`).

package/docs/TUTORIAL_CREATE_RECIPE.md

@@ -8,7 +8,7 @@ You’ll learn:
 - how templates/files are written
 - how to scaffold a team and run the file-first workflow
 
-## Step 0 — confirm Clawcipes is installed
+## Step 0 — confirm ClawRecipes is installed
 ```bash
 openclaw plugins list
 openclaw recipes list
@@ -80,7 +80,9 @@ templates:
     How you work:
     - Pick the lowest numbered ticket assigned to you.
     - Move it to `work/in-progress/`.
-    - Complete it and write a report in `work/done/`.
+    - Do the work.
+    - When ready for QA, move it to `work/testing/` and assign Owner to `test`.
+    - After QA passes, move it to `work/done/` and write a short completion report.
 
 files:
   - path: SOUL.md
@@ -110,9 +112,9 @@ openclaw recipes scaffold-team my-first-team --team-id my-first-team-team --appl
 ```
 
 You should now have:
-- `~/.openclaw/workspace/teams/my-first-team-team/`
-- `~/.openclaw/workspace/agents/my-first-team-team-lead/`
-- `~/.openclaw/workspace/agents/my-first-team-team-worker/`
+- `~/.openclaw/workspace-my-first-team-team/` (team shared workspace)
+- `~/.openclaw/workspace-my-first-team-team/roles/lead/`
+- `~/.openclaw/workspace-my-first-team-team/roles/worker/`
 
 ## Step 3 — dispatch a request
 ```bash
@@ -128,9 +130,16 @@ This will propose (or write, with `--yes`) three artifacts:
 - an assignment stub
 
 ## Step 4 — run the workflow
+Tickets move through lanes:
+- `work/backlog/` → `work/in-progress/` → `work/testing/` → `work/done/`
+
 - Move the ticket from `work/backlog/` → `work/in-progress/`
 - Do the work
-- Move the ticket to `work/done/` and add a `*.DONE.md` report
+- When ready for QA:
+  - Move the ticket to `work/testing/`
+  - Set `Owner: test` and add **Verification steps** to the ticket
+- After verification:
+  - Move the ticket to `work/done/` and add a short completion report
 
 ## Common mistakes
 - **Forgetting the `-team` suffix** on `--team-id` (required).