@clawcipes/recipes 0.2.4 → 0.2.6

package/README.md

@@ -4,8 +4,6 @@
   <img src="./clawcipes_cook.jpg" alt="Clawcipes logo" width="240" />
 </p>
 
-> **Experimental:** We’re in active development. Installing should not have any negative impacts, but it’s always good to be safe and copy your `~/.openclaw` folder to a backup.
-
 Clawcipes 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.
@@ -57,7 +55,8 @@ openclaw recipes dispatch \
 - `openclaw recipes install <idOrSlug> [--yes] [--global|--agent-id <id>|--team-id <id>]` (skills: global or scoped)
 - `openclaw recipes bind|unbind|bindings` (multi-agent routing)
 - `openclaw recipes dispatch ...` (request → inbox + ticket + assignment)
-- `openclaw recipes tickets|move-ticket|assign|take|complete` (file-first ticket workflow)
+- `openclaw recipes tickets|move-ticket|assign|take|handoff|complete` (file-first ticket workflow)
+- `openclaw recipes cleanup-workspaces` (safe cleanup of temporary test/scaffold workspaces)
 
 For full details, see `docs/COMMANDS.md`.
 
@@ -78,6 +77,21 @@ Start here:
 - Agents + skills: `docs/AGENTS_AND_SKILLS.md`
 - Tutorial (create a recipe): `docs/TUTORIAL_CREATE_RECIPE.md`
 
+## Development
+### Unit tests (vitest)
+Run:
+- `npm test`
+
+### Scaffold smoke test (regression)
+A lightweight smoke check validates scaffold-team output contains the required testing workflow docs (ticket 0004).
+
+Run:
+- `npm run test:smoke` (or `npm run scaffold:smoke`)
+
+Notes:
+- Creates a temporary `workspace-smoke-<timestamp>-team` under `~/.openclaw/` and then deletes it.
+- Exits non-zero on mismatch.
+
 Reference:
 - Commands: `docs/COMMANDS.md`
 - Recipe format: `docs/RECIPE_FORMAT.md`

package/docs/AGENTS_AND_SKILLS.md

@@ -151,6 +151,7 @@ A **team** recipe scaffolds a **shared workspace root** plus role folders:
   work/
     backlog/
     in-progress/
+    testing/
     done/
     assignments/
   roles/
@@ -162,7 +163,7 @@ Each role agent is a separate OpenClaw agent id (`<teamId>-<role>`), but they sh
 
 The shared workspace is the source of truth for:
 - intake (`inbox/`)
-- work queue (`work/backlog`, `work/in-progress`, `work/done`)
+- work queue (`work/backlog`, `work/in-progress`, `work/testing`, `work/done`)
 - assignments (`work/assignments`)
 - deliverables (`outbox/`)
 

package/docs/CLAWCIPES_KITCHEN.md

@@ -23,5 +23,5 @@ Clawcipes Kitchen is under active development.
 ## Roadmap (high level)
 - Approvals UI (approve/deny + audit trail)
 - Recipe browser and scaffold flows
-- Team dashboards (backlog/in-progress/done)
+- Team dashboards (backlog/in-progress/testing/done)
 - Publishing workflow integration

package/docs/COMMANDS.md

@@ -165,6 +165,31 @@ openclaw recipes tickets --team-id <teamId>
 openclaw recipes tickets --team-id <teamId> --json
 ```
 
+## `cleanup-workspaces`
+List (dry-run, default) or delete (with `--yes`) temporary test/scaffold team workspaces under your OpenClaw home directory.
+
+Safety rails:
+- Only considers `workspace-<teamId>` directories where `<teamId>`:
+  - ends with `-team`
+  - starts with an allowed prefix (default: `smoke-`, `qa-`, `tmp-`, `test-`)
+- Refuses symlinks
+- Protected teams (at minimum: `development-team`) are never deleted
+
+Examples:
+```bash
+# Dry-run (default): list what would be deleted
+openclaw recipes cleanup-workspaces
+
+# Actually delete eligible workspaces
+openclaw recipes cleanup-workspaces --yes
+
+# Custom prefixes (repeatable)
+openclaw recipes cleanup-workspaces --prefix smoke- --prefix qa- --yes
+
+# JSON output
+openclaw recipes cleanup-workspaces --json
+```
+
 ## `move-ticket`
 Move a ticket file between workflow stages and update the ticket’s `Status:` field.
 
@@ -188,7 +213,7 @@ openclaw recipes assign --team-id <teamId> --ticket 0007 --owner dev
 openclaw recipes assign --team-id <teamId> --ticket 0007 --owner lead
 ```
 
-Owners (current): `dev|devops|lead`.
+Owners (current): `dev|devops|lead|test`.
 
 ## `take`
 Shortcut: assign + move to in-progress.
@@ -197,6 +222,18 @@ Shortcut: assign + move to in-progress.
 openclaw recipes take --team-id <teamId> --ticket 0007 --owner dev
 ```
 
+## `handoff`
+QA handoff in one step: move a ticket to `work/testing/`, set `Status: testing`, assign to a tester (default `test`), and write/update the assignment stub.
+
+```bash
+openclaw recipes handoff --team-id <teamId> --ticket 0007
+openclaw recipes handoff --team-id <teamId> --ticket 0007 --tester test
+```
+
+Notes:
+- Creates `work/testing/` if missing.
+- Idempotent: if the ticket is already in `work/testing/`, it won’t re-move it; it will ensure fields + assignment stub.
+
 ## `complete`
 Shortcut: move to done + ensure `Status: done` + add `Completed:` timestamp.
 
@@ -214,7 +251,7 @@ openclaw recipes dispatch \
 Options:
 - `--team-id <teamId>` (required)
 - `--request <text>` (optional; prompts in TTY)
-- `--owner dev|devops|lead` (default: `dev`)
+- `--owner dev|devops|lead|test` (default: `dev`)
 - `--yes` (skip review prompt)
 
 Creates (createOnly):

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)