crewly 1.6.4 → 1.6.5

package/config/skills/agent/core/report-status/execute.sh

@@ -42,6 +42,7 @@ SUMMARY=""
 PROJECT_PATH=""
 TASK_PATH=""
 TASK_ID=""
+WORK_ITEM_ID=""
 PROGRESS=""
 STRUCTURED="false"
 
@@ -81,6 +82,10 @@ while [[ $# -gt 0 ]]; do
       TASK_ID="$2"
       shift 2
       ;;
+    --work-item-id|--wi-id)
+      WORK_ITEM_ID="$2"
+      shift 2
+      ;;
     --progress)
       PROGRESS="$2"
       shift 2
@@ -130,6 +135,7 @@ if [ -n "$INPUT_JSON" ]; then
   [ -z "$SUMMARY" ] && SUMMARY=$(printf '%s' "$INPUT" | jq -r '.summary // empty')
   [ -z "$TASK_PATH" ] && TASK_PATH=$(printf '%s' "$INPUT" | jq -r '.taskPath // empty')
   [ -z "$TASK_ID" ] && TASK_ID=$(printf '%s' "$INPUT" | jq -r '.taskId // empty')
+  [ -z "$WORK_ITEM_ID" ] && WORK_ITEM_ID=$(printf '%s' "$INPUT" | jq -r '.workItemId // empty')
   [ -z "$PROGRESS" ] && PROGRESS=$(printf '%s' "$INPUT" | jq -r '.progress // empty')
   [ -z "$PROJECT_PATH" ] && PROJECT_PATH=$(printf '%s' "$INPUT" | jq -r '.projectPath // empty')
   ARTIFACTS=$(printf '%s' "$INPUT" | jq -c '.artifacts // empty')
@@ -201,19 +207,37 @@ BODY=$(jq -n --arg content "$MESSAGE" --arg senderName "$SESSION_NAME" \
 
 api_call POST "/chat/agent-response" "$BODY"
 
-# If task is done and taskPath provided, move task file to done folder
-if [ "$STATUS" = "done" ] && [ -n "$TASK_PATH" ]; then
-  COMPLETE_BODY=$(jq -n \
-    --arg taskPath "$TASK_PATH" \
-    --arg sessionName "$SESSION_NAME" \
-    '{taskPath: $taskPath, sessionName: $sessionName}')
-  api_call POST "/task-management/complete" "$COMPLETE_BODY" || true
-fi
-
-# Auto-complete tracked tasks when status is done
+# Mark V3 WorkItem(s) for this session as complete when status=done.
+# Per spec/2026-05-06-task-management-v1-deprecation.md, V3 task-pool is now
+# the source of truth — we no longer move .md files via the v1
+# `/task-management/complete{-by-session}` endpoints.
+#
+# Resolution order for which WorkItem to complete:
+#   1. `workItemId` in input (preferred — explicit reference)
+#   2. The agent's currently-running WI fetched from the pool
+#
+# The legacy `taskPath` input is still accepted for backwards compatibility
+# but no longer drives the API call.
 if [ "$STATUS" = "done" ]; then
-  SESSION_BODY=$(jq -n --arg sessionName "$SESSION_NAME" '{sessionName: $sessionName}')
-  api_call POST "/task-management/complete-by-session" "$SESSION_BODY" || true
+  TARGET_WI_ID="${WORK_ITEM_ID:-}"
+  if [ -z "$TARGET_WI_ID" ]; then
+    # Fall back: query pool for this session's running WIs and complete the first match.
+    POOL_RESP=$(api_call GET "/task-pool/items?status=running&target=${SESSION_NAME}" 2>/dev/null || echo '{}')
+    TARGET_WI_ID=$(echo "$POOL_RESP" | jq -r '.workItems[0].id // .data[0].id // empty' 2>/dev/null || true)
+  fi
+
+  if [ -n "$TARGET_WI_ID" ]; then
+    # Hygiene #4: emit canonical body shape `{agentId, result:{summary}}`
+    # required by /api/task-pool/complete (task-pool.controller.ts
+    # `completeItem`). Prior shape `{summary}` 400'd with
+    # `agentId is required` + `summary required in body.result`,
+    # forcing every worker into a direct-curl workaround.
+    COMPLETE_BODY=$(jq -n \
+      --arg agentId "$SESSION_NAME" \
+      --arg summary "$SUMMARY" \
+      '{agentId: $agentId, result: {summary: $summary}}')
+    api_call POST "/task-pool/complete/${TARGET_WI_ID}" "$COMPLETE_BODY" || true
+  fi
 fi
 
 # Auto-persist key findings as project knowledge when task is done (#127, #219).

package/config/skills/agent/core/save-working-state/execute.sh

@@ -1,19 +1,30 @@
 #!/bin/bash
-# Save working state for current task — persists across session restarts
+# Save free-form working state for the current task — persists across session restarts.
+#
+# V3-only as of spec 2026-05-06-task-management-v1-deprecation.md. Replaces
+# `POST /task-management/save-working-notes`, which wrote a separate
+# `.md` notes file. Notes now accumulate under `WorkItem.metadata.notes[]`.
+#
+# Input shape:
+#   { "workItemId": "abc-123", "sessionName": "dev-1", "notes": "current state..." }
+#
+# Backwards-compat: a `taskId` field is accepted as an alias for
+# `workItemId` for one release window. New callers should use `workItemId`.
+
 set -euo pipefail
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 source "${SCRIPT_DIR}/../../_common/lib.sh"
 
 INPUT=$(read_json_input "${1:-}")
-[ -z "$INPUT" ] && error_exit "Usage: execute.sh '{\"taskId\":\"xxx\",\"sessionName\":\"crewly-product-sam-xxx\",\"notes\":\"current state...\"}'"
+[ -z "$INPUT" ] && error_exit "Usage: execute.sh '{\"workItemId\":\"abc-123\",\"sessionName\":\"dev-1\",\"notes\":\"current state\"}'"
 
-TASK_ID=$(printf '%s' "$INPUT" | jq -r '.taskId // empty')
+WORK_ITEM_ID=$(printf '%s' "$INPUT" | jq -r '.workItemId // .taskId // empty')
 SESSION_NAME=$(printf '%s' "$INPUT" | jq -r '.sessionName // empty')
 NOTES=$(printf '%s' "$INPUT" | jq -r '.notes // empty')
-require_param "taskId" "$TASK_ID"
+require_param "workItemId" "$WORK_ITEM_ID"
 require_param "sessionName" "$SESSION_NAME"
 require_param "notes" "$NOTES"
 
-BODY=$(printf '%s' "$INPUT" | jq '{taskId: .taskId, sessionName: .sessionName, notes: .notes}')
+BODY=$(jq -n --arg author "$SESSION_NAME" --arg note "$NOTES" '{author: $author, note: $note}')
 
-api_call POST "/task-management/save-working-notes" "$BODY"
+api_call POST "/task-pool/items/${WORK_ITEM_ID}/notes" "$BODY"

package/config/skills/agent/core/schedule-followup/SKILL.md

@@ -1,3 +1,22 @@
+---
+name: schedule-followup
+description: Schedule a future check-in that creates a WorkItem for you or another agent at a specific time (one-shot or bounded recurring).
+version: 1.0.0
+category: followup
+skillType: claude-skill
+tags:
+  - followup
+  - schedule
+  - cron
+  - workitem
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 15000
+---
+
 # schedule-followup
 
 Schedule a future check-in that creates a WorkItem for you or another agent.

package/config/skills/agent/core/send-message/SKILL.md

@@ -4,6 +4,12 @@ description: "Send a direct message to another agent's terminal session."
 version: 1.0.0
 category: communication
 skillType: claude-skill
+# Per orchestrator-namespace convention: orc has its own send-message wrapper at
+# config/skills/orchestrator/send-message/ which routes through the orc-specific
+# message-routing layer (delivery framing, jargon-hygiene gate, owner-vs-agent
+# audience distinction). Listing orchestrator here would let orc fall back to the
+# generic agent-side path and miss orc-specific behaviors. Keep orchestrator EXCLUDED.
+# Spec provenance: 4-piece skill-mistake fix dispatch (Sam→Quinn, post-PR #446 merge).
 assignableRoles:
   - developer
   - qa

package/config/skills/agent/core/supersede-memory/SKILL.md

@@ -0,0 +1,76 @@
+---
+name: Supersede Memory
+description: Mark a stale memory entry as superseded by a newer one. Hides the old entry from default recall while keeping it in the audit log.
+version: 1.0.0
+category: memory
+skillType: claude-skill
+assignableRoles:
+  - developer
+  - qa
+  - tpm
+  - designer
+  - frontend-developer
+  - backend-developer
+  - fullstack-dev
+  - qa-engineer
+  - product-manager
+  - architect
+  - generalist
+  - sales
+  - support
+triggers:
+  - supersede memory
+  - replace memory
+  - update outdated memory
+tags:
+  - memory
+  - supersession
+  - audit
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 15000
+---
+
+# Supersede Memory
+
+Mark a stale memory entry as superseded by a newer one. After this call, default `recall` will hide the old entry but keep it in the raw store for audit.
+
+Use this when a fact you previously remembered has been updated — for example, when a price, a process, or a decision changes, and the old entry would now confuse the agent if returned alongside the new one.
+
+## Usage
+
+```bash
+# CLI flags (preferred)
+bash execute.sh \
+  --agent crewly-product-max-c69ce8e6 \
+  --old-id rk-pricing-799 \
+  --new-id rk-pricing-800-plus-credits \
+  --reason "Steve updated pricing 2026-05-01"
+
+# Legacy JSON
+bash execute.sh '{
+  "agentId": "crewly-product-max-c69ce8e6",
+  "oldId": "rk-pricing-799",
+  "newId": "rk-pricing-800-plus-credits",
+  "reason": "Steve updated pricing 2026-05-01"
+}'
+```
+
+## Required Parameters
+- `--agent`  / `agentId`: The agent whose memory store contains both entries
+- `--old-id` / `oldId`:  The id of the entry being superseded
+- `--new-id` / `newId`:  The id of the new entry that replaces the old one
+
+## Optional Parameters
+- `--reason` / `reason`: Human-readable reason. Appended to the old entry's `evidence` as `supersession-reason:<reason>` so the audit trail survives.
+
+## Behavior
+1. Validates that both ids resolve to existing entries in the agent's memory.
+2. Validates that `oldId !== newId` (an entry cannot supersede itself).
+3. Sets `superseded=true` and `supersededBy=newId` on the old entry.
+4. Extends the old entry's `evidence` with a supersession marker.
+5. Persists via the canonical write path (atomic + cache-invalidating).
+6. After this call, default recall hides the old entry; explicit recall with `includeHidden=true` still returns it.

package/config/skills/agent/core/supersede-memory/execute.sh

@@ -0,0 +1,108 @@
+#!/bin/bash
+# Mark a stale memory entry as superseded by a newer one.
+# Memory Phase 1 — M4. Hides the old entry from default recall while keeping
+# it in the audit log. Both entries must already exist in the agent memory store.
+set -euo pipefail
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+source "${SCRIPT_DIR}/../../_common/lib.sh"
+
+print_usage() {
+  cat <<'EOF_USAGE'
+Usage:
+  # CLI flags (preferred)
+  bash execute.sh --agent dev-1 --old-id rk-old --new-id rk-new --reason "Pricing updated 2026-05-01"
+
+  # Legacy JSON (backward compatible)
+  bash execute.sh '{"agentId":"dev-1","oldId":"rk-old","newId":"rk-new","reason":"Pricing updated"}'
+
+Options:
+  --agent   | -a   Agent ID / session name (required)
+  --old-id  | -o   Id of the entry being superseded (required)
+  --new-id  | -n   Id of the new entry that replaces the old one (required)
+  --reason  | -r   Optional human-readable reason; appended to old entry's evidence
+  --json    | -j   Raw JSON payload
+  --help    | -h   Show this help
+EOF_USAGE
+}
+
+INPUT_JSON=""
+AGENT_ID=""
+OLD_ID=""
+NEW_ID=""
+REASON=""
+
+# Detect legacy JSON argument
+if [[ $# -gt 0 && ${1:0:1} == '{' ]]; then
+  INPUT_JSON="$1"
+  shift || true
+fi
+
+while [[ $# -gt 0 ]]; do
+  case "$1" in
+    --agent|-a)
+      AGENT_ID="$2"
+      shift 2
+      ;;
+    --old-id|-o)
+      OLD_ID="$2"
+      shift 2
+      ;;
+    --new-id|-n)
+      NEW_ID="$2"
+      shift 2
+      ;;
+    --reason|-r)
+      REASON="$2"
+      shift 2
+      ;;
+    --json|-j)
+      INPUT_JSON="$2"
+      shift 2
+      ;;
+    --help|-h)
+      print_usage
+      exit 0
+      ;;
+    --)
+      shift
+      break
+      ;;
+    *)
+      if [[ -z "$INPUT_JSON" && ${1:0:1} == '{' ]]; then
+        INPUT_JSON="$1"
+        shift
+      else
+        error_exit "Unknown argument: $1. Use --help for usage."
+      fi
+      ;;
+  esac
+done
+
+# Parse JSON if provided
+if [ -n "$INPUT_JSON" ]; then
+  INPUT=$(read_json_input "$INPUT_JSON")
+  [ -z "$AGENT_ID" ] && AGENT_ID=$(printf '%s' "$INPUT" | jq -r '.agentId // empty')
+  [ -z "$OLD_ID" ] && OLD_ID=$(printf '%s' "$INPUT" | jq -r '.oldId // empty')
+  [ -z "$NEW_ID" ] && NEW_ID=$(printf '%s' "$INPUT" | jq -r '.newId // empty')
+  [ -z "$REASON" ] && REASON=$(printf '%s' "$INPUT" | jq -r '.reason // empty')
+fi
+
+require_param "agentId (--agent)" "$AGENT_ID"
+require_param "oldId (--old-id)" "$OLD_ID"
+require_param "newId (--new-id)" "$NEW_ID"
+
+# Build body using env vars to safely handle special characters in reason.
+export _SUP_AGENT="$AGENT_ID"
+export _SUP_OLD="$OLD_ID"
+export _SUP_NEW="$NEW_ID"
+
+if [ -n "$REASON" ]; then
+  export _SUP_REASON="$REASON"
+  BODY=$(jq -n '{agentId: env._SUP_AGENT, oldId: env._SUP_OLD, newId: env._SUP_NEW, reason: env._SUP_REASON}')
+  unset _SUP_REASON
+else
+  BODY=$(jq -n '{agentId: env._SUP_AGENT, oldId: env._SUP_OLD, newId: env._SUP_NEW}')
+fi
+unset _SUP_AGENT _SUP_OLD _SUP_NEW
+
+api_call POST "/memory/supersede" "$BODY"

package/config/skills/agent/core/watch-for-event/SKILL.md

@@ -1,3 +1,22 @@
+---
+name: watch-for-event
+description: Subscribe to a system event (like agent:idle or task:completed) and create a WorkItem every time it fires — reactive follow-up, not time-based.
+version: 1.0.0
+category: followup
+skillType: claude-skill
+tags:
+  - followup
+  - event
+  - reactive
+  - workitem
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 15000
+---
+
 # watch-for-event
 
 Subscribe to a system event (like `agent:idle` or `task:completed`) and create

package/config/skills/agent/onboarding/materialize-team/SKILL.md

@@ -0,0 +1,94 @@
+---
+name: Materialize Team
+description: Materialize a confirmed team recommendation — writes the team config and flips the onboardingComplete flag. Onboarding-only.
+version: 0.1.0
+category: onboarding
+skillType: claude-skill
+assignableRoles:
+  - orchestrator
+triggers:
+  - materialize team
+  - create team
+  - confirm team
+tags:
+  - onboarding
+  - materialize
+  - team
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 15000
+---
+
+# Materialize Team (Onboarding v3)
+
+Take a confirmed `recommendation` (the object returned from
+`recommend-team`) and create the actual team:
+
+1. Writes `<teamsDir>/<uuid>/config.json` describing the team.
+2. Persists `{ onboardingComplete: true, completedAt }` to
+   `<projectFlagPath>` so the runtime knows onboarding is done.
+
+Returns the new `teamId` + the on-disk paths.
+
+This skill is callable **only when orc is in `'onboarding'` mode**.
+
+## Parameters
+
+| Flag                       | JSON Field         | Required | Description |
+|----------------------------|--------------------|----------|-------------|
+| `--recommendation` / `-r`  | `recommendation`   | Yes      | JSON object from `recommend-team` (templateId + agents + reasoning + source) |
+| `--teams-dir`              | `teamsDir`         | No       | Override the teams directory (default: `~/.crewly/teams`) |
+| `--project-flag-path`      | `projectFlagPath`  | No       | Override the project-flag path (default: `~/.crewly/onboarding-complete.json`) |
+| `--json` / `-j`            | —                  | No       | Whole request as a JSON object |
+
+## Examples
+
+```bash
+# Full payload via stdin
+cat <<'EOF' | bash execute.sh
+{
+  "recommendation": {
+    "templateId": "dtc-viral-content-team",
+    "agents": [
+      { "role": "content-drafter", "responsibilities": "...", "skillIds": ["content-drafter"] },
+      { "role": "support-triage",  "responsibilities": "...", "skillIds": ["support-triage"]  }
+    ],
+    "reasoning": "...",
+    "source": "hardcoded:ecommerce-content-support"
+  }
+}
+EOF
+
+# Or pass the recommendation JSON directly
+bash execute.sh --recommendation '{"templateId":"...","agents":[...],"reasoning":"...","source":"..."}'
+```
+
+## Output
+
+```json
+{
+  "success": true,
+  "result": {
+    "teamId": "ea0dd57a-15a9-4a34-9c6f-8f04534d89e7",
+    "teamConfigPath": "/Users/.../.crewly/teams/<uuid>/config.json",
+    "onboardingComplete": true,
+    "projectFlagPath": "/Users/.../.crewly/onboarding-complete.json",
+    "recommendation": { "...": "echo of the input" }
+  }
+}
+```
+
+## Notes
+
+- v0 (Mon 5/4 EOD): writes a minimal team config (id, templateId,
+  members[], onboardingSource) and flips the flag. No agent-soul
+  personalisation, no project linkage.
+- Wed–Fri: this skill will delegate to
+  `services/onboarding/onboarding-provision.service.ts` for full
+  template-engine provisioning + agent souls + goals.md generation.
+  The skill's input/output shape stays stable.
+- Errors propagate as `{success:false,error:"..."}`; orc surfaces them
+  honestly to the user rather than retrying silently.

package/config/skills/agent/onboarding/materialize-team/execute.sh

@@ -0,0 +1,98 @@
+#!/bin/bash
+# Materialize a confirmed team recommendation: write the team config and flip
+# the project onboardingComplete flag. Onboarding-only.
+# Wraps POST /api/orchestrator/onboarding/materialize-team.
+set -euo pipefail
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+source "${SCRIPT_DIR}/../../_common/lib.sh"
+
+INPUT_JSON=""
+RECOMMENDATION=""
+TEAMS_DIR=""
+PROJECT_FLAG_PATH=""
+
+# Detect legacy JSON argument
+if [[ $# -gt 0 && ${1:0:1} == '{' ]]; then
+  INPUT_JSON="$1"
+  shift || true
+fi
+
+while [[ $# -gt 0 ]]; do
+  case "$1" in
+    --recommendation|-r)
+      RECOMMENDATION="$2"
+      shift 2
+      ;;
+    --teams-dir)
+      TEAMS_DIR="$2"
+      shift 2
+      ;;
+    --project-flag-path)
+      PROJECT_FLAG_PATH="$2"
+      shift 2
+      ;;
+    --json|-j)
+      INPUT_JSON="$2"
+      shift 2
+      ;;
+    --help|-h)
+      cat <<EOF
+Usage: execute.sh --recommendation '<json>' \\
+                  [--teams-dir <path>] [--project-flag-path <path>]
+
+Or pipe a full request via stdin / --json:
+  {"recommendation": {...}, "teamsDir": "...", "projectFlagPath": "..."}
+
+The "recommendation" payload is the JSON object returned from
+the recommend-team skill (templateId + agents + reasoning + source).
+EOF
+      exit 0
+      ;;
+    --)
+      shift
+      break
+      ;;
+    *)
+      if [[ -z "$INPUT_JSON" && ${1:0:1} == '{' ]]; then
+        INPUT_JSON="$1"
+        shift
+      else
+        error_exit "Unknown argument: $1"
+      fi
+      ;;
+  esac
+done
+
+# Read from stdin if nothing else
+if [ -z "$INPUT_JSON" ] && [ -z "$RECOMMENDATION" ] && [ ! -t 0 ]; then
+  STDIN_DATA="$(cat)"
+  if [[ ${STDIN_DATA:0:1} == '{' ]]; then
+    INPUT_JSON="$STDIN_DATA"
+  fi
+fi
+
+# Parse JSON wrapper if provided
+if [ -n "$INPUT_JSON" ]; then
+  INPUT=$(read_json_input "$INPUT_JSON")
+  if [ -z "$RECOMMENDATION" ]; then
+    REC_FROM_JSON=$(printf '%s' "$INPUT" | jq -c '.recommendation // empty')
+    [ -n "$REC_FROM_JSON" ] && RECOMMENDATION="$REC_FROM_JSON"
+  fi
+  [ -z "$TEAMS_DIR" ]          && TEAMS_DIR=$(printf '%s' "$INPUT" | jq -r '.teamsDir // empty')
+  [ -z "$PROJECT_FLAG_PATH" ]  && PROJECT_FLAG_PATH=$(printf '%s' "$INPUT" | jq -r '.projectFlagPath // empty')
+fi
+
+require_param "recommendation (--recommendation)" "$RECOMMENDATION"
+
+export _MT_REC="$RECOMMENDATION"
+BODY=$(jq -n '{recommendation: (env._MT_REC | fromjson)}')
+unset _MT_REC
+
+if [ -n "$TEAMS_DIR" ]; then
+  BODY=$(echo "$BODY" | jq --arg p "$TEAMS_DIR" '. + {teamsDir: $p}')
+fi
+if [ -n "$PROJECT_FLAG_PATH" ]; then
+  BODY=$(echo "$BODY" | jq --arg p "$PROJECT_FLAG_PATH" '. + {projectFlagPath: $p}')
+fi
+
+api_call POST "/orchestrator/onboarding/materialize-team" "$BODY"

package/config/skills/agent/onboarding/recommend-team/SKILL.md

@@ -0,0 +1,90 @@
+---
+name: Recommend Team
+description: Recommend a team configuration (template + agents) based on the user's business context. Onboarding-only.
+version: 0.1.0
+category: onboarding
+skillType: claude-skill
+assignableRoles:
+  - orchestrator
+triggers:
+  - recommend a team
+  - propose team
+  - suggest team
+  - team recommendation
+tags:
+  - onboarding
+  - recommendation
+  - team
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 10000
+---
+
+# Recommend Team (Onboarding v3)
+
+Turn the discovery answers gathered in phases 1–3 of the onboarding
+conversation into a concrete team proposal: a template id + 2–4 agents
+with responsibilities and skill ids.
+
+This skill is callable **only when orc is in `'onboarding'` mode**. The
+runtime gate enforces that via `ONBOARDING_SKILL_ALLOWLIST`.
+
+## Parameters
+
+| Flag             | JSON Field | Required | Description |
+|------------------|------------|----------|-------------|
+| `--industry` / `-i` | `industry` | Yes | Free-text industry / domain (e.g. "small Shopify skincare shop") |
+| `--scale` / `-s`    | `scale`    | Yes | One of: `solo`, `small-team`, `company` |
+| `--tasks` / `-t`    | `tasks`    | No  | JSON array of `{ name: string, tier: <FeasibilityTier> }`. Empty allowed. |
+| `--json` / `-j`     | —          | No  | Whole request as a JSON object. |
+
+Feasibility tier vocabulary (must match the system prompt):
+`yes-today` | `collaborative` | `roadmap` | `out-of-scope`.
+
+## Examples
+
+```bash
+# Anchor demo (Steve's e-commerce skincare shop)
+bash execute.sh \
+  --industry "small Shopify skincare shop" \
+  --scale solo \
+  --tasks '[{"name":"weekly content","tier":"yes-today"},{"name":"customer support","tier":"yes-today"}]'
+
+# Or one-shot JSON
+bash execute.sh '{
+  "industry": "growth marketing agency",
+  "scale": "small-team",
+  "tasks": [
+    {"name":"lead gen","tier":"yes-today"},
+    {"name":"content distribution","tier":"yes-today"}
+  ]
+}'
+```
+
+## Output
+
+```json
+{
+  "success": true,
+  "recommendation": {
+    "templateId": "dtc-viral-content-team",
+    "agents": [
+      { "role": "content-drafter", "responsibilities": "...", "skillIds": [...] },
+      { "role": "support-triage",  "responsibilities": "...", "skillIds": [...] }
+    ],
+    "reasoning": "...",
+    "source": "hardcoded:ecommerce-content-support"
+  }
+}
+```
+
+## Notes
+
+- v0 (Mon 5/4 EOD): 5 hardcoded heuristic mappings + a generic 2-agent
+  fallback. ~80% of users land on a hardcoded mapping.
+- Wed–Fri: real RAG over Mia's spec v3 + doc 69 + the live template
+  registry. The `recommendation` shape stays stable — orc does not need
+  to be re-prompted when the strategy changes.