@lifeaitools/rdc-skills 0.37.8 → 0.37.9

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "rdc",
-  "version": "0.37.8",
+  "version": "0.37.9",
   "description": "RDC typed-agent dispatch skill suite for Claude Code — plan, build, review, overnight unattended builds with work-item tracking and TDD enforcement.",
   "author": {
     "name": "LIFEAI",
@@ -2120,6 +2120,78 @@
       "enabled_default": true,
       "codeflow_required": false,
       "purpose": "orient before working: position, target from the registry, and the harness shape"
+    },
+    "new": {
+      "name": "new",
+      "slash": "rdc:new",
+      "category": "dev-loop",
+      "usage": "rdc:new <slug> --product-type <t> [--environment <e> --host-type <t> --url <u>]",
+      "args": {
+        "positional": [
+          {
+            "name": "slug",
+            "required": true,
+            "description": "the new product's registry slug",
+            "accepts": "string"
+          }
+        ],
+        "flags": [
+          {
+            "name": "product-type",
+            "required": true,
+            "description": "one of the 11 declared product classes (app, site-ts, site-html, package, share-app, prototype, model, mcp, documentation, corpus, artifact)",
+            "accepts": "string"
+          },
+          {
+            "name": "environment",
+            "required": false,
+            "description": "deployment environment to also register (dev, prod, ...) — dev-only is the normal outcome",
+            "accepts": "string"
+          },
+          {
+            "name": "host-type",
+            "required": false,
+            "description": "runtime for the registered environment (coolify, pm2, ...)",
+            "accepts": "string"
+          },
+          {
+            "name": "url",
+            "required": false,
+            "description": "the registered environment's URL",
+            "accepts": "string"
+          }
+        ]
+      },
+      "requires": [
+        "supabase",
+        "git"
+      ],
+      "produces": [
+        "repo_registry_writes",
+        "app_deployments_writes"
+      ],
+      "default_model": "haiku",
+      "triggers": [
+        "create a new app",
+        "scaffold a new site",
+        "register a new package",
+        "rdc:new",
+        "new product",
+        "start a new repo",
+        "add a new deployment environment"
+      ],
+      "follows": [],
+      "leads_to": [
+        "open",
+        "plan",
+        "build",
+        "deploy"
+      ],
+      "sandbox_aware": false,
+      "output_contract": "guides/output-contract.md",
+      "enabled_default": true,
+      "codeflow_required": false,
+      "purpose": "scaffold and register a new product (rdc-harness create), then its deployment environment(s) (rdc-harness new) -- the create-time gap /rdc:open's gate-only design left unwrapped"
     }
   },
   "commands_meta": {

package/README.md

@@ -333,6 +333,7 @@ skills/
   help/SKILL.md        (manifest-driven skill index)
   housekeeping/SKILL.md (weekly maintenance audit)
   lifeai-brochure-author/SKILL.md (brochure JSX authoring)
+  new/SKILL.md         (product scaffolding and registration)
   new-model/SKILL.md   (reference model registration gate)
   onramp/SKILL.md      (Place Fund phase-1 enrollment)
   open/SKILL.md        (orient first: position, target, harness shape)

package/clauth-plugin.json

@@ -1,7 +1,7 @@
 {
   "schema": "lifeai.plugin.v1",
   "id": "rdc-skills",
-  "version": "0.37.8",
+  "version": "0.37.9",
   "publisher": "LIFEAI",
   "core": false,
   "documentation": {

package/commands/flow.md

@@ -45,44 +45,44 @@ rdc:flow normal                   # clear — back to no flow declared
 
 ## Steps
 
+**One direct script call, nothing more.** `$LIFEAI_ENV/bin/rdc-flow.mjs` is the CLI over
+`hooks/lib/rdc-flow.mjs` — run it, read its printed JSON, done. There is no research step:
+do not read this file's own source or reconstruct the call by hand, and do not fall back to
+an inline `node -e "import(...)"` — the CLI already does the right sequence internally. The
+call itself is fast (~0.1–0.2s measured live); if a turn spends more than a few seconds on
+this, that time is the agent reading docs, not the script running.
+
 ### 1. Read the current state
 
 ```bash
-node -e "import(require('url').pathToFileURL(process.env.LIFEAI_ENV + '/hooks/lib/rdc-flow.mjs').href).then(m=>console.log(JSON.stringify(m.currentState(),null,2)))"
+node $LIFEAI_ENV/bin/rdc-flow.mjs status
 ```
 
-`currentState()` reads BOTH axes at once — the declared flow AND any live `rdc-mode.mjs` hotfix/maintenance window — because a relaxed mode overrides a required flow (loosest state wins) and a status check that only showed flow would miss that override entirely. Report `flow` (or `null` if nothing declared — the fail-closed default), `flowReason`/`flowSetBy`/`flowSetAt` when set, and `mode` (`normal` unless a hotfix/maintenance window is open), with `modeReason`/`modeMinutesLeft` when it isn't.
+Prints BOTH axes at once — the declared flow AND any live `rdc-mode.mjs` hotfix/maintenance window — because a relaxed mode overrides a required flow (loosest state wins) and a status check that only showed flow would miss that override entirely. Report `flow` (or `null` if nothing declared — the fail-closed default), `flowReason`/`flowSetBy`/`flowSetAt` when set, and `mode` (`normal` unless a hotfix/maintenance window is open), with `modeReason`/`modeMinutesLeft` when it isn't.
 
 ### 2. Setting a plain work-shape flow — no reason required
 
 ```bash
-node -e "import(require('url').pathToFileURL(process.env.LIFEAI_ENV + '/hooks/lib/rdc-flow.mjs').href).then(m=>console.log(JSON.stringify(m.setFlow(process.argv[1],{setBy:process.argv[2]}),null,2)))" "<flow>" "<session-id>"
+node $LIFEAI_ENV/bin/rdc-flow.mjs <flow>
 ```
 
 ### 3. Setting hotfix or maintenance — a reason is REQUIRED
 
-Refuse to proceed without one — both setters throw on an empty reason for these two values, by design: an unexplained disarm is how a temporary state becomes permanent.
-
-Guard relaxation reads the **mode** store (`rdc-mode.mjs` `isRelaxedFor()`); the work-item
-exemption reads the **flow** store. `setFlow` alone relaxes no guard, so this one command
-writes both — `setFlowOrMode` routes `hotfix`/`maintenance` to `setMode`, then `setFlow`
-records the flow:
-
 ```bash
-node -e "import(require('url').pathToFileURL(process.env.LIFEAI_ENV + '/hooks/lib/rdc-flow.mjs').href).then(m=>{const [n,reason,setBy]=process.argv.slice(1);const o={reason,setBy};m.setFlowOrMode(n,o);m.setFlow(n,o);console.log(JSON.stringify(m.currentState(),null,2))})" "<hotfix|maintenance>" "<reason>" "<session-id>"
+node $LIFEAI_ENV/bin/rdc-flow.mjs <hotfix|maintenance> "<reason>"
 ```
 
-Read the printed state: `flow` and `mode` must both show the name. If `mode` is still `normal`, no guard is relaxed — stop and say so.
+The CLI refuses (exit 1, no state written) without one — an unexplained disarm is how a temporary state becomes permanent. It also writes both stores itself: guard relaxation reads the **mode** store (`rdc-mode.mjs` `isRelaxedFor()`); the work-item exemption reads the **flow** store; a bare `setFlow` would relax no guard, so the CLI calls `setFlowOrMode` then `setFlow` internally and prints the merged result of both.
 
-Then state plainly, in the checklist: **which guards are now relaxed, that the safety set is still armed, and that this stays active until explicitly cleared (no TTL — active management, not a silent timer).**
+Read the printed state: `flow` and `mode` must both show the name — the CLI itself throws if they disagree, so a clean exit already proves this. Then state plainly, in the checklist: **which guards are now relaxed, that the safety set is still armed, and that this stays active until explicitly cleared (no TTL — active management, not a silent timer).**
 
 ### 4. Returning to normal
 
 ```bash
-node -e "import(require('url').pathToFileURL(process.env.LIFEAI_ENV + '/hooks/lib/rdc-flow.mjs').href).then(m=>{m.clearFlow();m.setFlowOrMode('normal');console.log(JSON.stringify(m.currentState(),null,2))})"
+node $LIFEAI_ENV/bin/rdc-flow.mjs normal
 ```
 
-This clears both stores; a hotfix mode left open after the flow is cleared would keep guards relaxed.
+Clears both stores in one call; a hotfix mode left open after the flow is cleared would keep guards relaxed.
 
 Do this **as soon as the incident is over**, or the moment the declared work-shape changes.
 
@@ -98,5 +98,6 @@ Do this **as soon as the incident is over**, or the moment the declared work-sha
 
 ```bash
 node --test $LIFEAI_ENV/tests/rdc-flow.test.mjs
+node --test $LIFEAI_ENV/tests/rdc-flow-cli.test.mjs
 node --test C:/Dev/rdc-harness/fsm-daemon/tests/matrix.test.js
 ```

package/commands/mode.md

@@ -12,6 +12,12 @@ description: rdc:mode [status|hotfix "<reason>" [minutes]|normal] — show or se
 > default) — one FSM surface instead of two. This skill's underlying code
 > (`rdc-mode.mjs`) is untouched and still works; new work should use
 > `rdc:flow hotfix "<reason>"` instead of `rdc:mode hotfix ...`.
+>
+> **And `rdc:flow` itself is now a direct script call, not a doc to read:**
+> `node $LIFEAI_ENV/bin/rdc-flow.mjs hotfix "<reason>"` — no inline `node -e`,
+> no TTL/minutes option (flow-routed hotfix/maintenance never carries one, by
+> design). This page's own `node -e` steps below are the legacy `rdc:mode`
+> path (the only one with a `minutes` window) and stay as documented.
 
 # rdc:mode — operating mode