crewly 1.3.31 → 1.4.0

package/config/skills/orchestrator/delegate-task/{instructions.md → SKILL.md}

@@ -1,3 +1,30 @@
+---
+name: Delegate Task
+description: Send a structured task assignment to an agent with priority, context, and optional auto-monitoring. When monitor is provided, automatically subscribes to idle events and schedules fallback checks that are cleaned up on task completion. For formal task tracking, use assign-task instead. For simple messages, use send-message.
+version: 2.0.0
+category: management
+skillType: claude-skill
+assignableRoles:
+  - orchestrator
+triggers:
+  - delegate task
+  - assign work
+  - task agent
+  - delegate with monitoring
+  - send task to agent
+tags:
+  - task
+  - delegation
+  - management
+  - monitoring
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 30000
+---
+
 # Delegate Task
 
 Sends a structured task assignment to an agent. When a `projectPath` is provided, also creates a task MD file in the project's `.crewly/tasks/delegated/in_progress/` directory for tracking.

package/config/skills/orchestrator/delegate-task/execute.sh

@@ -14,9 +14,38 @@ TASK=$(echo "$INPUT" | jq -r '.task // empty')
 PRIORITY=$(echo "$INPUT" | jq -r '.priority // "normal"')
 CONTEXT=$(echo "$INPUT" | jq -r '.context // empty')
 PROJECT_PATH=$(echo "$INPUT" | jq -r '.projectPath // empty')
+# #150: Task type classification — 'technical' tasks can bypass PM routing
+TASK_TYPE=$(echo "$INPUT" | jq -r '.taskType // "general"')
+# #180: Cross-team validation
+TEAM_ID=$(echo "$INPUT" | jq -r '.teamId // empty')
+FORCE_CROSS_TEAM=$(echo "$INPUT" | jq -r '.forceCrossTeam // "false"')
 require_param "to" "$TO"
 require_param "task" "$TASK"
 
+# #180: Validate target agent belongs to the specified team
+if [ -n "$TEAM_ID" ] && [ "$FORCE_CROSS_TEAM" != "true" ]; then
+  TEAM_DATA=$(api_call GET "/teams/${TEAM_ID}" 2>/dev/null || echo '{}')
+  MEMBER_SESSION=$(echo "$TEAM_DATA" | jq -r --arg to "$TO" '.data.members[]? | select(.sessionName == $to) | .sessionName // empty' 2>/dev/null || true)
+  if [ -z "$MEMBER_SESSION" ]; then
+    echo "{\"success\":false,\"error\":\"Cross-team delegation blocked: ${TO} is not a member of team ${TEAM_ID}. Use forceCrossTeam:true to override.\"}"
+    exit 1
+  fi
+fi
+
+# #182: Technical task routing — if taskType=technical and target is PM with a TL,
+# auto-redirect to the TL to skip PM middleman latency
+if [ "$TASK_TYPE" = "technical" ] && [ -n "$TEAM_ID" ]; then
+  TARGET_ROLE=$(echo "$TEAM_DATA" | jq -r --arg to "$TO" '.data.members[]? | select(.sessionName == $to) | .role // empty' 2>/dev/null || true)
+  if [ "$TARGET_ROLE" = "product-manager" ]; then
+    # Find TL in the same team
+    TL_SESSION=$(echo "$TEAM_DATA" | jq -r '.data.members[]? | select(.role == "team-leader" or .canDelegate == true) | .sessionName // empty' 2>/dev/null | head -1 || true)
+    if [ -n "$TL_SESSION" ]; then
+      echo "{\"info\":\"Technical task redirected from PM (${TO}) to TL (${TL_SESSION})\"}" >&2
+      TO="$TL_SESSION"
+    fi
+  fi
+fi
+
 # Structured message parameters (for hierarchical teams)
 TITLE=$(echo "$INPUT" | jq -r '.title // empty')
 PARENT_TASK_ID=$(echo "$INPUT" | jq -r '.parentTaskId // empty')
@@ -79,13 +108,13 @@ if [ "$USE_STRUCTURED" = "true" ] && [ -n "$TITLE" ]; then
   [ -n "$CONTEXT" ] && TASK_MESSAGE="${TASK_MESSAGE}\n\nAdditional context: ${CONTEXT}"
   [ -n "$DEADLINE_HINT" ] && TASK_MESSAGE="${TASK_MESSAGE}\n\n**Deadline hint**: ${DEADLINE_HINT}"
   TASK_MESSAGE="${TASK_MESSAGE}\n\n---\nWhen done, report back using: bash ${CREWLY_ROOT}/config/skills/agent/core/report-status/execute.sh '{\"sessionName\":\"${TO}\",\"status\":\"done\",\"summary\":\"<brief summary>\",\"projectPath\":\"${PROJECT_PATH}\"}'"
-  TASK_MESSAGE="${TASK_MESSAGE}\n\nBefore reporting done, persist key findings using: bash ${CREWLY_ROOT}/config/skills/agent/core/remember/execute.sh '{\"agentId\":\"${TO}\",\"content\":\"<key findings>\",\"category\":\"pattern\",\"scope\":\"project\"}'"
+  TASK_MESSAGE="${TASK_MESSAGE}\n\nBefore reporting done, persist key findings using: bash ${CREWLY_ROOT}/config/skills/agent/core/remember/execute.sh '{\"agentId\":\"${TO}\",\"content\":\"<key findings>\",\"category\":\"pattern\",\"scope\":\"project\",\"projectPath\":\"${PROJECT_PATH}\"}'"
 else
   # Legacy free-text format (backwards compatible)
   TASK_MESSAGE="New task from orchestrator (priority: ${PRIORITY}):\n\n${TASK}"
   [ -n "$CONTEXT" ] && TASK_MESSAGE="${TASK_MESSAGE}\n\nContext: ${CONTEXT}"
   TASK_MESSAGE="${TASK_MESSAGE}\n\nWhen done, report back using: bash ${CREWLY_ROOT}/config/skills/agent/core/report-status/execute.sh '{\"sessionName\":\"${TO}\",\"status\":\"done\",\"summary\":\"<brief summary>\",\"projectPath\":\"${PROJECT_PATH}\"}'"
-  TASK_MESSAGE="${TASK_MESSAGE}\n\nBefore reporting done, persist key findings using: bash ${CREWLY_ROOT}/config/skills/agent/core/remember/execute.sh '{\"agentId\":\"${TO}\",\"content\":\"<key findings>\",\"category\":\"pattern\",\"scope\":\"project\"}'"
+  TASK_MESSAGE="${TASK_MESSAGE}\n\nBefore reporting done, persist key findings using: bash ${CREWLY_ROOT}/config/skills/agent/core/remember/execute.sh '{\"agentId\":\"${TO}\",\"content\":\"<key findings>\",\"category\":\"pattern\",\"scope\":\"project\",\"projectPath\":\"${PROJECT_PATH}\"}'"
 fi
 
 # Deliver the task message with fallback strategy:

package/config/skills/orchestrator/get-agent-logs/{instructions.md → SKILL.md}

@@ -1,3 +1,28 @@
+---
+name: Get Agent Logs
+description: "Get recent terminal output from an agent's PTY session."
+version: 1.0.0
+category: monitoring
+skillType: claude-skill
+assignableRoles:
+  - orchestrator
+triggers:
+  - agent logs
+  - check output
+  - terminal output
+tags:
+  - agent
+  - logs
+  - monitoring
+  - terminal
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 15000
+---
+
 # Get Agent Logs
 
 Retrieves recent terminal output from an agent's PTY session.

package/config/skills/orchestrator/get-agent-status/{instructions.md → SKILL.md}

@@ -1,3 +1,27 @@
+---
+name: Get Agent Status
+description: Check the current status of a specific agent by session name.
+version: 1.0.0
+category: monitoring
+skillType: claude-skill
+assignableRoles:
+  - orchestrator
+triggers:
+  - agent status
+  - check agent
+  - is agent active
+tags:
+  - agent
+  - status
+  - monitoring
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 15000
+---
+
 # Get Agent Status
 
 Returns the current status of a specific agent.

package/config/skills/orchestrator/get-project-overview/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: Get Project Overview
+description: Get an overview of all configured projects.
+version: 1.0.0
+category: management
+skillType: claude-skill
+assignableRoles:
+  - orchestrator
+triggers:
+  - project overview
+  - list projects
+  - show projects
+tags:
+  - project
+  - overview
+  - management
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 15000
+---
+
+# Get Project Overview
+
+Get an overview of all configured projects.
+
+## Usage
+
+```bash
+bash config/skills/orchestrator/get-project-overview/execute.sh
+```
+
+## Parameters
+
+None required.
+
+## Output
+
+JSON array of projects with their details.

package/config/skills/orchestrator/get-tasks/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: Get Tasks
+description: Get task progress and overview for the team.
+version: 1.0.0
+category: management
+skillType: claude-skill
+assignableRoles:
+  - orchestrator
+triggers:
+  - get tasks
+  - task progress
+  - show tasks
+tags:
+  - task
+  - progress
+  - management
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 15000
+---
+
+# Get Tasks
+
+Get task progress and overview for the team.
+
+## Usage
+
+```bash
+bash config/skills/orchestrator/get-tasks/execute.sh
+```
+
+## Parameters
+
+None required.
+
+## Output
+
+JSON with team task progress including assigned, completed, and blocked tasks.

package/config/skills/orchestrator/get-team-status/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: Get Team Status
+description: Get current status of all teams and their agents, including who is active/inactive.
+version: 1.0.0
+category: management
+skillType: claude-skill
+assignableRoles:
+  - orchestrator
+triggers:
+  - team status
+  - list teams
+  - who is active
+tags:
+  - team
+  - status
+  - monitoring
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 15000
+---
+
+# Get Team Status
+
+Returns the current status of all teams and their member agents.
+
+## Usage
+
+```bash
+bash config/skills/orchestrator/get-team-status/execute.sh
+```
+
+## Parameters
+
+None required.
+
+## Output
+
+JSON array of teams with members and their statuses (active/inactive, idle/in_progress).
+
+Each team may include a `mission` field (string) describing the team's purpose, plus optional `budget` and `qualityGate` configuration (#173).

package/config/skills/orchestrator/handle-agent-failure/{instructions.md → SKILL.md}

@@ -1,3 +1,30 @@
+---
+name: Handle Agent Failure
+description: Notify the orchestrator when an agent fails or becomes inactive unexpectedly, so recovery actions can be taken.
+version: 1.0.0
+category: monitoring
+skillType: claude-skill
+assignableRoles:
+  - orchestrator
+triggers:
+  - agent failed
+  - agent crashed
+  - agent inactive
+  - handle failure
+  - recovery
+tags:
+  - monitoring
+  - failure
+  - recovery
+  - agent-lifecycle
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 15000
+---
+
 # Handle Agent Failure
 
 Sends a failure notification to the orchestrator when an agent becomes inactive unexpectedly (runtime exit, API failure, crash). The orchestrator can then decide to restart the agent, reassign the task, or inform the user.

package/config/skills/orchestrator/heartbeat/{instructions.md → SKILL.md}

@@ -1,3 +1,27 @@
+---
+name: Heartbeat
+description: Perform a system health check and heartbeat. Calls multiple API endpoints to update heartbeat via middleware and returns system status.
+version: 1.0.0
+category: monitoring
+skillType: claude-skill
+assignableRoles:
+  - orchestrator
+triggers:
+  - heartbeat
+  - health check
+  - system status
+tags:
+  - monitoring
+  - heartbeat
+  - health
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 15000
+---
+
 # Heartbeat Skill
 
 Perform a system health check and heartbeat update.

package/config/skills/orchestrator/list-schedules/{instructions.md → SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: list-schedules
+description: List all active scheduled checks. Optionally filter by session name.
+---
+
 # list-schedules
 
 List all active scheduled checks (one-time and recurring).

package/config/skills/orchestrator/list-subscriptions/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: List Subscriptions
+description: List your active event subscriptions.
+version: 1.0.0
+category: monitoring
+skillType: claude-skill
+assignableRoles:
+  - orchestrator
+triggers:
+  - list subscriptions
+  - show subscriptions
+  - active subscriptions
+tags:
+  - events
+  - monitoring
+  - subscription
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 15000
+---
+
+# List Subscriptions
+
+Lists all active event subscriptions.
+
+## Usage
+
+```bash
+bash config/skills/orchestrator/list-subscriptions/execute.sh
+```
+
+## Parameters
+
+None required.
+
+## Output
+
+JSON array of active subscriptions with their IDs, event types, and filters.

package/config/skills/orchestrator/query-knowledge/{instructions.md → SKILL.md}

@@ -1,3 +1,31 @@
+---
+name: Query Knowledge
+description: Search the company knowledge base for SOPs, runbooks, architecture docs, and other documentation.
+version: 1.0.0
+category: memory
+skillType: claude-skill
+assignableRoles:
+  - orchestrator
+triggers:
+  - query knowledge
+  - search knowledge
+  - find docs
+  - search docs
+  - find runbook
+  - find SOP
+tags:
+  - memory
+  - knowledge
+  - search
+  - documentation
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 15000
+---
+
 # Query Knowledge
 
 Search the company knowledge base for relevant documents. Use this to find SOPs, runbooks, architecture docs, team norms, and other documentation before delegating process-oriented tasks.

package/config/skills/orchestrator/read-session-logs/{instructions.md → SKILL.md}

@@ -1,3 +1,29 @@
+---
+name: Read Session Logs
+description: Read persistent terminal log file for a session (ANSI-stripped, includes pre-restart output).
+version: 1.0.0
+category: monitoring
+skillType: claude-skill
+assignableRoles:
+  - orchestrator
+triggers:
+  - session logs
+  - agent logs file
+  - terminal history
+tags:
+  - logs
+  - monitoring
+  - session
+  - terminal
+  - history
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 15000
+---
+
 # Read Session Logs
 
 Read the persistent log file for a PTY session. Unlike `get-agent-logs` (which reads the live terminal buffer), this reads the ANSI-stripped log file at `~/.crewly/logs/sessions/{sessionName}.log`.

package/config/skills/orchestrator/read-system-logs/{instructions.md → SKILL.md}

@@ -1,3 +1,28 @@
+---
+name: Read System Logs
+description: Read recent Crewly server log entries from the persistent log file.
+version: 1.0.0
+category: monitoring
+skillType: claude-skill
+assignableRoles:
+  - orchestrator
+triggers:
+  - system logs
+  - server logs
+  - error logs
+tags:
+  - logs
+  - monitoring
+  - system
+  - errors
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 15000
+---
+
 # Read System Logs
 
 Read recent entries from the Crewly server log file (`~/.crewly/logs/crewly-YYYY-MM-DD.log`).

package/config/skills/orchestrator/recall/{instructions.md → SKILL.md}

@@ -1,3 +1,27 @@
+---
+name: Recall
+description: Retrieve relevant knowledge from memory based on context.
+version: 1.0.0
+category: memory
+skillType: claude-skill
+assignableRoles:
+  - orchestrator
+triggers:
+  - recall
+  - remember what
+  - check memory
+tags:
+  - memory
+  - knowledge
+  - retrieval
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 15000
+---
+
 # Recall
 
 Retrieve relevant knowledge from your persistent memory.

package/config/skills/orchestrator/record-failure/{instructions.md → SKILL.md}

@@ -1,3 +1,30 @@
+---
+name: Record Failure
+description: Record a failed approach or pitfall so the team can avoid repeating it.
+version: 1.0.0
+category: memory
+skillType: claude-skill
+assignableRoles:
+  - orchestrator
+triggers:
+  - record failure
+  - failed approach
+  - what failed
+  - note failure
+  - avoid this
+tags:
+  - memory
+  - failure
+  - pitfalls
+  - lessons-learned
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 15000
+---
+
 # Record Failure
 
 Record a failed approach or pitfall so the team can avoid repeating it.

package/config/skills/orchestrator/record-learning/{instructions.md → SKILL.md}

@@ -1,3 +1,27 @@
+---
+name: Record Learning
+description: Quickly record a learning or discovery while working on a task.
+version: 1.0.0
+category: memory
+skillType: claude-skill
+assignableRoles:
+  - orchestrator
+triggers:
+  - record learning
+  - learned that
+  - note discovery
+tags:
+  - memory
+  - learning
+  - quick-note
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 15000
+---
+
 # Record Learning
 
 Quickly record a learning or discovery. Simpler than `remember` — good for jotting down learnings.

package/config/skills/orchestrator/record-success/{instructions.md → SKILL.md}

@@ -1,3 +1,29 @@
+---
+name: Record Success
+description: Record a successful pattern or approach so the team can replicate it in the future.
+version: 1.0.0
+category: memory
+skillType: claude-skill
+assignableRoles:
+  - orchestrator
+triggers:
+  - record success
+  - successful pattern
+  - what worked
+  - note success
+tags:
+  - memory
+  - success
+  - patterns
+  - best-practices
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 15000
+---
+
 # Record Success
 
 Record a successful pattern or approach so the team can replicate it in the future.

package/config/skills/orchestrator/register-self/{instructions.md → SKILL.md}

@@ -1,3 +1,27 @@
+---
+name: Register Self
+description: Register the orchestrator as active with the Crewly backend. Must be called on startup.
+version: 1.0.0
+category: system
+skillType: claude-skill
+assignableRoles:
+  - orchestrator
+triggers:
+  - register
+  - check in
+  - go online
+tags:
+  - system
+  - registration
+  - startup
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 15000
+---
+
 # Register Self
 
 Registers the orchestrator as active with the Crewly backend. Call this immediately on startup.

package/config/skills/orchestrator/remember/{instructions.md → SKILL.md}

@@ -1,3 +1,27 @@
+---
+name: Remember
+description: Store knowledge in memory for future reference. Persists across sessions.
+version: 1.0.0
+category: memory
+skillType: claude-skill
+assignableRoles:
+  - orchestrator
+triggers:
+  - remember
+  - store knowledge
+  - save memory
+tags:
+  - memory
+  - knowledge
+  - persistence
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 15000
+---
+
 # Remember
 
 Store knowledge in your persistent memory for future reference.

package/config/skills/orchestrator/reply-chat/{instructions.md → SKILL.md}

@@ -1,3 +1,28 @@
+---
+name: Reply Chat
+description: Send a message to the Crewly Chat UI. Use this to post responses, updates, or notifications directly to a chat conversation.
+version: 1.0.0
+category: communication
+skillType: claude-skill
+assignableRoles:
+  - orchestrator
+triggers:
+  - reply chat
+  - send chat
+  - chat message
+  - chat response
+tags:
+  - communication
+  - chat
+  - notification
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 15000
+---
+
 # Reply Chat Skill
 
 Send a message to the Crewly Chat UI. This is the preferred way for orchestrators and agents to post messages to the Chat UI — it uses the backend API directly instead of relying on terminal output `[NOTIFY]` marker interception.