crewly 1.0.0

package/config/skills/orchestrator/stop-team/execute.sh

@@ -0,0 +1,13 @@
+#!/bin/bash
+# Stop all agents in a team
+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\"}'"
+
+TEAM_ID=$(echo "$INPUT" | jq -r '.teamId // empty')
+require_param "teamId" "$TEAM_ID"
+
+api_call POST "/teams/${TEAM_ID}/stop"

package/config/skills/orchestrator/stop-team/instructions.md

@@ -0,0 +1,19 @@
+# Stop Team
+
+Stops all agents in a team.
+
+## Usage
+
+```bash
+bash config/skills/orchestrator/stop-team/execute.sh '{"teamId":"abc-123-uuid"}'
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `teamId` | Yes | The team's UUID |
+
+## Output
+
+JSON confirmation with team shutdown status.

package/config/skills/orchestrator/stop-team/skill.json

@@ -0,0 +1,20 @@
+{
+  "id": "orc-stop-team",
+  "name": "Stop Team",
+  "description": "Stop all agents in a team.",
+  "category": "management",
+  "skillType": "claude-skill",
+  "promptFile": "instructions.md",
+  "execution": {
+    "type": "script",
+    "script": {
+      "file": "execute.sh",
+      "interpreter": "bash",
+      "timeoutMs": 30000
+    }
+  },
+  "assignableRoles": ["orchestrator"],
+  "triggers": ["stop team", "deactivate team", "shutdown team"],
+  "tags": ["team", "management", "lifecycle"],
+  "version": "1.0.0"
+}

package/config/skills/orchestrator/subscribe-event/execute.sh

@@ -0,0 +1,19 @@
+#!/bin/bash
+# Subscribe to agent lifecycle events
+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 '{\"eventType\":\"agent:idle\",\"filter\":{\"sessionName\":\"agent-joe\"},\"oneShot\":true}'"
+
+EVENT_TYPE=$(echo "$INPUT" | jq -r '.eventType // empty')
+require_param "eventType" "$EVENT_TYPE"
+
+# Inject subscriberSession from env (set by Crewly on each tmux session)
+# The API requires subscriberSession and filter but the agent doesn't need to provide them
+SUBSCRIBER_SESSION="${TMUX_SESSION_NAME:-crewly-orc}"
+BODY=$(echo "$INPUT" | jq --arg ss "$SUBSCRIBER_SESSION" \
+  '. + {subscriberSession: $ss} | if .filter == null then .filter = {} else . end')
+
+api_call POST "/events/subscribe" "$BODY"

package/config/skills/orchestrator/subscribe-event/instructions.md

@@ -0,0 +1,21 @@
+# Subscribe to Event
+
+Subscribe to agent lifecycle events. Matched events arrive as `[EVENT:subId:eventType]` in your terminal.
+
+## Usage
+
+```bash
+bash config/skills/orchestrator/subscribe-event/execute.sh '{"eventType":"agent:idle","filter":{"sessionName":"agent-joe"},"oneShot":true}'
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `eventType` | Yes | Event type: `agent:idle`, `agent:busy`, `agent:active`, `agent:inactive`, `agent:status_changed` |
+| `filter` | No | Filter object, e.g. `{"sessionName":"..."}` |
+| `oneShot` | No | If true, auto-unsubscribe after first match |
+
+## Output
+
+JSON with subscription ID for later management.

package/config/skills/orchestrator/subscribe-event/skill.json

@@ -0,0 +1,20 @@
+{
+  "id": "orc-subscribe-event",
+  "name": "Subscribe to Event",
+  "description": "Subscribe to agent lifecycle events (idle, busy, active, inactive, status_changed).",
+  "category": "monitoring",
+  "skillType": "claude-skill",
+  "promptFile": "instructions.md",
+  "execution": {
+    "type": "script",
+    "script": {
+      "file": "execute.sh",
+      "interpreter": "bash",
+      "timeoutMs": 15000
+    }
+  },
+  "assignableRoles": ["orchestrator"],
+  "triggers": ["subscribe event", "watch agent", "notify when"],
+  "tags": ["events", "monitoring", "subscription"],
+  "version": "1.0.0"
+}

package/config/skills/orchestrator/terminate-agent/execute.sh

@@ -0,0 +1,13 @@
+#!/bin/bash
+# Terminate an agent's terminal session
+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 '{\"sessionName\":\"agent-session\"}'"
+
+SESSION_NAME=$(echo "$INPUT" | jq -r '.sessionName // empty')
+require_param "sessionName" "$SESSION_NAME"
+
+api_call DELETE "/terminal/${SESSION_NAME}"

package/config/skills/orchestrator/terminate-agent/instructions.md

@@ -0,0 +1,19 @@
+# Terminate Agent
+
+Terminate an agent's terminal session completely. Use with caution.
+
+## Usage
+
+```bash
+bash config/skills/orchestrator/terminate-agent/execute.sh '{"sessionName":"agent-joe"}'
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `sessionName` | Yes | The agent's PTY session name to terminate |
+
+## Output
+
+JSON confirmation of session termination.

package/config/skills/orchestrator/terminate-agent/skill.json

@@ -0,0 +1,20 @@
+{
+  "id": "orc-terminate-agent",
+  "name": "Terminate Agent",
+  "description": "Terminate an agent's terminal session completely.",
+  "category": "management",
+  "skillType": "claude-skill",
+  "promptFile": "instructions.md",
+  "execution": {
+    "type": "script",
+    "script": {
+      "file": "execute.sh",
+      "interpreter": "bash",
+      "timeoutMs": 30000
+    }
+  },
+  "assignableRoles": ["orchestrator"],
+  "triggers": ["terminate agent", "kill session", "destroy agent"],
+  "tags": ["agent", "termination", "management"],
+  "version": "1.0.0"
+}

package/config/skills/orchestrator/unsubscribe-event/execute.sh

@@ -0,0 +1,13 @@
+#!/bin/bash
+# Cancel an event subscription
+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 '{\"subscriptionId\":\"sub-123\"}'"
+
+SUB_ID=$(echo "$INPUT" | jq -r '.subscriptionId // empty')
+require_param "subscriptionId" "$SUB_ID"
+
+api_call DELETE "/events/subscribe/${SUB_ID}"

package/config/skills/orchestrator/unsubscribe-event/instructions.md

@@ -0,0 +1,19 @@
+# Unsubscribe from Event
+
+Cancel an event subscription.
+
+## Usage
+
+```bash
+bash config/skills/orchestrator/unsubscribe-event/execute.sh '{"subscriptionId":"sub-abc123"}'
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `subscriptionId` | Yes | The subscription ID to cancel |
+
+## Output
+
+JSON confirmation of cancellation.

package/config/skills/orchestrator/unsubscribe-event/skill.json

@@ -0,0 +1,20 @@
+{
+  "id": "orc-unsubscribe-event",
+  "name": "Unsubscribe from Event",
+  "description": "Cancel an event subscription by ID.",
+  "category": "monitoring",
+  "skillType": "claude-skill",
+  "promptFile": "instructions.md",
+  "execution": {
+    "type": "script",
+    "script": {
+      "file": "execute.sh",
+      "interpreter": "bash",
+      "timeoutMs": 15000
+    }
+  },
+  "assignableRoles": ["orchestrator"],
+  "triggers": ["unsubscribe event", "cancel subscription"],
+  "tags": ["events", "monitoring", "subscription"],
+  "version": "1.0.0"
+}

package/config/skills/orchestrator/update-focus/execute.sh

@@ -0,0 +1,13 @@
+#!/bin/bash
+# Update the team's current focus
+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 '{\"focus\":\"...\",\"projectPath\":\"...\",\"updatedBy\":\"orchestrator\"}'"
+
+FOCUS=$(echo "$INPUT" | jq -r '.focus // empty')
+require_param "focus" "$FOCUS"
+
+api_call POST "/memory/focus" "$INPUT"

package/config/skills/orchestrator/update-focus/instructions.md

@@ -0,0 +1,21 @@
+# Update Focus
+
+Update the team's current focus area to align effort and communicate priorities.
+
+## Usage
+
+```bash
+bash config/skills/orchestrator/update-focus/execute.sh '{"focus":"Stabilize authentication flow before adding new features","projectPath":"/path/to/project","updatedBy":"orchestrator"}'
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `focus` | Yes | The new focus area description |
+| `projectPath` | No | Path to the project this focus applies to |
+| `updatedBy` | No | Who is updating the focus (e.g., "orchestrator") |
+
+## Output
+
+JSON confirmation with the updated focus entry.

package/config/skills/orchestrator/update-focus/skill.json

@@ -0,0 +1,20 @@
+{
+  "id": "orc-update-focus",
+  "name": "Update Focus",
+  "description": "Update the team's current focus area to align effort and communicate priorities.",
+  "category": "memory",
+  "skillType": "claude-skill",
+  "promptFile": "instructions.md",
+  "execution": {
+    "type": "script",
+    "script": {
+      "file": "execute.sh",
+      "interpreter": "bash",
+      "timeoutMs": 15000
+    }
+  },
+  "assignableRoles": ["orchestrator"],
+  "triggers": ["update focus", "change focus", "set focus", "team focus"],
+  "tags": ["memory", "focus", "planning", "coordination"],
+  "version": "1.0.0"
+}

package/config/skills/playwright-chrome-browser/instructions.md

@@ -0,0 +1,95 @@
+# Playwright Chrome Browser
+
+This skill enables browser automation capabilities through the Playwright MCP server for Claude Code.
+
+## Prerequisites
+
+Before using this skill, you must install the Playwright MCP server in Claude Code:
+
+```bash
+claude mcp add @anthropic/mcp-server-playwright
+```
+
+Verify the installation by checking your Claude Code MCP configuration.
+
+## Capabilities
+
+When this skill is enabled, agents can:
+
+- Navigate to web pages
+- Take screenshots of pages or specific elements
+- Fill out forms and input fields
+- Click buttons and links
+- Extract text content from pages
+- Wait for elements to appear
+- Handle multiple browser tabs
+- Execute in headless mode (no visible browser window)
+
+## Usage
+
+The browser automation tools are available through MCP (Model Context Protocol) when the Playwright MCP server is configured in Claude Code.
+
+### Available Tools
+
+- `mcp__playwright__browser_navigate` - Navigate to a URL
+- `mcp__playwright__browser_screenshot` - Take a screenshot
+- `mcp__playwright__browser_click` - Click on an element
+- `mcp__playwright__browser_fill` - Fill an input field
+- `mcp__playwright__browser_select` - Select from dropdown
+- `mcp__playwright__browser_hover` - Hover over an element
+- `mcp__playwright__browser_evaluate` - Execute JavaScript on the page
+- `mcp__playwright__browser_console_messages` - Get console messages
+- `mcp__playwright__browser_network_requests` - Monitor network activity
+- `mcp__playwright__browser_tab_list` - List open tabs
+- `mcp__playwright__browser_tab_new` - Open a new tab
+- `mcp__playwright__browser_tab_select` - Switch between tabs
+- `mcp__playwright__browser_tab_close` - Close a tab
+- `mcp__playwright__browser_close` - Close the browser
+
+## Comparison with Chrome Browser Skill
+
+| Feature | Playwright MCP | Chrome Extension |
+|---------|---------------|------------------|
+| Installation | MCP server install | Chrome extension |
+| Browser visibility | Headless (invisible) | Visible browser |
+| Speed | Faster (no rendering) | Real browser speed |
+| Reliability | Very stable | Depends on extension |
+| Use case | Testing, scraping | Interactive automation |
+
+## Best Practices
+
+1. **Always take screenshots** after navigation to verify page state
+2. **Use specific selectors** - prefer IDs and data-testid attributes
+3. **Wait for elements** before interacting with them
+4. **Handle errors gracefully** - pages may load slowly or fail
+5. **Close browser when done** to free resources
+
+## Example Workflow
+
+```
+1. Navigate to the target URL
+2. Wait for page to load
+3. Take a screenshot to verify state
+4. Interact with elements (click, fill, select)
+5. Take another screenshot to verify result
+6. Extract needed data
+7. Close the browser
+```
+
+## Troubleshooting
+
+### MCP Server Not Found
+If you get an error about the MCP server not being available:
+1. Verify installation: Check Claude Code MCP settings
+2. Restart Claude Code after adding the MCP server
+3. Re-run: `claude mcp add @anthropic/mcp-server-playwright`
+
+### Element Not Found
+- Ensure the page has fully loaded before interacting
+- Verify the selector is correct using browser dev tools
+- Try alternative selectors (text content, aria labels)
+
+### Screenshot Failures
+- Ensure the browser has navigated to a page first
+- Check that the element exists if taking element screenshot
+- Verify sufficient disk space for screenshot storage

package/config/skills/playwright-chrome-browser/skill.json

@@ -0,0 +1,44 @@
+{
+  "id": "playwright-chrome-browser",
+  "name": "Playwright Chrome Browser",
+  "description": "Enable browser automation capabilities using Playwright MCP server. This allows agents to interact with web pages, take screenshots, fill forms, and perform automated browser tasks through the Playwright automation framework.",
+  "category": "automation",
+  "skillType": "mcp",
+  "promptFile": "instructions.md",
+  "execution": {
+    "type": "mcp-tool",
+    "mcpTool": {
+      "toolName": "mcp__playwright__*",
+      "defaultParams": {}
+    }
+  },
+  "runtime": {
+    "runtime": "claude-code",
+    "requiredMcpServers": ["@anthropic/mcp-server-playwright"]
+  },
+  "notices": [
+    {
+      "type": "requirement",
+      "title": "Playwright MCP Required",
+      "message": "This skill requires the Playwright MCP server to be installed in Claude Code. Run: claude mcp add @anthropic/mcp-server-playwright",
+      "link": "https://www.npmjs.com/package/@anthropic/mcp-server-playwright",
+      "linkText": "View Package"
+    },
+    {
+      "type": "info",
+      "title": "Claude Code Runtime Only",
+      "message": "This skill is only available when using Claude Code as the AI runtime."
+    },
+    {
+      "type": "info",
+      "title": "Headless by Default",
+      "message": "Playwright runs in headless mode by default. The browser window is not visible during automation."
+    }
+  ],
+  "triggers": ["playwright", "browser", "web automation", "screenshot", "click", "fill form", "navigate", "headless"],
+  "tags": ["browser", "automation", "playwright", "mcp", "web", "headless", "testing"],
+  "assignableRoles": [],
+  "version": "1.0.0",
+  "createdAt": "2024-01-01T00:00:00.000Z",
+  "updatedAt": "2024-01-01T00:00:00.000Z"
+}

package/config/sops/common/blocker-handling.md

@@ -0,0 +1,55 @@
+---
+id: common-blocker-handling
+version: 1
+createdAt: 2026-01-29T00:00:00Z
+updatedAt: 2026-01-29T00:00:00Z
+createdBy: system
+role: all
+category: escalation
+priority: 9
+title: Blocker Handling
+description: How to handle and escalate blockers
+triggers:
+  - blocked
+  - stuck
+  - help
+  - issue
+  - problem
+tags:
+  - escalation
+  - blockers
+  - help
+---
+
+# Blocker Handling
+
+## Types of Blockers
+
+1. **Technical** - Code issue, bug, error
+2. **Dependency** - Waiting on another task
+3. **Clarity** - Unclear requirements
+4. **Access** - Missing permissions/resources
+5. **External** - Third-party issue
+
+## Resolution Steps
+
+1. **Identify** - What exactly is blocking?
+2. **Research** - Can you find a solution?
+3. **Document** - Record what you've tried
+4. **Ask** - Use `recall` tool for similar issues
+5. **Escalate** - If still blocked after 30 min
+
+## When to Escalate
+
+- Blocked for more than 30 minutes
+- Multiple failed attempts
+- Need external help
+- Critical path affected
+
+## Escalation Message
+
+Include:
+- What you're trying to do
+- What's blocking you
+- What you've tried
+- What help you need

package/config/sops/common/communication-protocol.md

@@ -0,0 +1,52 @@
+---
+id: common-communication
+version: 1
+createdAt: 2026-01-29T00:00:00Z
+updatedAt: 2026-01-29T00:00:00Z
+createdBy: system
+role: all
+category: communication
+priority: 10
+title: Communication Protocol
+description: Standard communication protocol for all agents
+triggers:
+  - message
+  - send
+  - communicate
+  - team
+  - ask
+tags:
+  - communication
+  - team
+  - protocol
+---
+
+# Communication Protocol
+
+## When to Communicate
+
+- **Starting work** - Notify PM when accepting task
+- **Progress updates** - Every 30 minutes or on completion
+- **Blockers** - Immediately when blocked
+- **Questions** - When unclear about requirements
+- **Completion** - When task is ready for review
+
+## Message Format
+
+Keep messages:
+- **Concise** - Get to the point
+- **Actionable** - Clear what's needed
+- **Contextual** - Include relevant details
+
+## Escalation Path
+
+1. First: Try to resolve yourself
+2. Then: Ask teammate
+3. Then: Ask PM
+4. Finally: Escalate to orchestrator
+
+## Tools
+
+- `send_message` - Direct to specific agent
+- `report_progress` - Status updates
+- `request_review` - Ask for code review

package/config/sops/developer/coding-standards.md

@@ -0,0 +1,54 @@
+---
+id: dev-coding-standards
+version: 1
+createdAt: 2026-01-29T00:00:00Z
+updatedAt: 2026-01-29T00:00:00Z
+createdBy: system
+role: developer
+category: quality
+priority: 10
+title: Coding Standards
+description: Standard coding practices for all developers
+triggers:
+  - code
+  - implement
+  - write
+  - function
+  - class
+tags:
+  - standards
+  - quality
+  - typescript
+---
+
+# Coding Standards
+
+Follow these standards for all code changes.
+
+## Code Style
+
+1. **Use TypeScript** - All new code should be TypeScript
+2. **Explicit types** - Define interfaces for all data structures
+3. **No `any`** - Use `unknown` with type guards instead
+4. **Meaningful names** - Variables and functions should be self-documenting
+
+## File Organization
+
+1. One component/service per file
+2. Test files next to source files (`*.test.ts`)
+3. Group related files in directories
+4. Use barrel exports (`index.ts`)
+
+## Functions
+
+1. **Single responsibility** - One function, one purpose
+2. **Small functions** - Aim for <30 lines
+3. **Pure functions** - Minimize side effects
+4. **Document complex logic** - Add comments for non-obvious code
+
+## Error Handling
+
+1. Always use try/catch for async operations
+2. Log errors with context
+3. Throw meaningful error messages
+4. Don't swallow errors silently

package/config/sops/developer/git-workflow.md

@@ -0,0 +1,58 @@
+---
+id: dev-git-workflow
+version: 1
+createdAt: 2026-01-29T00:00:00Z
+updatedAt: 2026-01-29T00:00:00Z
+createdBy: system
+role: developer
+category: git
+priority: 10
+title: Git Workflow
+description: Standard git workflow for developers
+triggers:
+  - commit
+  - push
+  - branch
+  - merge
+  - git
+tags:
+  - git
+  - workflow
+  - version-control
+---
+
+# Git Workflow
+
+## Branch Naming
+
+- `feat/{ticket-id}-{description}` - New features
+- `fix/{ticket-id}-{description}` - Bug fixes
+- `refactor/{description}` - Code refactoring
+- `test/{description}` - Adding tests
+
+## Commit Messages
+
+Use conventional commits:
+
+```
+{type}({scope}): {description}
+
+{body - optional}
+
+{footer - optional}
+```
+
+Types: `feat`, `fix`, `refactor`, `test`, `docs`, `chore`
+
+## Commit Frequency
+
+- Commit at least every 30 minutes
+- Each commit should be atomic (one logical change)
+- Don't commit broken code
+
+## Before Pushing
+
+1. Run `npm run typecheck`
+2. Run `npm test`
+3. Run `npm run lint`
+4. Review your changes: `git diff`