crewly 1.2.3 → 1.2.6

package/config/skills/team-leader/start-agent/execute.sh

@@ -0,0 +1,39 @@
+#!/bin/bash
+# Start a worker agent within this Team Leader's subordinate scope.
+# Validates hierarchy (worker.parentMemberId == TL.memberId) before starting.
+set -euo pipefail
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+source "${SCRIPT_DIR}/../_common/lib.sh"
+
+INPUT="${1:-}"
+[ -z "$INPUT" ] && error_exit "Usage: execute.sh '{\"teamId\":\"team-uuid\",\"memberId\":\"member-uuid\",\"tlMemberId\":\"tl-member-id\"}'"
+
+TEAM_ID=$(echo "$INPUT" | jq -r '.teamId // empty')
+MEMBER_ID=$(echo "$INPUT" | jq -r '.memberId // empty')
+TL_MEMBER_ID=$(echo "$INPUT" | jq -r '.tlMemberId // empty')
+require_param "teamId" "$TEAM_ID"
+require_param "memberId" "$MEMBER_ID"
+require_param "tlMemberId" "$TL_MEMBER_ID"
+
+# Validate hierarchy: target worker must be a subordinate of this TL
+TEAM_DATA=$(api_call GET "/teams/${TEAM_ID}" 2>/dev/null || echo '{}')
+TEAM_SUCCESS=$(echo "$TEAM_DATA" | jq -r '.success // false' 2>/dev/null || echo "false")
+
+if [ "$TEAM_SUCCESS" != "true" ]; then
+  error_exit "Failed to fetch team data for team ${TEAM_ID}"
+fi
+
+# Find the target member and check parentMemberId
+WORKER_PARENT=$(echo "$TEAM_DATA" | jq -r --arg mid "$MEMBER_ID" \
+  '.data.members[] | select(.id == $mid) | .parentMemberId // empty' 2>/dev/null || true)
+
+if [ -z "$WORKER_PARENT" ]; then
+  error_exit "Member ${MEMBER_ID} not found in team ${TEAM_ID} or has no parentMemberId set"
+fi
+
+if [ "$WORKER_PARENT" != "$TL_MEMBER_ID" ]; then
+  error_exit "Hierarchy violation: member ${MEMBER_ID} (parentMemberId=${WORKER_PARENT}) is not a subordinate of TL ${TL_MEMBER_ID}"
+fi
+
+# Hierarchy validated — start the agent
+api_call POST "/teams/${TEAM_ID}/members/${MEMBER_ID}/start"

package/config/skills/team-leader/start-agent/instructions.md

@@ -0,0 +1,48 @@
+# Start Agent (TL Version)
+
+Starts a worker agent within the Team Leader's subordinate scope. Validates hierarchy before starting — the target worker's `parentMemberId` must match the TL's `memberId`.
+
+## When to Use
+
+- When a worker needs to be activated for task assignment
+- After a worker was previously stopped and needs to be restarted
+- When scaling up the sub-team for a new objective
+
+## Usage
+
+```bash
+bash {{TL_SKILLS_PATH}}/start-agent/execute.sh '{"teamId":"{{TEAM_ID}}","memberId":"worker-member-uuid","tlMemberId":"{{MEMBER_ID}}"}'
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `teamId` | Yes | The team's UUID |
+| `memberId` | Yes | The target worker's member UUID |
+| `tlMemberId` | Yes | The TL's own member ID for hierarchy validation |
+
+## Hierarchy Validation
+
+The script fetches team data and validates:
+- The target member exists in the team
+- The member's `parentMemberId` matches the TL's `memberId`
+
+If validation fails, the start is rejected with a hierarchy violation error. TLs can only start their own subordinates — not agents in other teams or under other TLs.
+
+## Differences from Orchestrator start-agent
+
+| Aspect | Orchestrator | Team Leader |
+|--------|-------------|-------------|
+| Scope | Any agent in any team | Only subordinates |
+| Hierarchy check | None | Validates parentMemberId |
+| Extra parameter | None | `tlMemberId` required |
+
+## Output
+
+JSON confirmation with agent startup status, same format as orchestrator start-agent.
+
+## Related Skills
+
+- `stop-agent` — Stop a subordinate worker
+- `delegate-task` — Assign tasks to workers after starting them

package/config/skills/team-leader/start-agent/skill.json

@@ -0,0 +1,20 @@
+{
+  "id": "tl-start-agent",
+  "name": "Start Agent (TL)",
+  "description": "Start a worker agent within the Team Leader's subordinate scope. Validates that the target worker's parentMemberId matches the TL's memberId before starting.",
+  "category": "management",
+  "skillType": "claude-skill",
+  "promptFile": "instructions.md",
+  "execution": {
+    "type": "script",
+    "script": {
+      "file": "execute.sh",
+      "interpreter": "bash",
+      "timeoutMs": 60000
+    }
+  },
+  "assignableRoles": ["team-leader"],
+  "triggers": ["start agent", "start worker", "activate worker", "boot worker"],
+  "tags": ["agent", "management", "lifecycle", "hierarchy"],
+  "version": "1.0.0"
+}

package/config/skills/team-leader/stop-agent/execute.sh

@@ -0,0 +1,39 @@
+#!/bin/bash
+# Stop a worker agent within this Team Leader's subordinate scope.
+# Validates hierarchy (worker.parentMemberId == TL.memberId) before stopping.
+set -euo pipefail
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+source "${SCRIPT_DIR}/../_common/lib.sh"
+
+INPUT="${1:-}"
+[ -z "$INPUT" ] && error_exit "Usage: execute.sh '{\"teamId\":\"team-uuid\",\"memberId\":\"member-uuid\",\"tlMemberId\":\"tl-member-id\"}'"
+
+TEAM_ID=$(echo "$INPUT" | jq -r '.teamId // empty')
+MEMBER_ID=$(echo "$INPUT" | jq -r '.memberId // empty')
+TL_MEMBER_ID=$(echo "$INPUT" | jq -r '.tlMemberId // empty')
+require_param "teamId" "$TEAM_ID"
+require_param "memberId" "$MEMBER_ID"
+require_param "tlMemberId" "$TL_MEMBER_ID"
+
+# Validate hierarchy: target worker must be a subordinate of this TL
+TEAM_DATA=$(api_call GET "/teams/${TEAM_ID}" 2>/dev/null || echo '{}')
+TEAM_SUCCESS=$(echo "$TEAM_DATA" | jq -r '.success // false' 2>/dev/null || echo "false")
+
+if [ "$TEAM_SUCCESS" != "true" ]; then
+  error_exit "Failed to fetch team data for team ${TEAM_ID}"
+fi
+
+# Find the target member and check parentMemberId
+WORKER_PARENT=$(echo "$TEAM_DATA" | jq -r --arg mid "$MEMBER_ID" \
+  '.data.members[] | select(.id == $mid) | .parentMemberId // empty' 2>/dev/null || true)
+
+if [ -z "$WORKER_PARENT" ]; then
+  error_exit "Member ${MEMBER_ID} not found in team ${TEAM_ID} or has no parentMemberId set"
+fi
+
+if [ "$WORKER_PARENT" != "$TL_MEMBER_ID" ]; then
+  error_exit "Hierarchy violation: member ${MEMBER_ID} (parentMemberId=${WORKER_PARENT}) is not a subordinate of TL ${TL_MEMBER_ID}"
+fi
+
+# Hierarchy validated — stop the agent
+api_call POST "/teams/${TEAM_ID}/members/${MEMBER_ID}/stop"

package/config/skills/team-leader/stop-agent/instructions.md

@@ -0,0 +1,49 @@
+# Stop Agent (TL Version)
+
+Stops a worker agent within the Team Leader's subordinate scope. Validates hierarchy before stopping — the target worker's `parentMemberId` must match the TL's `memberId`.
+
+## When to Use
+
+- When a worker is no longer needed for current objectives
+- When scaling down the sub-team after task completion
+- When a worker is stuck and needs to be restarted (stop then start)
+
+## Usage
+
+```bash
+bash {{TL_SKILLS_PATH}}/stop-agent/execute.sh '{"teamId":"{{TEAM_ID}}","memberId":"worker-member-uuid","tlMemberId":"{{MEMBER_ID}}"}'
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `teamId` | Yes | The team's UUID |
+| `memberId` | Yes | The target worker's member UUID |
+| `tlMemberId` | Yes | The TL's own member ID for hierarchy validation |
+
+## Hierarchy Validation
+
+The script fetches team data and validates:
+- The target member exists in the team
+- The member's `parentMemberId` matches the TL's `memberId`
+
+If validation fails, the stop is rejected with a hierarchy violation error. TLs can only stop their own subordinates — not agents in other teams or under other TLs.
+
+## Differences from Orchestrator stop-agent
+
+| Aspect | Orchestrator | Team Leader |
+|--------|-------------|-------------|
+| Scope | Any agent in any team | Only subordinates |
+| Hierarchy check | None | Validates parentMemberId |
+| Extra parameter | None | `tlMemberId` required |
+
+## Output
+
+JSON confirmation with agent shutdown status, same format as orchestrator stop-agent.
+
+## Related Skills
+
+- `start-agent` — Start a subordinate worker
+- `delegate-task` — Assign tasks to running workers
+- `handle-failure` — Handle worker failures (may need stop + restart)

package/config/skills/team-leader/stop-agent/skill.json

@@ -0,0 +1,20 @@
+{
+  "id": "tl-stop-agent",
+  "name": "Stop Agent (TL)",
+  "description": "Stop a worker agent within the Team Leader's subordinate scope. Validates that the target worker's parentMemberId matches the TL's memberId before stopping.",
+  "category": "management",
+  "skillType": "claude-skill",
+  "promptFile": "instructions.md",
+  "execution": {
+    "type": "script",
+    "script": {
+      "file": "execute.sh",
+      "interpreter": "bash",
+      "timeoutMs": 30000
+    }
+  },
+  "assignableRoles": ["team-leader"],
+  "triggers": ["stop agent", "stop worker", "deactivate worker", "shutdown worker"],
+  "tags": ["agent", "management", "lifecycle", "hierarchy"],
+  "version": "1.0.0"
+}

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

@@ -0,0 +1,296 @@
+#!/bin/bash
+# Verify a completed task's output against the team's verification pipeline.
+# Reads the task output and runs verification steps based on the team template.
+#
+# Supports two modes:
+# 1. Explicit checks: pass checks[] array directly (legacy behavior)
+# 2. Template pipeline: pass templateId to load verification steps from template
+#
+# When templateId is provided and checks is empty, pipeline steps are loaded
+# from the template API and executed according to the passPolicy.
+set -euo pipefail
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+source "${SCRIPT_DIR}/../_common/lib.sh"
+
+INPUT="${1:-}"
+[ -z "$INPUT" ] && error_exit "Usage: execute.sh '{\"taskId\":\"...\",\"taskPath\":\"...\",\"workerId\":\"...\",\"teamId\":\"...\",\"projectPath\":\"...\",\"templateId\":\"dev-fullstack\",\"checks\":[...]}'"
+
+TASK_ID=$(echo "$INPUT" | jq -r '.taskId // empty')
+TASK_PATH=$(echo "$INPUT" | jq -r '.taskPath // empty')
+WORKER_ID=$(echo "$INPUT" | jq -r '.workerId // empty')
+TEAM_ID=$(echo "$INPUT" | jq -r '.teamId // empty')
+PROJECT_PATH=$(echo "$INPUT" | jq -r '.projectPath // empty')
+TEMPLATE_ID=$(echo "$INPUT" | jq -r '.templateId // empty')
+CHECKS=$(echo "$INPUT" | jq -c '.checks // []')
+
+# At least taskPath or taskId is needed
+if [ -z "$TASK_PATH" ] && [ -z "$TASK_ID" ]; then
+  error_exit "Either taskPath or taskId is required"
+fi
+
+# Read task output if taskPath is provided
+TASK_OUTPUT=""
+if [ -n "$TASK_PATH" ]; then
+  TASK_READ_BODY=$(jq -n --arg taskPath "$TASK_PATH" '{taskPath: $taskPath}')
+  TASK_DATA=$(api_call POST "/task-management/read-task" "$TASK_READ_BODY" 2>/dev/null || echo '{}')
+  TASK_OUTPUT=$(echo "$TASK_DATA" | jq -r '.data.content // empty' 2>/dev/null || true)
+fi
+
+# If taskId is provided, try to get output from task tracking
+if [ -n "$TASK_ID" ]; then
+  OUTPUT_BODY=$(jq -n --arg taskId "$TASK_ID" '{taskId: $taskId}')
+  OUTPUT_DATA=$(api_call POST "/task-management/get-output" "$OUTPUT_BODY" 2>/dev/null || echo '{}')
+  TASK_OUTPUT_FROM_ID=$(echo "$OUTPUT_DATA" | jq -r '.data.output // empty' 2>/dev/null || true)
+  [ -z "$TASK_OUTPUT" ] && TASK_OUTPUT="$TASK_OUTPUT_FROM_ID"
+fi
+
+# =============================================================================
+# Pipeline loading: convert template pipeline steps to checks
+# =============================================================================
+
+PASS_POLICY="all"
+MAX_RETRIES=2
+CHECK_COUNT=$(echo "$CHECKS" | jq 'length')
+
+if [ "$CHECK_COUNT" = "0" ] && [ -n "$TEMPLATE_ID" ]; then
+  # Load pipeline from template API
+  TEMPLATE_DATA=$(api_call GET "/templates/${TEMPLATE_ID}" 2>/dev/null || echo '{}')
+  TEMPLATE_SUCCESS=$(echo "$TEMPLATE_DATA" | jq -r '.success // false' 2>/dev/null || echo "false")
+
+  if [ "$TEMPLATE_SUCCESS" = "true" ]; then
+    PIPELINE=$(echo "$TEMPLATE_DATA" | jq -c '.data.verificationPipeline // {}' 2>/dev/null || echo '{}')
+    PASS_POLICY=$(echo "$PIPELINE" | jq -r '.passPolicy // "all"')
+    MAX_RETRIES=$(echo "$PIPELINE" | jq -r '.maxRetries // 2')
+    STEPS=$(echo "$PIPELINE" | jq -c '.steps // []')
+    STEP_COUNT=$(echo "$STEPS" | jq 'length')
+
+    # Convert pipeline steps to checks format
+    CHECKS="[]"
+    for i in $(seq 0 $((STEP_COUNT - 1))); do
+      STEP_ID=$(echo "$STEPS" | jq -r ".[$i].id // \"step-${i}\"")
+      STEP_NAME=$(echo "$STEPS" | jq -r ".[$i].name // \"Step ${i}\"")
+      STEP_METHOD=$(echo "$STEPS" | jq -r ".[$i].method // \"manual_review\"")
+      STEP_CRITICAL=$(echo "$STEPS" | jq -r ".[$i].critical // false")
+      STEP_CONFIG=$(echo "$STEPS" | jq -c ".[$i].config // {}")
+
+      case "$STEP_METHOD" in
+        quality_gates)
+          # Map quality gates to command checks using the gates config
+          GATES=$(echo "$STEP_CONFIG" | jq -r '.gates // [] | .[]' 2>/dev/null || true)
+          if [ -n "$GATES" ] && [ -n "$PROJECT_PATH" ]; then
+            for GATE in $GATES; do
+              GATE_CMD=""
+              case "$GATE" in
+                typecheck) GATE_CMD="npm run typecheck 2>&1 || npx tsc --noEmit 2>&1" ;;
+                tests)     GATE_CMD="npm test 2>&1" ;;
+                build)     GATE_CMD="npm run build 2>&1" ;;
+                lint)      GATE_CMD="npm run lint 2>&1" ;;
+              esac
+              if [ -n "$GATE_CMD" ]; then
+                CHECKS=$(echo "$CHECKS" | jq \
+                  --arg name "${STEP_ID}-${GATE}" \
+                  --arg command "$GATE_CMD" \
+                  --arg critical "$STEP_CRITICAL" \
+                  '. + [{name: $name, command: $command, type: "command", critical: ($critical == "true")}]')
+              fi
+            done
+          else
+            # No gates specified — default to build check
+            CHECKS=$(echo "$CHECKS" | jq \
+              --arg name "$STEP_ID" \
+              --arg command "npm run build 2>&1" \
+              --arg critical "$STEP_CRITICAL" \
+              '. + [{name: $name, command: $command, type: "command", critical: ($critical == "true")}]')
+          fi
+          ;;
+        e2e_test)
+          # Map to e2e test command
+          FRAMEWORK=$(echo "$STEP_CONFIG" | jq -r '.framework // "playwright"')
+          TEST_DIR=$(echo "$STEP_CONFIG" | jq -r '.testDir // "tests/e2e"')
+          CHECKS=$(echo "$CHECKS" | jq \
+            --arg name "$STEP_ID" \
+            --arg command "npx ${FRAMEWORK} test ${TEST_DIR} 2>&1" \
+            --arg critical "$STEP_CRITICAL" \
+            '. + [{name: $name, command: $command, type: "command", critical: ($critical == "true")}]')
+          ;;
+        code_review|screenshot_review|gemini_vision|content_check|fact_check|source_verify|data_validate|browser_test|custom_script|manual_review)
+          # These methods require TL judgment — record as manual review steps
+          CHECKS=$(echo "$CHECKS" | jq \
+            --arg name "$STEP_ID" \
+            --arg desc "$STEP_NAME" \
+            --arg method "$STEP_METHOD" \
+            --arg critical "$STEP_CRITICAL" \
+            '. + [{name: $name, type: "manual", method: $method, description: $desc, critical: ($critical == "true")}]')
+          ;;
+        *)
+          # Unknown method — skip
+          CHECKS=$(echo "$CHECKS" | jq \
+            --arg name "$STEP_ID" \
+            --arg method "$STEP_METHOD" \
+            --arg critical "$STEP_CRITICAL" \
+            '. + [{name: $name, type: "skip", method: $method, critical: ($critical == "true")}]')
+          ;;
+      esac
+    done
+
+    CHECK_COUNT=$(echo "$CHECKS" | jq 'length')
+  fi
+fi
+
+# =============================================================================
+# Run verification checks
+# =============================================================================
+
+RESULTS="[]"
+TOTAL_PASSED=0
+TOTAL_FAILED=0
+CRITICAL_PASSED=0
+CRITICAL_FAILED=0
+FAILED_STEPS="[]"
+
+if [ "$CHECK_COUNT" = "0" ]; then
+  # No checks at all — report a pass-through verification
+  RESULTS=$(jq -n '[{
+    "name": "manual-review",
+    "passed": true,
+    "critical": false,
+    "message": "No automated checks configured. Task output available for manual review."
+  }]')
+  TOTAL_PASSED=1
+else
+  for i in $(seq 0 $((CHECK_COUNT - 1))); do
+    CHECK_NAME=$(echo "$CHECKS" | jq -r ".[$i].name // \"check-${i}\"")
+    CHECK_CMD=$(echo "$CHECKS" | jq -r ".[$i].command // empty")
+    CHECK_TYPE=$(echo "$CHECKS" | jq -r ".[$i].type // \"command\"")
+    CHECK_CRITICAL=$(echo "$CHECKS" | jq -r ".[$i].critical // false")
+
+    if [ "$CHECK_TYPE" = "command" ] && [ -n "$CHECK_CMD" ] && [ -n "$PROJECT_PATH" ]; then
+      # Execute the verification command in the project directory
+      CHECK_OUTPUT=""
+      CHECK_PASSED=true
+      CHECK_OUTPUT=$(cd "$PROJECT_PATH" && eval "$CHECK_CMD" 2>&1) || CHECK_PASSED=false
+
+      # Truncate output to avoid huge payloads
+      CHECK_OUTPUT=$(echo "$CHECK_OUTPUT" | tail -50)
+
+      if [ "$CHECK_PASSED" = "true" ]; then
+        TOTAL_PASSED=$((TOTAL_PASSED + 1))
+        [ "$CHECK_CRITICAL" = "true" ] && CRITICAL_PASSED=$((CRITICAL_PASSED + 1))
+      else
+        TOTAL_FAILED=$((TOTAL_FAILED + 1))
+        [ "$CHECK_CRITICAL" = "true" ] && CRITICAL_FAILED=$((CRITICAL_FAILED + 1))
+        FAILED_STEPS=$(echo "$FAILED_STEPS" | jq --arg name "$CHECK_NAME" '. + [$name]')
+      fi
+
+      RESULTS=$(echo "$RESULTS" | jq \
+        --arg name "$CHECK_NAME" \
+        --arg passed "$CHECK_PASSED" \
+        --arg output "$CHECK_OUTPUT" \
+        --arg critical "$CHECK_CRITICAL" \
+        '. + [{name: $name, passed: ($passed == "true"), critical: ($critical == "true"), output: $output}]')
+    elif [ "$CHECK_TYPE" = "content-scan" ]; then
+      # Content-based verification (check task output contains expected patterns)
+      CHECK_PATTERN=$(echo "$CHECKS" | jq -r ".[$i].pattern // empty")
+      if [ -n "$CHECK_PATTERN" ] && [ -n "$TASK_OUTPUT" ]; then
+        if echo "$TASK_OUTPUT" | grep -qiE "$CHECK_PATTERN"; then
+          TOTAL_PASSED=$((TOTAL_PASSED + 1))
+          [ "$CHECK_CRITICAL" = "true" ] && CRITICAL_PASSED=$((CRITICAL_PASSED + 1))
+          RESULTS=$(echo "$RESULTS" | jq --arg name "$CHECK_NAME" --arg critical "$CHECK_CRITICAL" \
+            '. + [{name: $name, passed: true, critical: ($critical == "true"), output: "Pattern found"}]')
+        else
+          TOTAL_FAILED=$((TOTAL_FAILED + 1))
+          [ "$CHECK_CRITICAL" = "true" ] && CRITICAL_FAILED=$((CRITICAL_FAILED + 1))
+          FAILED_STEPS=$(echo "$FAILED_STEPS" | jq --arg name "$CHECK_NAME" '. + [$name]')
+          RESULTS=$(echo "$RESULTS" | jq --arg name "$CHECK_NAME" --arg critical "$CHECK_CRITICAL" \
+            '. + [{name: $name, passed: false, critical: ($critical == "true"), output: "Pattern not found"}]')
+        fi
+      else
+        TOTAL_PASSED=$((TOTAL_PASSED + 1))
+        [ "$CHECK_CRITICAL" = "true" ] && CRITICAL_PASSED=$((CRITICAL_PASSED + 1))
+        RESULTS=$(echo "$RESULTS" | jq --arg name "$CHECK_NAME" --arg critical "$CHECK_CRITICAL" \
+          '. + [{name: $name, passed: true, critical: ($critical == "true"), output: "Skipped (no pattern or output)"}]')
+      fi
+    elif [ "$CHECK_TYPE" = "manual" ]; then
+      # Manual review steps — require TL judgment, auto-pass with note
+      CHECK_METHOD=$(echo "$CHECKS" | jq -r ".[$i].method // \"manual_review\"")
+      CHECK_DESC=$(echo "$CHECKS" | jq -r ".[$i].description // \"Manual review required\"")
+      TOTAL_PASSED=$((TOTAL_PASSED + 1))
+      [ "$CHECK_CRITICAL" = "true" ] && CRITICAL_PASSED=$((CRITICAL_PASSED + 1))
+      RESULTS=$(echo "$RESULTS" | jq \
+        --arg name "$CHECK_NAME" \
+        --arg method "$CHECK_METHOD" \
+        --arg desc "$CHECK_DESC" \
+        --arg critical "$CHECK_CRITICAL" \
+        '. + [{name: $name, passed: true, critical: ($critical == "true"), output: ("Requires TL judgment: " + $desc), method: $method, requiresReview: true}]')
+    else
+      # Unknown check type — skip
+      RESULTS=$(echo "$RESULTS" | jq --arg name "$CHECK_NAME" --arg type "$CHECK_TYPE" --arg critical "$CHECK_CRITICAL" \
+        '. + [{name: $name, passed: true, critical: ($critical == "true"), output: ("Skipped: unknown check type " + $type)}]')
+      TOTAL_PASSED=$((TOTAL_PASSED + 1))
+      [ "$CHECK_CRITICAL" = "true" ] && CRITICAL_PASSED=$((CRITICAL_PASSED + 1))
+    fi
+  done
+fi
+
+# =============================================================================
+# Calculate pass/fail based on passPolicy
+# =============================================================================
+
+TOTAL_CHECKS=$((TOTAL_PASSED + TOTAL_FAILED))
+if [ "$TOTAL_CHECKS" -gt 0 ]; then
+  SCORE=$(echo "scale=0; $TOTAL_PASSED * 100 / $TOTAL_CHECKS" | bc)
+else
+  SCORE=100
+fi
+
+# Determine overall pass based on passPolicy
+case "$PASS_POLICY" in
+  critical_only)
+    # Only critical steps must pass
+    PASSED=$( [ "$CRITICAL_FAILED" -eq 0 ] && echo "true" || echo "false" )
+    ;;
+  majority)
+    # >50% of total checks must pass
+    HALF=$(echo "scale=0; $TOTAL_CHECKS / 2" | bc)
+    PASSED=$( [ "$TOTAL_PASSED" -gt "$HALF" ] && echo "true" || echo "false" )
+    ;;
+  all|*)
+    # All checks must pass (default)
+    PASSED=$( [ "$TOTAL_FAILED" -eq 0 ] && echo "true" || echo "false" )
+    ;;
+esac
+
+# Build feedback message
+if [ "$PASSED" = "true" ]; then
+  FEEDBACK="Verification passed (${TOTAL_PASSED}/${TOTAL_CHECKS} checks, policy: ${PASS_POLICY})."
+else
+  FEEDBACK="Verification failed: ${TOTAL_FAILED}/${TOTAL_CHECKS} checks failed (policy: ${PASS_POLICY})."
+fi
+
+# Check if any results require manual TL review
+REQUIRES_REVIEW=$(echo "$RESULTS" | jq '[.[] | select(.requiresReview == true)] | length')
+if [ "$REQUIRES_REVIEW" -gt 0 ]; then
+  FEEDBACK="${FEEDBACK} ${REQUIRES_REVIEW} step(s) require Team Leader review."
+fi
+
+jq -n \
+  --arg passed "$PASSED" \
+  --arg score "$SCORE" \
+  --arg feedback "$FEEDBACK" \
+  --arg passPolicy "$PASS_POLICY" \
+  --argjson failedSteps "$FAILED_STEPS" \
+  --argjson results "$RESULTS" \
+  --arg taskId "$TASK_ID" \
+  --arg workerId "$WORKER_ID" \
+  --arg templateId "$TEMPLATE_ID" \
+  '{
+    passed: ($passed == "true"),
+    score: ($score | tonumber),
+    feedback: $feedback,
+    passPolicy: $passPolicy,
+    failedSteps: $failedSteps,
+    results: $results,
+    taskId: $taskId,
+    workerId: $workerId,
+    templateId: $templateId
+  }'

package/config/skills/team-leader/verify-output/instructions.md

@@ -0,0 +1,122 @@
+# Verify Output
+
+Executes the team's verification pipeline against a completed task. Reads the task output and runs verification checks (build, tests, content scans) based on the team template configuration.
+
+Supports two modes:
+1. **Explicit checks**: Pass `checks[]` array directly with specific verification steps
+2. **Template pipeline**: Pass `templateId` to automatically load verification steps from the team template's `verificationPipeline`
+
+## When to Use
+
+- When a worker reports a task as `done`
+- When `report-status` indicates task completion
+- Before marking a task as verified and reporting to the Orchestrator
+
+## Usage
+
+### With explicit checks (legacy)
+```bash
+bash {{SKILLS_PATH}}/team-leader/verify-output/execute.sh '{"taskId":"task-123","taskPath":"/project/.crewly/tasks/m1/done/task.md","workerId":"worker-1","teamId":"team-123","projectPath":"/path/to/project","checks":[{"name":"build","command":"npm run build"},{"name":"tests","command":"npm test"}]}'
+```
+
+### With template pipeline (recommended)
+```bash
+bash {{SKILLS_PATH}}/team-leader/verify-output/execute.sh '{"taskId":"task-123","taskPath":"/project/.crewly/tasks/m1/done/task.md","workerId":"worker-1","teamId":"team-123","projectPath":"/path/to/project","templateId":"dev-fullstack"}'
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `taskId` | No* | Task ID for tracking lookup |
+| `taskPath` | No* | Absolute path to the task markdown file |
+| `workerId` | No | ID of the worker who completed the task |
+| `teamId` | No | Team ID (for context) |
+| `projectPath` | No | Project directory (required for command-type checks) |
+| `templateId` | No | Template ID to load verification pipeline from |
+| `checks` | No | Array of verification steps (overrides template pipeline) |
+
+*At least one of `taskId` or `taskPath` is required.
+
+## Check Types
+
+### Command checks (default)
+Run a shell command in the project directory and check exit code:
+```json
+{ "name": "build", "type": "command", "command": "npm run build" }
+```
+
+### Content scan checks
+Search task output for a regex pattern:
+```json
+{ "name": "has-tests", "type": "content-scan", "pattern": "test.*pass|coverage.*[89]\\d%" }
+```
+
+### Manual review steps
+Steps that require Team Leader judgment (auto-loaded from template pipeline):
+```json
+{ "name": "code-review", "type": "manual", "method": "code_review", "description": "Review code diff" }
+```
+
+## Template Pipeline Integration
+
+When `templateId` is provided and `checks` is empty, the skill loads the verification pipeline from the template API (`GET /api/templates/:id`) and converts pipeline steps to checks:
+
+| Pipeline Method | Execution |
+|----------------|-----------|
+| `quality_gates` | Runs gate commands (typecheck, tests, build, lint) |
+| `e2e_test` | Runs end-to-end test framework |
+| `code_review` | Marked as manual review for TL |
+| `screenshot_review` | Marked as manual review for TL |
+| `gemini_vision` | Marked as manual review for TL |
+| `content_check` | Marked as manual review for TL |
+| `fact_check` | Marked as manual review for TL |
+| `source_verify` | Marked as manual review for TL |
+| `data_validate` | Marked as manual review for TL |
+| `browser_test` | Marked as manual review for TL |
+| `manual_review` | Marked as manual review for TL |
+| `custom_script` | Marked as manual review for TL |
+
+### Pass Policies
+
+The template's `passPolicy` controls the overall pass/fail determination:
+
+| Policy | Behavior |
+|--------|----------|
+| `all` | All checks must pass (default) |
+| `majority` | More than 50% of checks must pass |
+| `critical_only` | Only critical steps must pass |
+
+## Output
+
+```json
+{
+  "passed": false,
+  "score": 67,
+  "feedback": "Verification failed: 1/3 checks failed (policy: critical_only).",
+  "passPolicy": "critical_only",
+  "failedSteps": ["quality-gates-tests"],
+  "results": [
+    { "name": "quality-gates-build", "passed": true, "critical": true, "output": "..." },
+    { "name": "quality-gates-tests", "passed": false, "critical": true, "output": "3 tests failed..." },
+    { "name": "code-review", "passed": true, "critical": true, "output": "Requires TL judgment: Code Review", "method": "code_review", "requiresReview": true }
+  ],
+  "taskId": "task-123",
+  "workerId": "worker-1",
+  "templateId": "dev-fullstack"
+}
+```
+
+## Decision Flow After Verification
+
+```
+passed: true  → Report success to Orchestrator via aggregate-results
+passed: false → Call handle-failure with the failure details
+requiresReview: true → TL must manually evaluate these steps
+```
+
+## Related Skills
+
+- `handle-failure` — Handle verification failures
+- `aggregate-results` — Include verification results in reports
+- `decompose-goal` — Original task decomposition

package/config/skills/team-leader/verify-output/skill.json

@@ -0,0 +1,20 @@
+{
+  "id": "tl-verify-output",
+  "name": "Verify Output",
+  "description": "Execute the team's verification pipeline against a completed task. Reads verificationPipeline configuration from the team template and runs each verification step sequentially.",
+  "category": "quality",
+  "skillType": "claude-skill",
+  "promptFile": "instructions.md",
+  "execution": {
+    "type": "script",
+    "script": {
+      "file": "execute.sh",
+      "interpreter": "bash",
+      "timeoutMs": 60000
+    }
+  },
+  "assignableRoles": ["team-leader"],
+  "triggers": ["verify output", "check work", "review task", "quality check", "verify task"],
+  "tags": ["verification", "quality", "review", "management"],
+  "version": "1.0.0"
+}