crewly 1.4.61 → 1.4.63

package/config/skills/agent/marketing/weekly-marketing-report/execute.test.sh

@@ -0,0 +1,241 @@
+#!/bin/bash
+# Tests for weekly-marketing-report skill
+set -euo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+EXECUTE="${SCRIPT_DIR}/execute.sh"
+TEST_PROJECT=$(mktemp -d)
+PASS=0
+FAIL=0
+
+cleanup() {
+  rm -rf "$TEST_PROJECT"
+}
+trap cleanup EXIT
+
+assert_eq() {
+  local test_name="$1" expected="$2" actual="$3"
+  if [ "$expected" = "$actual" ]; then
+    echo "  ✓ ${test_name}"
+    PASS=$((PASS + 1))
+  else
+    echo "  ✗ ${test_name}: expected '${expected}', got '${actual}'"
+    FAIL=$((FAIL + 1))
+  fi
+}
+
+assert_true() {
+  local test_name="$1" value="$2"
+  if [ "$value" = "true" ]; then
+    echo "  ✓ ${test_name}"
+    PASS=$((PASS + 1))
+  else
+    echo "  ✗ ${test_name}: expected true, got '${value}'"
+    FAIL=$((FAIL + 1))
+  fi
+}
+
+echo "=== Weekly Marketing Report Skill Tests ==="
+echo ""
+
+# ─────────────────────────────────────────────
+# Test 1: Missing required parameters
+# ─────────────────────────────────────────────
+echo "Test 1: Missing required parameters"
+RESULT=$(bash "$EXECUTE" '{}' 2>&1 || true)
+HAS_ERROR=$(echo "$RESULT" | jq -r '.error // empty' 2>/dev/null || echo "")
+assert_true "exits with error on missing params" "$([ -n "$HAS_ERROR" ] && echo true || echo false)"
+
+# ─────────────────────────────────────────────
+# Test 2: Empty calendar (no file)
+# ─────────────────────────────────────────────
+echo "Test 2: No calendar file"
+EMPTY_PROJECT=$(mktemp -d)
+RESULT=$(bash "$EXECUTE" "{
+  \"projectPath\": \"${EMPTY_PROJECT}\",
+  \"weekEndDate\": \"2026-03-29\",
+  \"businessName\": \"EmptyBiz\"
+}")
+
+assert_true "returns success" "$(echo "$RESULT" | jq -r '.success')"
+assert_eq "totalPosts is 0" "0" "$(echo "$RESULT" | jq -r '.report.totalPosts')"
+assert_true "has recommendations" "$(echo "$RESULT" | jq -r '.report.recommendations | length > 0')"
+assert_true "has markdown" "$(echo "$RESULT" | jq -r '.markdown' | grep -q 'Weekly Marketing Report' && echo true || echo false)"
+rm -rf "$EMPTY_PROJECT"
+
+# ─────────────────────────────────────────────
+# Test 3: Calendar with sample data
+# ─────────────────────────────────────────────
+echo "Test 3: Calendar with sample data"
+CALENDAR_DIR="${TEST_PROJECT}/.crewly/content"
+mkdir -p "$CALENDAR_DIR"
+cat > "${CALENDAR_DIR}/calendar.json" << 'CALEOF'
+{
+  "entries": [
+    {
+      "id": "cc-test-001",
+      "title": "AI Trends Thread",
+      "platform": "x",
+      "type": "thread",
+      "scheduledDate": "2026-03-23",
+      "status": "published",
+      "publishedAt": "2026-03-23T10:00:00Z",
+      "line": "crewly",
+      "topic": "AI trends",
+      "notes": "",
+      "tags": ["ai"],
+      "createdAt": "2026-03-22T00:00:00Z",
+      "updatedAt": "2026-03-23T10:00:00Z"
+    },
+    {
+      "id": "cc-test-002",
+      "title": "LinkedIn Thought Leadership",
+      "platform": "linkedin",
+      "type": "post",
+      "scheduledDate": "2026-03-24",
+      "status": "published",
+      "publishedAt": "2026-03-24T09:00:00Z",
+      "line": "crewly",
+      "topic": "Leadership",
+      "notes": "",
+      "tags": ["leadership"],
+      "createdAt": "2026-03-22T00:00:00Z",
+      "updatedAt": "2026-03-24T09:00:00Z"
+    },
+    {
+      "id": "cc-test-003",
+      "title": "Product Update Post",
+      "platform": "x",
+      "type": "post",
+      "scheduledDate": "2026-03-25",
+      "status": "draft",
+      "line": "crewly",
+      "topic": "Product update",
+      "notes": "",
+      "tags": ["product"],
+      "createdAt": "2026-03-22T00:00:00Z",
+      "updatedAt": "2026-03-22T00:00:00Z"
+    },
+    {
+      "id": "cc-test-004",
+      "title": "Community Question",
+      "platform": "linkedin",
+      "type": "post",
+      "scheduledDate": "2026-03-26",
+      "status": "ready",
+      "line": "crewly",
+      "topic": "Community",
+      "notes": "",
+      "tags": ["community"],
+      "createdAt": "2026-03-22T00:00:00Z",
+      "updatedAt": "2026-03-22T00:00:00Z"
+    },
+    {
+      "id": "cc-test-old",
+      "title": "Old Post (outside week)",
+      "platform": "x",
+      "type": "post",
+      "scheduledDate": "2026-03-10",
+      "status": "published",
+      "publishedAt": "2026-03-10T10:00:00Z",
+      "line": "crewly",
+      "topic": "Old",
+      "notes": "",
+      "tags": [],
+      "createdAt": "2026-03-09T00:00:00Z",
+      "updatedAt": "2026-03-10T10:00:00Z"
+    }
+  ],
+  "metadata": {
+    "createdAt": "2026-03-22T00:00:00Z",
+    "version": "1.0"
+  }
+}
+CALEOF
+
+RESULT=$(bash "$EXECUTE" "{
+  \"projectPath\": \"${TEST_PROJECT}\",
+  \"weekEndDate\": \"2026-03-29\",
+  \"businessName\": \"TestBiz\"
+}")
+
+assert_true "returns success" "$(echo "$RESULT" | jq -r '.success')"
+assert_eq "totalPosts is 4" "4" "$(echo "$RESULT" | jq -r '.report.totalPosts')"
+assert_eq "publishedCount is 2" "2" "$(echo "$RESULT" | jq -r '.report.publishedCount')"
+assert_eq "completionRate is 50" "50" "$(echo "$RESULT" | jq -r '.report.completionRate')"
+
+# Platform breakdown
+assert_eq "x platform count" "2" "$(echo "$RESULT" | jq -r '.report.platformBreakdown.x')"
+assert_eq "linkedin platform count" "2" "$(echo "$RESULT" | jq -r '.report.platformBreakdown.linkedin')"
+
+# Status breakdown
+assert_eq "published status count" "2" "$(echo "$RESULT" | jq -r '.report.statusBreakdown.published')"
+assert_eq "draft status count" "1" "$(echo "$RESULT" | jq -r '.report.statusBreakdown.draft')"
+assert_eq "ready status count" "1" "$(echo "$RESULT" | jq -r '.report.statusBreakdown.ready')"
+
+# Pipeline health
+assert_eq "pipeline draft count" "1" "$(echo "$RESULT" | jq -r '.report.pipelineHealth.draft')"
+assert_eq "pipeline ready count" "1" "$(echo "$RESULT" | jq -r '.report.pipelineHealth.ready')"
+assert_eq "pipeline published count" "2" "$(echo "$RESULT" | jq -r '.report.pipelineHealth.published')"
+
+# Recommendations
+assert_true "has recommendations" "$(echo "$RESULT" | jq -r '.report.recommendations | length > 0')"
+
+# Markdown output
+assert_true "markdown contains business name" "$(echo "$RESULT" | jq -r '.markdown' | grep -q 'TestBiz' && echo true || echo false)"
+assert_true "markdown contains Platform Breakdown" "$(echo "$RESULT" | jq -r '.markdown' | grep -q 'Platform Breakdown' && echo true || echo false)"
+
+# ─────────────────────────────────────────────
+# Test 4: Excludes out-of-range entries
+# ─────────────────────────────────────────────
+echo "Test 4: Excludes out-of-range entries"
+# The old post (2026-03-10) should NOT be in the week ending 2026-03-29
+assert_eq "old post excluded from count" "4" "$(echo "$RESULT" | jq -r '.report.totalPosts')"
+
+# ─────────────────────────────────────────────
+# Test 5: Report with custom calendarPath
+# ─────────────────────────────────────────────
+echo "Test 5: Custom calendarPath"
+CUSTOM_CAL=$(mktemp)
+cat > "$CUSTOM_CAL" << 'CALEOF'
+{
+  "entries": [
+    {
+      "id": "cc-custom-001",
+      "title": "Custom Post",
+      "platform": "x",
+      "type": "post",
+      "scheduledDate": "2026-04-01",
+      "status": "published",
+      "publishedAt": "2026-04-01T10:00:00Z",
+      "line": "crewly",
+      "topic": "Custom",
+      "notes": "",
+      "tags": [],
+      "createdAt": "2026-04-01T00:00:00Z",
+      "updatedAt": "2026-04-01T10:00:00Z"
+    }
+  ],
+  "metadata": {"createdAt":"2026-04-01T00:00:00Z","version":"1.0"}
+}
+CALEOF
+
+RESULT=$(bash "$EXECUTE" "{
+  \"calendarPath\": \"${CUSTOM_CAL}\",
+  \"weekEndDate\": \"2026-04-05\",
+  \"businessName\": \"CustomBiz\"
+}")
+
+assert_true "returns success with custom path" "$(echo "$RESULT" | jq -r '.success')"
+assert_eq "finds 1 entry" "1" "$(echo "$RESULT" | jq -r '.report.totalPosts')"
+rm -f "$CUSTOM_CAL"
+
+# ─────────────────────────────────────────────
+# Summary
+# ─────────────────────────────────────────────
+echo ""
+echo "=== Results: ${PASS} passed, ${FAIL} failed ==="
+
+if [ "$FAIL" -gt 0 ]; then
+  exit 1
+fi

package/config/skills/orchestrator/send-to-remote/SKILL.md

@@ -0,0 +1,51 @@
+# send-to-remote
+
+Send a cross-machine message to a remote Crewly instance via Slack.
+
+## When to use
+
+Use this skill when you need to communicate with a Crewly orchestrator running on a different machine. Both machines must be connected to the same Slack workspace and have cross-machine messaging configured.
+
+## Prerequisites
+
+1. Both machines must have Slack connected
+2. Cross-machine messaging must be configured on both machines (via `POST /api/cross-machine/configure`)
+3. Both machines must be in the same Slack workspace
+
+## Usage
+
+```bash
+# Delegate a task to a remote machine
+bash execute.sh '{"targetMachine":"<device-id>","type":"delegate-task","message":"Run the full test suite on branch feature/xyz"}'
+
+# Send a message to a remote orchestrator
+bash execute.sh '{"targetMachine":"<device-id>","type":"send-message","message":"Build completed successfully"}'
+
+# Request status from a remote machine
+bash execute.sh '{"targetMachine":"<device-id>","type":"status-request"}'
+
+# Ping all machines (broadcast)
+bash execute.sh '{"targetMachine":"*","type":"ping"}'
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `targetMachine` | Yes | Target device ID (UUID from `~/.crewly/device.json`) or `*` for broadcast |
+| `type` | Yes | Message type: `delegate-task`, `send-message`, `status-request`, `ping` |
+| `message` | No | Human-readable message text |
+| `payload` | No | JSON object with additional structured data |
+
+## Message Types
+
+- **delegate-task**: Ask the remote orchestrator to execute a task
+- **send-message**: Send an informational message
+- **status-request**: Request status from the remote machine (triggers automatic response)
+- **ping**: Check if a machine is online (triggers automatic pong response)
+
+## Finding Device IDs
+
+To find a remote machine's device ID:
+1. On the remote machine: `cat ~/.crewly/device.json` → `deviceId` field
+2. Or use `GET /api/cross-machine/status` on the local machine to see your own ID

package/config/skills/orchestrator/send-to-remote/execute.sh

@@ -0,0 +1,114 @@
+#!/bin/bash
+# Send a cross-machine message to a remote Crewly instance via Slack
+#
+# Usage:
+#   bash execute.sh '{"targetMachine":"device-uuid","type":"delegate-task","message":"Run tests"}'
+#   bash execute.sh --target device-uuid --type delegate-task --message "Run tests"
+#   bash execute.sh --target "*" --type ping   # Broadcast ping to all machines
+#
+# Parameters:
+#   targetMachine / --target   Target device ID or "*" for broadcast (required)
+#   type / --type              Message type: delegate-task|send-message|status-request|ping (required)
+#   message / --message        Message text (optional, included in payload)
+#   payload / --payload        JSON payload string (optional)
+#
+set -euo pipefail
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+source "${SCRIPT_DIR}/../_common/lib.sh"
+
+print_usage() {
+  cat <<'EOF_USAGE'
+Usage:
+  bash execute.sh '{"targetMachine":"device-uuid","type":"delegate-task","message":"..."}'
+  bash execute.sh --target <deviceId> --type <type> [--message <text>] [--payload <json>]
+
+Options:
+  --target  | -t   Target device ID or "*" for broadcast (required)
+  --type    | -T   Message type: delegate-task, send-message, status-request, ping (required)
+  --message | -m   Message text (optional)
+  --payload | -p   JSON payload object (optional)
+  --help    | -h   Show this help
+EOF_USAGE
+}
+
+INPUT_JSON=""
+TARGET=""
+TYPE=""
+MESSAGE=""
+PAYLOAD=""
+
+# Detect legacy JSON argument
+if [[ $# -gt 0 && ${1:0:1} == '{' ]]; then
+  INPUT_JSON="$1"
+  shift || true
+fi
+
+while [[ $# -gt 0 ]]; do
+  case "$1" in
+    --target|-t)
+      TARGET="$2"
+      shift 2
+      ;;
+    --type|-T)
+      TYPE="$2"
+      shift 2
+      ;;
+    --message|-m)
+      MESSAGE="$2"
+      shift 2
+      ;;
+    --payload|-p)
+      PAYLOAD="$2"
+      shift 2
+      ;;
+    --help|-h)
+      print_usage
+      exit 0
+      ;;
+    *)
+      if [[ -z "$INPUT_JSON" && ${1:0:1} == '{' ]]; then
+        INPUT_JSON="$1"
+        shift
+      else
+        echo '{"error":"Unknown argument: '"$1"'"}' >&2
+        exit 1
+      fi
+      ;;
+  esac
+done
+
+# Parse JSON input
+if [ -n "$INPUT_JSON" ]; then
+  TARGET=${TARGET:-$(printf '%s\n' "$INPUT_JSON" | jq -r '.targetMachine // empty')}
+  TYPE=${TYPE:-$(printf '%s\n' "$INPUT_JSON" | jq -r '.type // empty')}
+  MESSAGE=${MESSAGE:-$(printf '%s\n' "$INPUT_JSON" | jq -r '.message // empty')}
+  PAYLOAD=${PAYLOAD:-$(printf '%s\n' "$INPUT_JSON" | jq -r '.payload // empty')}
+fi
+
+require_param "targetMachine" "$TARGET"
+require_param "type" "$TYPE"
+
+# Build the API request body
+export _TARGET="$TARGET"
+export _TYPE="$TYPE"
+export _MESSAGE="${MESSAGE:-}"
+
+if [ -n "$PAYLOAD" ] && [ "$PAYLOAD" != "null" ]; then
+  export _PAYLOAD="$PAYLOAD"
+  BODY=$(jq -n '{
+    targetMachine: env._TARGET,
+    type: env._TYPE,
+    message: (if env._MESSAGE != "" then env._MESSAGE else null end),
+    payload: (env._PAYLOAD | fromjson)
+  } | with_entries(select(.value != null))')
+  unset _PAYLOAD
+else
+  BODY=$(jq -n '{
+    targetMachine: env._TARGET,
+    type: env._TYPE,
+    message: (if env._MESSAGE != "" then env._MESSAGE else null end)
+  } | with_entries(select(.value != null))')
+fi
+unset _TARGET _TYPE _MESSAGE
+
+api_call POST "/cross-machine/send" "$BODY"

package/config/templates/marketing-team/README.md

@@ -0,0 +1,42 @@
+# AI Marketing Team Template
+
+A 3-agent AI marketing team designed for SMBs. Automates content strategy, creation, and analytics across social media platforms.
+
+## Team Composition
+
+- **Maya (Strategist)**: Plans weekly content calendars, researches trends, monitors competitors, and delegates content tasks to the Writer.
+- **Alex (Writer)**: Creates platform-specific social media posts, blog articles, and email newsletters following brand guidelines.
+- **Jordan (Analyst)**: Compiles weekly performance reports with platform metrics, top performers, and data-driven recommendations.
+
+## Workflow
+
+The team follows a weekly content cycle:
+
+1. **Strategy** (Maya) — Research trends, review last week's performance, create content calendar
+2. **Creation** (Alex) — Write content pieces from the calendar, following platform and brand guidelines
+3. **Analysis** (Jordan) — Compile performance metrics, identify top content, recommend optimizations
+
+## Included Skills
+
+- `content-calendar` — CRUD operations for content scheduling
+- `social-media-post` — Generate platform-specific posts
+- `seo-blog-writer` — Write SEO-optimized blog content
+- `daily-standup-report` — Generate team activity reports
+
+## Quick Start
+
+```bash
+npx crewly create team --template marketing-team
+```
+
+## Customization
+
+1. Fill in `knowledge/docs/brand-voice-guide.md` with your brand's voice and tone
+2. Update `goals.md` with your specific marketing KPIs
+3. Adjust content mix ratios in the Strategist's role prompt
+
+## Quality Gates
+
+- **Strategy Quality** — Validates calendar completeness and content mix
+- **Content Quality** — Checks brand voice, grammar, and platform formatting
+- **Report Quality** — Ensures metrics accuracy and actionable recommendations

package/config/templates/marketing-team/goals.md

@@ -0,0 +1,21 @@
+# Marketing Team Goals
+
+## Objective 1: Content Consistency and Quality
+- **KR1**: Publish a minimum of 5 pieces of content per week across all platforms.
+- **KR2**: Maintain 100% adherence to the weekly content calendar (no missed posts).
+- **KR3**: Achieve a minimum content quality score of 80/100 across all peer reviews.
+
+## Objective 2: Audience Growth and Engagement
+- **KR1**: Grow total audience across platforms by 10% month-over-month.
+- **KR2**: Achieve an average engagement rate of 3%+ on X and LinkedIn posts.
+- **KR3**: Increase content reach by 15% week-over-week through optimized posting times and formats.
+
+## Objective 3: Brand Voice and Strategic Alignment
+- **KR1**: 100% of published content passes the brand voice consistency checklist.
+- **KR2**: Maintain a content mix ratio within 5% of target (40% educational, 30% engagement, 20% promotional, 10% community).
+- **KR3**: Respond to trending topics within 24 hours of identification.
+
+## Objective 4: Data-Driven Optimization
+- **KR1**: Deliver weekly performance reports within 24 hours of the reporting period end.
+- **KR2**: Implement at least 2 data-backed strategy adjustments per week based on analytics.
+- **KR3**: Reduce cost-per-engagement by 10% month-over-month through content optimization.

package/config/templates/marketing-team/knowledge/docs/brand-voice-guide.md

@@ -0,0 +1,61 @@
+# Brand Voice Guide
+
+> **Note**: This is a template. Fill in the sections below during brand onboarding to customize for your business.
+
+## Brand Identity
+
+- **Business Name**: [Your Business Name]
+- **Industry**: [Your Industry]
+- **Target Audience**: [Primary audience description]
+- **Brand Mission**: [One-sentence mission statement]
+
+## Voice Attributes
+
+Define 3-5 adjectives that describe your brand voice:
+
+1. [e.g., Professional]
+2. [e.g., Approachable]
+3. [e.g., Innovative]
+4. [e.g., Trustworthy]
+
+## Tone Guidelines
+
+### We Sound Like
+- [Example: A knowledgeable friend who explains complex topics simply]
+- [Example: An enthusiastic expert who genuinely cares about helping]
+
+### We Never Sound Like
+- [Example: Condescending or overly academic]
+- [Example: Pushy or sales-driven]
+
+## Language Rules
+
+### Preferred Terms
+| Instead of... | Use... |
+|---------------|--------|
+| [e.g., Users] | [e.g., Customers] |
+| [e.g., Buy] | [e.g., Get started] |
+
+### Words to Avoid
+- [e.g., Cheap, basic, simple]
+
+## Platform Tone Adjustments
+
+### X (Twitter)
+- Tone shift: [e.g., More casual, punchy]
+- Emoji usage: [e.g., Moderate, 1-2 per post]
+
+### LinkedIn
+- Tone shift: [e.g., More professional, thought-leadership]
+- Emoji usage: [e.g., Minimal]
+
+### Instagram
+- Tone shift: [e.g., More visual, story-driven]
+- Emoji usage: [e.g., Liberal, use to enhance readability]
+
+## Content Pillars
+
+1. **[Pillar 1 Name]**: [Description — e.g., Industry insights and trends]
+2. **[Pillar 2 Name]**: [Description — e.g., Product tips and tutorials]
+3. **[Pillar 3 Name]**: [Description — e.g., Customer success stories]
+4. **[Pillar 4 Name]**: [Description — e.g., Behind-the-scenes and culture]

package/config/templates/marketing-team/knowledge/docs/content-best-practices.md

@@ -0,0 +1,64 @@
+# Social Media Content Best Practices
+
+## General Principles
+
+### The 80/20 Rule
+- 80% of content should inform, educate, or entertain your audience
+- 20% can directly promote your product or service
+
+### Platform-Native Content
+- Never cross-post identical content across platforms
+- Adapt format, length, and tone for each platform
+- Respect platform-specific conventions (e.g., threads on X, carousels on LinkedIn)
+
+## Content Creation Guidelines
+
+### Headlines and Hooks
+- Lead with the most compelling insight or question
+- Use numbers and specifics ("3 lessons" beats "some lessons")
+- Create curiosity gaps without being clickbait
+- Front-load value — readers decide in 2 seconds
+
+### Visual Content
+- Use consistent brand colors and fonts
+- Prefer data visualizations over stock photos
+- Screenshots and real examples outperform generic graphics
+- Always include alt text for accessibility
+
+### Hashtag Strategy
+- Research hashtag reach before using them
+- Mix high-volume and niche hashtags
+- Create a branded hashtag for campaigns
+- Platform limits: X (1-2), LinkedIn (3-5), Instagram (5-15)
+
+## Engagement Best Practices
+
+### Timing
+- Post during peak audience activity hours
+- Maintain consistent posting schedule
+- Space posts at least 2 hours apart on the same platform
+
+### Community Building
+- Respond to comments within 1 hour during business hours
+- Ask questions to encourage discussion
+- Share and comment on relevant community content
+- Tag relevant people and companies when appropriate
+
+### Content Repurposing
+- Turn blog posts into social media threads
+- Convert data points into infographics
+- Extract quotes from long-form content for standalone posts
+- Compile related posts into roundup articles
+
+## Measuring Success
+
+### Key Metrics by Platform
+- **X**: Impressions, engagement rate, retweets, profile clicks
+- **LinkedIn**: Impressions, engagement rate, shares, profile views
+- **Instagram**: Reach, saves, shares, comments
+- **Facebook**: Reach, engagement, shares, click-through rate
+
+### Benchmarks
+- Good engagement rate: 1-3% (varies by platform and audience size)
+- Good click-through rate: 2-5%
+- Healthy follower growth: 2-5% monthly

package/config/templates/marketing-team/knowledge/index.json

@@ -0,0 +1,24 @@
+{
+  "version": "1.0.0",
+  "lastUpdated": "2026-03-22T00:00:00.000Z",
+  "documents": [
+    {
+      "id": "content-best-practices",
+      "title": "Social Media Content Best Practices",
+      "path": "docs/content-best-practices.md",
+      "category": "best-practice",
+      "tags": ["social-media", "content", "marketing", "engagement"],
+      "summary": "Best practices for creating effective social media content across platforms.",
+      "createdAt": "2026-03-22T00:00:00.000Z"
+    },
+    {
+      "id": "brand-voice-guide",
+      "title": "Brand Voice Guide",
+      "path": "docs/brand-voice-guide.md",
+      "category": "terminology",
+      "tags": ["brand", "voice", "tone", "guidelines"],
+      "summary": "Template for defining brand voice, tone, and messaging guidelines. Filled during onboarding.",
+      "createdAt": "2026-03-22T00:00:00.000Z"
+    }
+  ]
+}

package/config/templates/marketing-team/learned-patterns.json

@@ -0,0 +1,5 @@
+{
+  "version": "1.0.0",
+  "lastUpdated": "2026-03-22T00:00:00.000Z",
+  "patterns": []
+}

package/config/templates/marketing-team/norms/brand-consistency.md

@@ -0,0 +1,40 @@
+# Brand Consistency Rules
+
+## Purpose
+
+These rules ensure all marketing output maintains a consistent brand identity across platforms, agents, and content types.
+
+## Mandatory Rules
+
+### 1. Voice Consistency
+- All content must follow the Brand Voice Guide (see `knowledge/docs/brand-voice-guide.md`)
+- When in doubt about tone, err on the side of the brand's primary voice attribute
+- Platform-specific tone adjustments are allowed, but core voice must remain recognizable
+
+### 2. Visual Identity
+- Use approved brand colors in all graphics and visual directions
+- Maintain consistent font usage across platforms
+- Logo placement follows brand guidelines
+- Image style should be consistent (e.g., always flat design, always photography)
+
+### 3. Messaging Hierarchy
+- Lead with the value proposition, not the feature
+- Use the approved tagline in profile bios and campaign headers
+- Key messages should be repeated across platforms (rephrased, not copied)
+
+### 4. Content Pillars
+- Every post must map to at least one defined content pillar
+- Maintain the target content mix ratio (educational/engagement/promotional/community)
+- Track pillar distribution in the weekly report
+
+### 5. Cross-Platform Consistency
+- Same campaign runs on all active platforms (adapted per platform)
+- Announcements go out simultaneously across platforms
+- Profile information is kept in sync (bio, links, profile image)
+
+## Enforcement
+
+- The Strategist (Maya) is responsible for brand consistency review
+- Content that fails brand consistency must be revised before publication
+- Weekly reports should include a brand consistency score or flag
+- New team members must review the Brand Voice Guide before creating content