crewly 1.5.18 → 1.5.19

package/config/skills/team-leader/delegate-task/execute.sh

@@ -61,6 +61,7 @@ if [ -z "$INPUT_JSON" ] && [ -z "$TASK" ] && [ ! -t 0 ]; then
 fi
 
 # Parse JSON if provided (backward compatible)
+INPUT="{}"
 if [ -n "$INPUT_JSON" ]; then
   INPUT=$(read_json_input "$INPUT_JSON")
   [ -z "$TO" ] && TO=$(printf '%s' "$INPUT" | jq -r '.to // empty')
@@ -116,7 +117,10 @@ fi
 TASK_MESSAGE="New task from Team Leader (priority: ${PRIORITY}):\n\n**[REQUIRED] When done, you MUST:** (1) Output a text summary of your work, findings, and any issues. (2) Call report-status:\nbash ${CREWLY_ROOT}/config/skills/agent/core/report-status/execute.sh '{\"sessionName\":\"${TO}\",\"status\":\"done\",\"summary\":\"<brief summary>\",\"projectPath\":\"${PROJECT_PATH}\"}'\n\n---\n\n${TASK}"
 [ -n "$CONTEXT" ] && TASK_MESSAGE="${TASK_MESSAGE}\n\nContext: ${CONTEXT}"
 
-# Deliver the task message with fallback strategy
+# Deliver the task message with fallback strategy:
+# 1. Try normal delivery (waitForReady)
+# 2. If fails, try force delivery
+# 3. If still fails, auto-start the worker then retry
 BODY=$(jq -n --arg message "$TASK_MESSAGE" '{message: $message, waitForReady: true, waitTimeout: 15000}')
 
 DELIVER_OK=true
@@ -125,8 +129,43 @@ api_call POST "/terminal/${TO}/deliver" "$BODY" || DELIVER_OK=false
 if [ "$DELIVER_OK" = "false" ]; then
   FORCE_BODY=$(jq -n --arg message "$TASK_MESSAGE" '{message: $message, force: true}')
   api_call POST "/terminal/${TO}/deliver" "$FORCE_BODY" || {
-    echo '{"error":"Failed to deliver task to '"$TO"'. Session may not exist or agent is not running."}'
-    exit 1
+    # Worker likely offline — attempt auto-start if we have team context
+    STARTED=false
+    if [ -n "$TEAM_ID" ]; then
+      # Find worker's memberId from team data
+      WORKER_MEMBER_ID=""
+      if [ -n "$TEAM_DATA" ] && [ "$(echo "$TEAM_DATA" | jq -r '.success // false')" = "true" ]; then
+        WORKER_MEMBER_ID=$(echo "$TEAM_DATA" | jq -r --arg session "$TO" \
+          '.data.members[] | select(.sessionName == $session) | .id // empty' 2>/dev/null || true)
+      else
+        # Fetch team data if not already loaded
+        TEAM_DATA=$(api_call GET "/teams/${TEAM_ID}" 2>/dev/null || echo '{}')
+        WORKER_MEMBER_ID=$(echo "$TEAM_DATA" | jq -r --arg session "$TO" \
+          '.data.members[] | select(.sessionName == $session) | .id // empty' 2>/dev/null || true)
+      fi
+
+      if [ -n "$WORKER_MEMBER_ID" ]; then
+        echo '{"info":"Worker '"$TO"' appears offline — auto-starting..."}' >&2
+        START_RESULT=$(api_call POST "/teams/${TEAM_ID}/members/${WORKER_MEMBER_ID}/start" '{}' 2>/dev/null || true)
+        START_OK=$(echo "$START_RESULT" | jq -r '.success // false' 2>/dev/null || echo "false")
+
+        if [ "$START_OK" = "true" ]; then
+          echo '{"info":"Worker '"$TO"' start triggered — retrying delivery in 10s..."}' >&2
+          sleep 10
+          # Retry delivery after agent boots
+          RETRY_BODY=$(jq -n --arg message "$TASK_MESSAGE" '{message: $message, waitForReady: true, waitTimeout: 30000}')
+          api_call POST "/terminal/${TO}/deliver" "$RETRY_BODY" && STARTED=true || {
+            # Final fallback: force deliver
+            api_call POST "/terminal/${TO}/deliver" "$FORCE_BODY" && STARTED=true || true
+          }
+        fi
+      fi
+    fi
+
+    if [ "$STARTED" = "false" ]; then
+      echo '{"error":"Failed to deliver task to '"$TO"'. Worker is offline and could not be auto-started. Ensure the worker is a team member with a valid session.","to":"'"$TO"'","teamId":"'"$TEAM_ID"'"}'
+      exit 1
+    fi
   }
 fi
 

package/config/skills/team-leader/design-checklist/SKILL.md

@@ -0,0 +1,122 @@
+---
+name: Design Checklist
+description: "Generate an acceptance checklist for a delegated objective BEFORE execution begins. The checklist must be sent to and approved by the superior (Orchestrator/user) to ensure alignment. Once approved, it becomes the verification standard used by verify-output after task completion."
+version: 1.0.0
+category: quality
+skillType: claude-skill
+assignableRoles:
+  - team-leader
+triggers:
+  - design checklist
+  - create acceptance criteria
+  - define verification checklist
+  - alignment checklist
+tags:
+  - checklist
+  - quality
+  - alignment
+  - verification
+  - planning
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 30000
+---
+
+# Design Checklist
+
+Generates a structured acceptance checklist for a task/objective **before execution begins**.
+The checklist is sent to the Orchestrator (or user) for alignment and approval.
+Once approved, the TL uses it during `verify-output` after workers complete the task.
+
+## Flow
+
+```
+1. TL receives objective from Orchestrator
+2. TL runs design-checklist → generates checklist.json
+3. Checklist sent to Orchestrator for approval
+4. Orchestrator approves/adjusts → POST /api/task-management/:taskId/checklist/approve
+5. TL proceeds with decompose-goal + delegate-task
+6. Workers complete → TL runs verify-output with approved checklist
+```
+
+## Usage
+
+```bash
+bash {{SKILLS_PATH}}/team-leader/design-checklist/execute.sh \
+  --objective "Build user authentication" \
+  --project-path /path/to/project \
+  --task-id task-123 \
+  [--team-id team-456] \
+  [--mission-id mission-789]
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `--objective` | Yes | The objective/task to design acceptance criteria for |
+| `--project-path` | Yes | Project root path |
+| `--task-id` | Yes | Task ID for storing the checklist |
+| `--team-id` | No | Team ID (loads template verification pipeline as baseline) |
+| `--mission-id` | No | Mission ID (loads Mission.successCriteria for alignment) |
+
+## Output
+
+The skill outputs context for the runtime to generate a checklist, then stores it:
+
+```json
+{
+  "success": true,
+  "taskId": "task-123",
+  "checklistPath": "/project/.crewly/tasks/.../checklist.json",
+  "status": "pending_approval",
+  "itemCount": 5
+}
+```
+
+## Checklist Format
+
+```json
+{
+  "taskId": "task-123",
+  "objective": "Build user authentication",
+  "status": "pending_approval",
+  "createdBy": "tl-session-name",
+  "createdAt": "ISO8601",
+  "alignedWith": "mission-success-criteria (if available)",
+  "items": [
+    {
+      "id": "chk-1",
+      "category": "functionality",
+      "description": "JWT token generation and validation works correctly",
+      "type": "command",
+      "command": "npm test -- --grep 'jwt'",
+      "critical": true
+    },
+    {
+      "id": "chk-2",
+      "category": "quality",
+      "description": "Test coverage above 80%",
+      "type": "command",
+      "command": "npm test -- --coverage",
+      "critical": true
+    },
+    {
+      "id": "chk-3",
+      "category": "review",
+      "description": "Code follows project patterns and has proper error handling",
+      "type": "manual",
+      "critical": false
+    }
+  ]
+}
+```
+
+## Related Skills
+
+- `decompose-goal` — Break objective into subtasks (run AFTER checklist approved)
+- `verify-output` — Use approved checklist to verify completed work
+- `delegate-task` — Assign subtasks to workers

package/config/skills/team-leader/design-checklist/execute.sh

@@ -0,0 +1,157 @@
+#!/bin/bash
+# Design an acceptance checklist for an objective BEFORE execution.
+# The checklist is stored and must be approved by the superior before
+# the TL proceeds with decompose-goal and delegate-task.
+set -euo pipefail
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+source "${SCRIPT_DIR}/../_common/lib.sh"
+
+# --- Input parsing ---
+OBJECTIVE=""
+PROJECT_PATH=""
+TASK_ID=""
+TEAM_ID=""
+MISSION_ID=""
+INPUT_JSON=""
+
+if [[ $# -gt 0 && ${1:0:1} == '{' ]]; then
+  INPUT_JSON="$1"
+  shift || true
+fi
+
+while [[ $# -gt 0 ]]; do
+  case "$1" in
+    --objective|-o)     OBJECTIVE="$2";      shift 2 ;;
+    --project-path|-p)  PROJECT_PATH="$2";   shift 2 ;;
+    --task-id|-t)       TASK_ID="$2";        shift 2 ;;
+    --team-id|-g)       TEAM_ID="$2";        shift 2 ;;
+    --mission-id|-m)    MISSION_ID="$2";     shift 2 ;;
+    --json|-j)          INPUT_JSON="$2";     shift 2 ;;
+    --help|-h)
+      echo "Usage: execute.sh --objective 'Build auth' --project-path /path --task-id task-123 [--team-id team-456] [--mission-id mission-789]"
+      exit 0 ;;
+    *) shift ;;
+  esac
+done
+
+# Legacy JSON fallback
+if [[ -n "$INPUT_JSON" ]]; then
+  [[ -z "$OBJECTIVE" ]]    && OBJECTIVE=$(echo "$INPUT_JSON" | jq -r '.objective // empty' 2>/dev/null || true)
+  [[ -z "$PROJECT_PATH" ]] && PROJECT_PATH=$(echo "$INPUT_JSON" | jq -r '.projectPath // empty' 2>/dev/null || true)
+  [[ -z "$TASK_ID" ]]      && TASK_ID=$(echo "$INPUT_JSON" | jq -r '.taskId // empty' 2>/dev/null || true)
+  [[ -z "$TEAM_ID" ]]      && TEAM_ID=$(echo "$INPUT_JSON" | jq -r '.teamId // empty' 2>/dev/null || true)
+  [[ -z "$MISSION_ID" ]]   && MISSION_ID=$(echo "$INPUT_JSON" | jq -r '.missionId // empty' 2>/dev/null || true)
+fi
+
+require_param "objective" "$OBJECTIVE"
+require_param "project-path" "$PROJECT_PATH"
+require_param "task-id" "$TASK_ID"
+
+# --- Load context for checklist generation ---
+
+# Load Mission success criteria if mission linked
+MISSION_CRITERIA=""
+if [[ -n "$MISSION_ID" ]]; then
+  MISSION_DATA=$(api_call GET "/missions/${MISSION_ID}" 2>/dev/null || true)
+  if [[ -n "$MISSION_DATA" ]]; then
+    MISSION_CRITERIA=$(echo "$MISSION_DATA" | jq -r '.data.successCriteria // [] | join("\n- ")' 2>/dev/null || true)
+  fi
+fi
+
+# Load team template verification pipeline if team linked
+TEMPLATE_PIPELINE=""
+if [[ -n "$TEAM_ID" ]]; then
+  TEAM_DATA=$(api_call GET "/teams/${TEAM_ID}" 2>/dev/null || true)
+  if [[ -n "$TEAM_DATA" ]]; then
+    TEMPLATE_ID=$(echo "$TEAM_DATA" | jq -r '.data.templateId // empty' 2>/dev/null || true)
+    if [[ -n "$TEMPLATE_ID" ]]; then
+      TEMPLATE_DATA=$(api_call GET "/templates/${TEMPLATE_ID}" 2>/dev/null || true)
+      if [[ -n "$TEMPLATE_DATA" ]]; then
+        TEMPLATE_PIPELINE=$(echo "$TEMPLATE_DATA" | jq -r '
+          .data.verificationPipeline.steps // [] |
+          map("- " + (.method // "check") + ": " + (.description // .name // "unnamed step")) |
+          join("\n")
+        ' 2>/dev/null || true)
+      fi
+    fi
+  fi
+fi
+
+# --- Output context for the runtime to generate checklist ---
+# The TL runtime (Claude Code / Gemini CLI) reads this and produces
+# the structured checklist. This is the key "no new LLM layer" design.
+
+cat << CHECKLIST_PROMPT
+
+## Acceptance Checklist Design
+
+You are designing an acceptance checklist for this objective BEFORE execution begins.
+This checklist will be sent to your superior (Orchestrator) for approval.
+Once approved, you will use it to verify workers' output after task completion.
+
+### Objective
+${OBJECTIVE}
+
+### Mission Success Criteria (align with these)
+${MISSION_CRITERIA:-No mission linked — design criteria based on the objective itself.}
+
+### Team Verification Pipeline (baseline checks)
+${TEMPLATE_PIPELINE:-No template pipeline — design checks from scratch.}
+
+### Instructions
+
+Design a verification checklist with 3-8 items. Each item should be:
+- **Concrete and measurable** — not vague ("good code" is bad, "all tests pass" is good)
+- **Aligned with Mission criteria** if available
+- **Categorized**: functionality, quality, security, performance, documentation
+
+For each item, specify:
+- \`id\`: unique identifier (e.g., "chk-1")
+- \`category\`: functionality | quality | security | performance | documentation
+- \`description\`: what is being verified
+- \`type\`: "command" (automated check) or "manual" (TL judgment)
+- \`command\`: shell command to run (only for type=command)
+- \`critical\`: true if this is a must-pass item, false if nice-to-have
+
+Output valid JSON matching this schema:
+\`\`\`json
+{
+  "taskId": "${TASK_ID}",
+  "objective": "${OBJECTIVE}",
+  "status": "pending_approval",
+  "createdBy": "${CREWLY_SESSION_NAME:-tl}",
+  "createdAt": "$(date -u +%Y-%m-%dT%H:%M:%SZ)",
+  "items": [
+    {
+      "id": "chk-1",
+      "category": "functionality",
+      "description": "Description of what to verify",
+      "type": "command",
+      "command": "npm test",
+      "critical": true
+    }
+  ]
+}
+\`\`\`
+
+After generating the JSON, save it and submit for approval:
+\`\`\`bash
+# Save checklist
+cat > "${PROJECT_PATH}/.crewly/tasks/checklist-${TASK_ID}.json" << 'CHECKLIST_EOF'
+<YOUR_JSON_OUTPUT>
+CHECKLIST_EOF
+
+# Submit for approval
+curl -s -X POST "${CREWLY_API_URL}/api/task-management/${TASK_ID}/checklist" \\
+  -H "Content-Type: application/json" \\
+  -d @"${PROJECT_PATH}/.crewly/tasks/checklist-${TASK_ID}.json"
+\`\`\`
+
+Then notify your superior:
+"I've designed the acceptance checklist for '${OBJECTIVE}'. Please review and approve before I proceed with task decomposition."
+
+**Do NOT start decompose-goal or delegate-task until the checklist is approved.**
+
+CHECKLIST_PROMPT
+
+echo '{"success":true,"message":"Checklist design context provided to runtime","taskId":"'"${TASK_ID}"'"}'

package/config/skills/team-leader/verify-output/execute.sh

@@ -21,6 +21,7 @@ WORKER_ID=$(printf '%s' "$INPUT" | jq -r '.workerId // empty')
 TEAM_ID=$(printf '%s' "$INPUT" | jq -r '.teamId // empty')
 PROJECT_PATH=$(printf '%s' "$INPUT" | jq -r '.projectPath // empty')
 TEMPLATE_ID=$(printf '%s' "$INPUT" | jq -r '.templateId // empty')
+CHECKLIST_PATH=$(printf '%s' "$INPUT" | jq -r '.checklistPath // empty')
 CHECKS=$(printf '%s' "$INPUT" | jq -c '.checks // []')
 
 # At least taskPath or taskId is needed
@@ -44,6 +45,47 @@ if [ -n "$TASK_ID" ]; then
   [ -z "$TASK_OUTPUT" ] && TASK_OUTPUT="$TASK_OUTPUT_FROM_ID"
 fi
 
+# =============================================================================
+# Pre-approved checklist loading (from design-checklist skill)
+# =============================================================================
+
+# If checklistPath is provided, load pre-approved checklist items as checks.
+# This takes priority over template pipeline and inline checks.
+if [ -n "$CHECKLIST_PATH" ] && [ -f "$CHECKLIST_PATH" ]; then
+  CHECKLIST_DATA=$(cat "$CHECKLIST_PATH" 2>/dev/null || echo '{}')
+  CHECKLIST_STATUS=$(echo "$CHECKLIST_DATA" | jq -r '.status // "unknown"' 2>/dev/null || true)
+
+  if [ "$CHECKLIST_STATUS" = "approved" ]; then
+    # Convert checklist items to verification checks
+    CHECKS=$(echo "$CHECKLIST_DATA" | jq -c '
+      [.items[] | {
+        name: .id,
+        type: .type,
+        command: (.command // empty),
+        pattern: (.pattern // empty),
+        description: .description,
+        critical: (.critical // false)
+      }]
+    ' 2>/dev/null || echo '[]')
+
+    PASS_POLICY=$(echo "$CHECKLIST_DATA" | jq -r '.passPolicy // "critical_only"' 2>/dev/null || echo "critical_only")
+  else
+    echo '{"error":"Checklist exists but is not approved (status: '"$CHECKLIST_STATUS"'). Approve first via POST /api/task-management/'$TASK_ID'/checklist/approve"}' >&2
+    # Fall through to template/inline checks
+  fi
+
+# If no checklistPath but taskId, try to find checklist automatically
+elif [ -n "$TASK_ID" ] && [ -n "$PROJECT_PATH" ]; then
+  AUTO_CHECKLIST="${PROJECT_PATH}/.crewly/tasks/checklist-${TASK_ID}.json"
+  if [ -f "$AUTO_CHECKLIST" ]; then
+    CHECKLIST_STATUS=$(jq -r '.status // "unknown"' "$AUTO_CHECKLIST" 2>/dev/null || true)
+    if [ "$CHECKLIST_STATUS" = "approved" ]; then
+      CHECKS=$(jq -c '[.items[] | {name: .id, type: .type, command: (.command // empty), pattern: (.pattern // empty), description: .description, critical: (.critical // false)}]' "$AUTO_CHECKLIST" 2>/dev/null || echo '[]')
+      PASS_POLICY=$(jq -r '.passPolicy // "critical_only"' "$AUTO_CHECKLIST" 2>/dev/null || echo "critical_only")
+    fi
+  fi
+fi
+
 # =============================================================================
 # Pipeline loading: convert template pipeline steps to checks
 # =============================================================================

package/config/templates/agent-gemini-md.md

@@ -17,7 +17,9 @@ You are running inside Crewly, a multi-agent orchestration platform.
 2. **Always follow the Code Commit SOP** (9 steps, 3 review rounds) when the team has this norm
 3. **Always write tests** alongside code — one source file = one test file, co-located
 4. **Never run destructive git operations** (checkout --, reset --hard) without stashing first
-5. **Follow project coding standards** defined in CLAUDE.md (TypeScript strict, no hardcoded values, JSDoc comments)
+5. Follow project coding standards defined in CLAUDE.md (TypeScript strict, no hardcoded values, JSDoc comments)
+6. **CRITICAL: Manual Publishing Only** — ALL content publishing on ALL platforms (X, LinkedIn, XHS, etc.) must be done manually by Steve. Agents MUST NOT publish directly via remote-browser or any other tool. Only delivery of content packages to Steve via Slack is allowed. Refer to `config/domain-sops/content-publishing-policy.sop.md`.
+
 
 ## Gemini CLI Notes
 

package/config/templates/ai-video-social-team.json

@@ -0,0 +1,22 @@
+{
+  "id": "ai-video-social-team",
+  "name": "AI Video Social Team",
+  "description": "Scriptwriter + Video Producer + Distribution Specialist for creating automated social media videos using Remotion. Optimized for short-form video platforms.",
+  "members": [
+    {
+      "name": "Video Scriptwriter",
+      "role": "content-writer",
+      "systemPrompt": "You are a video scriptwriter. Your goal is to write concise, high-impact scripts for short-form social media videos. Structure your output into clear slides or scenes that fit the Remotion 'text-slides' or 'launch' templates. Focus on retention, hooks, and clear messaging."
+    },
+    {
+      "name": "Video Producer",
+      "role": "video-producer",
+      "systemPrompt": "You are a video producer specializing in Remotion automation. Use the 'remotion-video' skill to turn scripts into MP4 videos. Choose appropriate templates (launch, text-slides, announcement) based on the content. Handle visual styling (colors, branding) and ensure the output video is ready for distribution."
+    },
+    {
+      "name": "Social Growth Specialist",
+      "role": "distribution-growth",
+      "systemPrompt": "You are a social growth specialist. Manage the distribution of AI-generated videos across platforms like TikTok, XHS, and Reels. Research trending hashtags, optimize descriptions, and engage with the community to drive reach and follower growth. Track performance and feedback to improve future content."
+    }
+  ]
+}

package/config/templates/broker-squad-v1.json

@@ -0,0 +1,22 @@
+{
+  "id": "broker-squad-v1",
+  "name": "Insurance Agency Broker Squad",
+  "description": "Insurance data analyst + Customer Success + Compliance for independent insurance agencies. Handles policy comparison, renewals, and regulatory monitoring.",
+  "members": [
+    {
+      "name": "Insurance Analyst",
+      "role": "data-analyst",
+      "systemPrompt": "You are an insurance analyst. Compare policies, assess risk, and analyze market trends. Help agents find the best coverage for clients."
+    },
+    {
+      "name": "Renewal Specialist",
+      "role": "customer-success",
+      "systemPrompt": "You are a customer success specialist focusing on insurance renewals. Notify clients of upcoming renewals, handle basic inquiries, and assist with onboarding."
+    },
+    {
+      "name": "Compliance Agent",
+      "role": "compliance-officer",
+      "systemPrompt": "You are a compliance officer for an insurance agency. Monitor state regulations, audit documentation for errors, and ensure all processes meet industry standards."
+    }
+  ]
+}

package/config/templates/customer-loyalty-team.json

@@ -0,0 +1,44 @@
+{
+  "id": "customer-loyalty-team",
+  "name": "Customer Loyalty & Success Team",
+  "description": "Premium support team focused on turning tickets into loyalty. Uses radical empathy and proactive retention strategies.",
+  "version": "1.0.0",
+  "category": "support",
+  "targetVertical": "SaaS / Agencies",
+  "tags": ["support", "success", "loyalty", "retention"],
+  "hierarchical": true,
+  "roles": [
+    {
+      "role": "success-manager",
+      "label": "Customer Success Lead",
+      "expertId": "empathetic-resolver",
+      "domainSOP": "customer-onboarding",
+      "defaultName": "Hope",
+      "count": 1,
+      "hierarchyLevel": 1,
+      "canDelegate": true,
+      "defaultSkills": [
+        "delegate-task",
+        "verify-output",
+        "sentiment-analysis",
+        "retention-strategy",
+        "report-status"
+      ]
+    },
+    {
+      "role": "support-agent",
+      "label": "Support Specialist",
+      "defaultName": "Sam",
+      "count": 2,
+      "hierarchyLevel": 2,
+      "reportsTo": "success-manager",
+      "defaultSkills": [
+        "ticket-resolution",
+        "brand-voice-alignment",
+        "complete-task",
+        "request-help"
+      ]
+    }
+  ],
+  "mission": "Provide world-class support that reduces churn and increases customer lifetime value."
+}

package/config/templates/customer-ops-team.json

@@ -0,0 +1,22 @@
+{
+  "id": "customer-ops-team",
+  "name": "Customer Feedback & Ops Team",
+  "description": "Feedback Analyst + Ops Specialist + Customer Advocate for managing customer satisfaction and system reliability. Uses AI to analyze sentiment and automate support workflows.",
+  "members": [
+    {
+      "name": "Feedback Analyst",
+      "role": "data-analyst",
+      "systemPrompt": "You are a feedback analyst. Use the 'feedback-analyzer' skill to extract sentiment, topics, and priority from customer messages. Categorize feedback into actionable items and identify recurring pain points to share with the team."
+    },
+    {
+      "name": "Ops Specialist",
+      "role": "ops-engineer",
+      "systemPrompt": "You are an operations specialist. Monitor system health and performance. Coordinate with the feedback analyst to correlate customer reports with system logs or metrics. Focus on identifying and resolving technical bottlenecks."
+    },
+    {
+      "name": "Customer Advocate",
+      "role": "customer-support",
+      "systemPrompt": "You are a customer advocate. Take analyzed feedback and operational status to draft empathetic, helpful responses to customers using the 'email-responder' skill. Prioritize issues for the product team based on customer impact."
+    }
+  ]
+}

package/config/templates/dtc-viral-content-team.json

@@ -0,0 +1,58 @@
+{
+  "id": "dtc-viral-content-team",
+  "name": "DTC Viral Content Team",
+  "description": "High-conversion content team for solopreneurs and Shopify brands. Focused on viral hooks, scroll-stopping creative, and performance data.",
+  "version": "1.0.0",
+  "category": "marketing",
+  "targetVertical": "E-commerce / DTC",
+  "tags": ["dtc", "viral", "content", "shopify", "tiktok"],
+  "hierarchical": true,
+  "roles": [
+    {
+      "role": "content-lead",
+      "label": "Content Strategy Lead",
+      "expertId": "viral-alchemist",
+      "domainSOP": "content-production-pipeline",
+      "defaultName": "Vee",
+      "count": 1,
+      "hierarchyLevel": 1,
+      "canDelegate": true,
+      "defaultSkills": [
+        "decompose-goal",
+        "delegate-task",
+        "verify-output",
+        "content-calendar",
+        "report-status"
+      ]
+    },
+    {
+      "role": "writer",
+      "label": "Viral Copywriter",
+      "defaultName": "Ace",
+      "count": 1,
+      "hierarchyLevel": 2,
+      "reportsTo": "content-lead",
+      "defaultSkills": [
+        "social-media-post",
+        "conversion-copy",
+        "complete-task",
+        "request-help"
+      ]
+    },
+    {
+      "role": "creator",
+      "label": "UGC Content Creator",
+      "defaultName": "Coco",
+      "count": 1,
+      "hierarchyLevel": 2,
+      "reportsTo": "content-lead",
+      "defaultSkills": [
+        "image-generation",
+        "video-scripting",
+        "complete-task",
+        "request-help"
+      ]
+    }
+  ],
+  "mission": "Generate high-conversion viral content that drives traffic and sales for DTC brands."
+}

package/config/templates/expert-innovation-team.json

@@ -0,0 +1,60 @@
+{
+  "id": "expert-innovation-team",
+  "name": "Expert Innovation Team (Pro)",
+  "description": "High-performance team guided by the world's greatest thinkers. Combines visionary design with radical engineering first principles.",
+  "version": "1.0.0",
+  "category": "innovation",
+  "targetVertical": "R&D / New Product Development",
+  "tags": ["innovation", "strategy", "engineering", "first-principles"],
+  "hierarchical": true,
+  "roles": [
+    {
+      "role": "strategist",
+      "label": "Visionary Strategist",
+      "expertId": "steve-jobs",
+      "domainSOP": "innovation-strategy",
+      "defaultName": "Steve",
+      "count": 1,
+      "hierarchyLevel": 1,
+      "canDelegate": true,
+      "defaultSkills": [
+        "decompose-goal",
+        "delegate-task",
+        "design-review",
+        "market-analysis",
+        "report-status"
+      ]
+    },
+    {
+      "role": "engineer",
+      "label": "Radical Engineer",
+      "expertId": "elon-musk",
+      "reportsTo": "strategist",
+      "defaultName": "Elon",
+      "count": 1,
+      "hierarchyLevel": 2,
+      "defaultSkills": [
+        "first-principles-analysis",
+        "technical-optimization",
+        "automation-scripting",
+        "complete-task"
+      ]
+    },
+    {
+      "role": "allocator",
+      "label": "Capital Allocator",
+      "expertId": "charlie-munger",
+      "reportsTo": "strategist",
+      "defaultName": "Charlie",
+      "count": 1,
+      "hierarchyLevel": 2,
+      "defaultSkills": [
+        "risk-assessment",
+        "mental-model-audit",
+        "inverted-problem-solving",
+        "complete-task"
+      ]
+    }
+  ],
+  "mission": "Apply world-class mental models to solve impossible problems and build insanely great products."
+}