Initial commit
This commit is contained in:
24
.claude-plugin/plugin.json
Normal file
24
.claude-plugin/plugin.json
Normal file
@@ -0,0 +1,24 @@
|
||||
{
|
||||
"name": "campaign-orchestration",
|
||||
"description": "Multi-channel campaign coordination and optimization",
|
||||
"version": "1.0.0",
|
||||
"author": {
|
||||
"name": "GTM Agents",
|
||||
"email": "opensource@intentgpt.ai"
|
||||
},
|
||||
"skills": [
|
||||
"./skills/campaign-planning/SKILL.md",
|
||||
"./skills/channel-integration/SKILL.md",
|
||||
"./skills/performance-tracking/SKILL.md"
|
||||
],
|
||||
"agents": [
|
||||
"./agents/campaign-manager.md",
|
||||
"./agents/channel-coordinator.md",
|
||||
"./agents/performance-optimizer.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/launch-campaign.md",
|
||||
"./commands/coordinate-channels.md",
|
||||
"./commands/optimize-performance.md"
|
||||
]
|
||||
}
|
||||
3
README.md
Normal file
3
README.md
Normal file
@@ -0,0 +1,3 @@
|
||||
# campaign-orchestration
|
||||
|
||||
Multi-channel campaign coordination and optimization
|
||||
30
agents/campaign-manager.md
Normal file
30
agents/campaign-manager.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
name: campaign-manager
|
||||
description: Leads cross-functional GTM campaigns from planning through launch, coordinating
|
||||
strategy, creative, channels, and reporting.
|
||||
model: haiku
|
||||
---
|
||||
|
||||
|
||||
# Campaign Manager Agent
|
||||
|
||||
## Responsibilities
|
||||
- Translate business goals into campaign objectives, KPIs, and briefs.
|
||||
- Coordinate strategy, creative, channel, and analytics teams.
|
||||
- Maintain integrated timelines, budgets, and risk mitigation plans.
|
||||
- Ensure feedback loops between performance data and execution teams.
|
||||
|
||||
## Workflow
|
||||
1. **Intake** – capture campaign goals, audience, offers, and constraints.
|
||||
2. **Plan** – build campaign brief, messaging doc, asset list, and workback schedule.
|
||||
3. **Coordinate** – run stand-ups, unblock owners, manage approvals.
|
||||
4. **Launch** – oversee sequencing across channels and ensure QA passes.
|
||||
5. **Optimize** – review dashboards, deploy tests, share insights with leadership.
|
||||
|
||||
## Outputs
|
||||
- Campaign brief & KPI matrix
|
||||
- Master timeline + RACI
|
||||
- Risk register / mitigation plan
|
||||
- Executive status updates
|
||||
|
||||
---
|
||||
28
agents/channel-coordinator.md
Normal file
28
agents/channel-coordinator.md
Normal file
@@ -0,0 +1,28 @@
|
||||
---
|
||||
name: channel-coordinator
|
||||
description: Oversees multi-channel execution, ensuring messaging and schedules stay aligned across email, social, paid, events, and web.
|
||||
model: haiku
|
||||
---
|
||||
|
||||
# Channel Coordinator Agent
|
||||
|
||||
## Responsibilities
|
||||
- Translate campaign strategy into channel-specific playbooks.
|
||||
- Manage publishing calendars, UTMs, budgets, and pacing per channel.
|
||||
- Ensure creative/spec compliance across email, social, paid media, PR, events.
|
||||
- Surface channel readiness/risk status to campaign manager.
|
||||
|
||||
## Workflow
|
||||
1. **Brief Sync** – gather goals, offers, creative assets, targeting parameters.
|
||||
2. **Channel Plans** – define audiences, placements, cadences, and KPIs for each channel.
|
||||
3. **Execution QA** – verify tracking, creative specs, approvals, and accessibility.
|
||||
4. **Live Monitoring** – monitor delivery, pacing, and engagement; coordinate quick fixes.
|
||||
5. **Reporting** – compile channel insights and recommendations for optimization cycles.
|
||||
|
||||
## Deliverables
|
||||
- Channel launch checklist per channel.
|
||||
- Calendar + trafficking sheet.
|
||||
- Risk/issues log with mitigation steps.
|
||||
- Channel performance snapshot for analytics.
|
||||
|
||||
---
|
||||
28
agents/performance-optimizer.md
Normal file
28
agents/performance-optimizer.md
Normal file
@@ -0,0 +1,28 @@
|
||||
---
|
||||
name: performance-optimizer
|
||||
description: Analytics-focused operator who monitors campaign performance, runs experiments, and recommends budget/channel shifts.
|
||||
model: haiku
|
||||
---
|
||||
|
||||
# Performance Optimizer Agent
|
||||
|
||||
## Responsibilities
|
||||
- Build near-real-time dashboards for pipeline, spend, and engagement KPIs.
|
||||
- Identify under/over-performing channels, creatives, audiences.
|
||||
- Propose experiments (copy, offers, sequencing) and forecast outcomes.
|
||||
- Coordinate with channel leads to implement optimizations and report impact.
|
||||
|
||||
## Workflow
|
||||
1. **Instrumentation** – confirm UTMs, tracking pixels, and BI dashboards are live.
|
||||
2. **Daily Readout** – monitor pacing vs goals; flag anomalies.
|
||||
3. **Insight Generation** – drill into cohort/segment data, diagnose root causes.
|
||||
4. **Optimization Plan** – prioritize actions with owner, expected lift, timeline.
|
||||
5. **Post-Action Review** – measure lift, document learnings, feed back into playbooks.
|
||||
|
||||
## Outputs
|
||||
- Daily/weekly performance summary.
|
||||
- Experiment backlog with ICE scoring.
|
||||
- Budget reallocation recommendations.
|
||||
- Executive dashboards with commentary.
|
||||
|
||||
---
|
||||
41
commands/coordinate-channels.md
Normal file
41
commands/coordinate-channels.md
Normal file
@@ -0,0 +1,41 @@
|
||||
---
|
||||
name: coordinate-channels
|
||||
description: Align scheduling, messaging, and trafficking across all campaign channels.
|
||||
usage: /campaign-orchestration:coordinate-channels --campaign "Q1 Launch" --channels "email,social,paid,events"
|
||||
---
|
||||
|
||||
# Coordinate Channels Command
|
||||
|
||||
## Purpose
|
||||
Provide a unified execution plan for cross-channel campaigns, detailing cadences, owners, specs, and QA checkpoints.
|
||||
|
||||
## Syntax
|
||||
```bash
|
||||
/campaign-orchestration:coordinate-channels \
|
||||
--campaign "<name>" \
|
||||
--channels "email,social,paid,events" \
|
||||
--start "2025-01-10" \
|
||||
--end "2025-02-28"
|
||||
```
|
||||
|
||||
### Parameters
|
||||
- `--campaign`: Campaign name or ID.
|
||||
- `--channels`: Comma-delimited list of channels to orchestrate.
|
||||
- `--start` / `--end`: Run dates for calendar generation.
|
||||
- `--budget`: Optional channel budget map (JSON or CSV).
|
||||
- `--offers`: Asset bundle or offer IDs to align messaging.
|
||||
- `--tracking`: UTM/taxonomy style guide reference.
|
||||
|
||||
## Output Package
|
||||
- Master channel calendar (table + ICS export) with send dates, owners, statuses.
|
||||
- Channel-specific checklists (assets required, approvals, QA steps, trafficking notes).
|
||||
- Risk log (dependencies, blockers, mitigations).
|
||||
- Reporting expectations (metrics per channel, refresh cadence).
|
||||
|
||||
## Best Practices
|
||||
- Sequence channels for storytelling (teaser -> announcement -> nurture).
|
||||
- Lock copy deadlines at least 5 business days before launch.
|
||||
- Share QA sign-off path (creative, legal, ops) to avoid delays.
|
||||
- Maintain single source of truth for UTMs and tracking scripts.
|
||||
|
||||
---
|
||||
346
commands/launch-campaign.md
Normal file
346
commands/launch-campaign.md
Normal file
@@ -0,0 +1,346 @@
|
||||
---
|
||||
name: launch-campaign
|
||||
description: Coordinate strategy, creative, channels, and analytics for multi-agent marketing campaigns.
|
||||
usage: /campaign-orchestration:launch-campaign "Q1 Product Launch" --type product-launch --budget 100000 --timeline 8
|
||||
---
|
||||
|
||||
# Campaign Orchestration Workflow
|
||||
|
||||
Multi-agent orchestration for end-to-end marketing campaign execution, coordinating strategy, creative, distribution, and analytics across multiple channels.
|
||||
|
||||
## Command Syntax
|
||||
```bash
|
||||
/campaign-orchestration:launch-campaign "<campaign_name>" --type <type> --budget <amount> --timeline <weeks>
|
||||
```
|
||||
|
||||
## Orchestration Overview
|
||||
|
||||
This orchestrator coordinates 8+ specialized agents to execute comprehensive marketing campaigns:
|
||||
|
||||
```
|
||||
┌────────────────────────────────────────┐
|
||||
│ Campaign Orchestrator │
|
||||
│ (Master Coordinator) │
|
||||
└────────────────┬───────────────────────┘
|
||||
│
|
||||
┌────────────┴────────────┐
|
||||
│ │
|
||||
┌───▼──────┐ ┌───────▼──────┐
|
||||
│Strategy │ │ Creative │
|
||||
│Agents │ │ Agents │
|
||||
├──────────┤ ├──────────────┤
|
||||
│Campaign │ │Content │
|
||||
│Strategist│ │Creator │
|
||||
│Audience │ │Designer │
|
||||
│Analyst │ │Copy Writer │
|
||||
└──────────┘ └──────────────┘
|
||||
│ │
|
||||
└────────────┬────────────┘
|
||||
│
|
||||
┌────────────┴────────────┐
|
||||
│ │
|
||||
┌───▼──────┐ ┌───────▼──────┐
|
||||
│Channel │ │ Analytics │
|
||||
│Agents │ │ Agents │
|
||||
├──────────┤ ├──────────────┤
|
||||
│Email │ │Data Analyst │
|
||||
│Social │ │Attribution │
|
||||
│Paid Media│ │ROI Calculator│
|
||||
│SEO │ │Dashboard │
|
||||
└──────────┘ └──────────────┘
|
||||
```
|
||||
|
||||
### GTM Agents Pattern & Plan Checklist
|
||||
> Based on GTM Agents's orchestrator guidance @puerto/plugins/orchestrator/README.md#112-325.
|
||||
|
||||
- **Pattern Selection**: default to **pipeline** (Strategy → Creative → Channels → Optimization). Switch to **diamond/fan-out** when creative/analytics work can parallelize; note pattern choice in the plan header.
|
||||
- **Plan Schema**: every `/campaign-orchestration` run must emit a JSON plan saved under `.claude/plans/plan-<timestamp>.json` with objective, complexity, stages, task IDs, parallelization block, context-passing notes, error handling, and success criteria.
|
||||
- **Tool Hooks**: reference `docs/gtm-essentials.md` tools inside plan steps (Serena for code/landing-page patches, Context7 for doc lookups, Sequential Thinking for retros, Playwright for QA checkpoints).
|
||||
- **Guardrails & Escalation**: define retry strategy (immediate vs modified), max retries (default 2), and escalation path (Campaign Strategist → RevOps lead) for failures.
|
||||
- **Review Flow**: before execution, run the checklist from `docs/usage-guide.md#orchestration-best-practices-puerto-parity` (agent availability, dependency validation, deliverables alignment).
|
||||
|
||||
## Workflow Phases
|
||||
|
||||
### Phase 1: Strategy Development (Days 1-5)
|
||||
**Lead Agent**: Campaign Strategist (Sonnet)
|
||||
**Supporting Agents**: Audience Analyst, Competitive Analyst
|
||||
|
||||
```yaml
|
||||
Tasks:
|
||||
- Define campaign objectives and KPIs
|
||||
- Analyze target audience and segments
|
||||
- Research competitive landscape
|
||||
- Develop messaging framework
|
||||
- Create campaign brief
|
||||
|
||||
Outputs:
|
||||
- Campaign strategy document
|
||||
- Audience personas
|
||||
- Messaging matrix
|
||||
- Success metrics framework
|
||||
```
|
||||
|
||||
### Phase 2: Creative Development (Days 6-15)
|
||||
**Lead Agent**: Creative Director (Sonnet)
|
||||
**Supporting Agents**: Content Creator, Designer, Copywriter
|
||||
|
||||
```yaml
|
||||
Tasks:
|
||||
- Develop creative concepts
|
||||
- Write core content pieces
|
||||
- Design visual assets
|
||||
- Create video scripts
|
||||
- Build landing pages
|
||||
|
||||
Outputs:
|
||||
- Content library
|
||||
- Design assets
|
||||
- Landing pages
|
||||
- Video content
|
||||
- Email templates
|
||||
```
|
||||
|
||||
### Phase 3: Channel Setup (Days 16-20)
|
||||
**Lead Agent**: Channel Coordinator (Haiku)
|
||||
**Supporting Agents**: Email Marketer, Social Manager, Paid Specialist
|
||||
|
||||
```yaml
|
||||
Tasks:
|
||||
- Configure email automation
|
||||
- Set up social campaigns
|
||||
- Launch paid advertising
|
||||
- Optimize for SEO
|
||||
- Prepare PR outreach
|
||||
|
||||
Outputs:
|
||||
- Email sequences live
|
||||
- Social calendar scheduled
|
||||
- Ads launched
|
||||
- SEO optimizations complete
|
||||
- PR pitches sent
|
||||
```
|
||||
|
||||
### Phase 4: Launch & Optimization (Days 21+)
|
||||
**Lead Agent**: Performance Optimizer (Sonnet)
|
||||
**Supporting Agents**: Data Analyst, Attribution Specialist
|
||||
|
||||
```yaml
|
||||
Tasks:
|
||||
- Monitor real-time performance
|
||||
- A/B test variations
|
||||
- Optimize based on data
|
||||
- Scale winning elements
|
||||
- Report on results
|
||||
|
||||
Outputs:
|
||||
- Performance dashboards
|
||||
- Optimization reports
|
||||
- Test results
|
||||
- ROI analysis
|
||||
- Executive summary
|
||||
```
|
||||
|
||||
## Agent Coordination Matrix
|
||||
|
||||
| Agent | Role | Phase | Handoffs |
|
||||
|-------|------|-------|----------|
|
||||
| Campaign Strategist | Overall strategy | 1 | → Creative Director |
|
||||
| Audience Analyst | Segment definition | 1 | → All agents |
|
||||
| Creative Director | Creative oversight | 2 | → Channel agents |
|
||||
| Content Creator | Content production | 2 | → Channel agents |
|
||||
| Email Marketer | Email execution | 3 | → Data Analyst |
|
||||
| Social Manager | Social execution | 3 | → Data Analyst |
|
||||
| Paid Specialist | Paid media | 3 | → ROI Calculator |
|
||||
| Data Analyst | Performance tracking | 4 | → All agents |
|
||||
|
||||
## Campaign Types
|
||||
|
||||
### Product Launch Campaign
|
||||
```bash
|
||||
/campaign-orchestration:launch-campaign "Q1 Product Launch" \
|
||||
--type product-launch \
|
||||
--budget 100000 \
|
||||
--timeline 8
|
||||
```
|
||||
|
||||
**Specialized Workflow**:
|
||||
- Pre-launch buzz building
|
||||
- Launch day coordination
|
||||
- Post-launch momentum
|
||||
- Customer success stories
|
||||
|
||||
### Demand Generation Campaign
|
||||
```bash
|
||||
/campaign-orchestration:launch-campaign "Enterprise Lead Gen" \
|
||||
--type demand-gen \
|
||||
--budget 50000 \
|
||||
--timeline 12
|
||||
```
|
||||
|
||||
**Specialized Workflow**:
|
||||
- Content pillar development
|
||||
- Lead magnet creation
|
||||
- Nurture sequence design
|
||||
- Sales handoff optimization
|
||||
|
||||
### Brand Awareness Campaign
|
||||
```bash
|
||||
/campaign-orchestration:launch-campaign "Brand Awareness 2024" \
|
||||
--type brand \
|
||||
--budget 200000 \
|
||||
--timeline 16
|
||||
```
|
||||
|
||||
**Specialized Workflow**:
|
||||
- Brand narrative development
|
||||
- Influencer partnerships
|
||||
- PR coordination
|
||||
- Event integration
|
||||
|
||||
## Coordination Protocols
|
||||
|
||||
### Communication Flow
|
||||
```
|
||||
1. Daily Standups: Quick sync between active agents
|
||||
2. Phase Gates: Formal handoffs with deliverable review
|
||||
3. Escalation Path: Issues → Lead Agent → Orchestrator
|
||||
4. Feedback Loops: Performance data → All agents
|
||||
```
|
||||
|
||||
### Decision Framework
|
||||
```
|
||||
if (performance < target) {
|
||||
1. Data Analyst identifies issue
|
||||
2. Relevant agent proposes solution
|
||||
3. Orchestrator approves change
|
||||
4. Implementation within 24 hours
|
||||
}
|
||||
```
|
||||
|
||||
### Quality Checkpoints
|
||||
- Strategy approval before creative
|
||||
- Creative review before channel setup
|
||||
- Soft launch before full launch
|
||||
- Daily optimization cycles
|
||||
- Plan file updated when scope or owners change (keep `.claude/plans` log in sync).
|
||||
|
||||
## Resource Allocation
|
||||
|
||||
### Agent Time Allocation
|
||||
```
|
||||
Strategy Phase:
|
||||
- Strategist: 100%
|
||||
- Analysts: 75%
|
||||
- Others: 25%
|
||||
|
||||
Creative Phase:
|
||||
- Creative team: 100%
|
||||
- Strategist: 25%
|
||||
- Channel agents: 50%
|
||||
|
||||
Execution Phase:
|
||||
- Channel agents: 100%
|
||||
- Analytics: 100%
|
||||
- Creative: 25%
|
||||
```
|
||||
|
||||
### Budget Distribution (Typical)
|
||||
- Creative Development: 20%
|
||||
- Paid Media: 40%
|
||||
- Technology/Tools: 10%
|
||||
- Content Creation: 20%
|
||||
- Analytics/Reporting: 10%
|
||||
|
||||
## Success Metrics
|
||||
|
||||
### Campaign KPIs
|
||||
```python
|
||||
{
|
||||
"reach": {
|
||||
"impressions": target * 1.2,
|
||||
"unique_visitors": target,
|
||||
"engagement_rate": "5%+"
|
||||
},
|
||||
"conversion": {
|
||||
"leads_generated": 500,
|
||||
"mql_rate": "40%",
|
||||
"sql_rate": "20%"
|
||||
},
|
||||
"revenue": {
|
||||
"pipeline_generated": budget * 10,
|
||||
"revenue_attributed": budget * 3,
|
||||
"roi": "300%+"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Agent Performance Metrics
|
||||
- Strategy accuracy: 85%+
|
||||
- Creative approval rate: 90%+
|
||||
- Channel performance: Above benchmark
|
||||
- Data accuracy: 99%+
|
||||
|
||||
## Output Deliverables
|
||||
|
||||
### Campaign Launch Kit
|
||||
```
|
||||
📁 Campaign Assets
|
||||
├── 📄 Strategy Document
|
||||
├── 📁 Creative Files
|
||||
│ ├── 🎨 Design Assets
|
||||
│ ├── 📝 Copy Docs
|
||||
│ └── 🎥 Video Files
|
||||
├── 📁 Channel Configs
|
||||
│ ├── 📧 Email Sequences
|
||||
│ ├── 📱 Social Calendar
|
||||
│ └── 💰 Ad Campaigns
|
||||
└── 📊 Analytics Dashboard
|
||||
```
|
||||
|
||||
### Executive Report Template
|
||||
```
|
||||
Campaign: [Name]
|
||||
Duration: [Timeline]
|
||||
Budget: [Amount]
|
||||
|
||||
Results Summary:
|
||||
- Reach: [Metrics]
|
||||
- Engagement: [Metrics]
|
||||
- Conversions: [Metrics]
|
||||
- Revenue: [Metrics]
|
||||
|
||||
Key Insights:
|
||||
1. [Top performing element]
|
||||
2. [Surprising finding]
|
||||
3. [Optimization opportunity]
|
||||
|
||||
ROI: [Percentage]
|
||||
Recommendation: [Next steps]
|
||||
```
|
||||
|
||||
## Error Handling & Recovery
|
||||
|
||||
### Common Issues & Solutions
|
||||
| Issue | Detection | Resolution | Recovery Time |
|
||||
|-------|-----------|------------|---------------|
|
||||
| Low engagement | Analytics agent | Creative refresh | 48 hours |
|
||||
| Poor conversion | Attribution agent | Landing page optimization | 24 hours |
|
||||
| Budget overrun | Finance monitor | Channel reallocation | Same day |
|
||||
| Technical failure | System alerts | Backup activation | 1 hour |
|
||||
|
||||
### GTM Agents-Inspired Safeguards
|
||||
- **Retry strategy**: retry once immediately with adjusted parameters; on second failure, escalate to orchestrator for manual intervention.
|
||||
- **Fallback agents**: if specialized agents unavailable, document substitutions (e.g., Content Strategist covering Copywriter) in the plan.
|
||||
- **Escalation triggers**: if KPIs breach guardrails twice in 48h (see lifecycle-mapping skill), notify Marketing Director + RevOps lead.
|
||||
|
||||
## Integration Points
|
||||
|
||||
- **Project Management**: Asana, Monday.com
|
||||
- **Creative Tools**: Figma, Canva, Adobe
|
||||
- **Marketing Platforms**: HubSpot, Marketo, Salesforce
|
||||
- **Analytics**: Google Analytics, Mixpanel, Heap
|
||||
- **Communication**: Slack, Teams
|
||||
|
||||
---
|
||||
|
||||
*Orchestration Model: claude-sonnet-4 for strategy, claude-haiku-4-5 for execution*
|
||||
41
commands/optimize-performance.md
Normal file
41
commands/optimize-performance.md
Normal file
@@ -0,0 +1,41 @@
|
||||
---
|
||||
name: optimize-performance
|
||||
description: Monitor live campaign metrics, identify issues, and recommend budget/channel adjustments.
|
||||
usage: /campaign-orchestration:optimize-performance --campaign "Q1 Launch" --lookback 7d
|
||||
---
|
||||
|
||||
# Optimize Performance Command
|
||||
|
||||
## Purpose
|
||||
Provide near-real-time performance insights plus prioritized optimization actions for active campaigns.
|
||||
|
||||
## Syntax
|
||||
```bash
|
||||
/campaign-orchestration:optimize-performance \
|
||||
--campaign "<name>" \
|
||||
--lookback 7d \
|
||||
--kpis "pipeline,sql,ctr,cpl" \
|
||||
--thresholds thresholds.json
|
||||
```
|
||||
|
||||
### Parameters
|
||||
- `--campaign`: Campaign identifier.
|
||||
- `--lookback`: Window for analysis (e.g., 3d, 7d, 14d).
|
||||
- `--kpis`: Metrics to monitor (pipeline, SQLs, CTR, CPL, ROAS, etc.).
|
||||
- `--thresholds`: JSON config for alert thresholds or target ranges.
|
||||
- `--experiments`: Optional backlog file for ICE scoring.
|
||||
|
||||
## Output Package
|
||||
- KPI snapshot (table/graph) with pacing vs goal.
|
||||
- Anomaly detection summary (channels, creatives, audiences under/overperforming).
|
||||
- Recommended actions list (owner, impact, effort, deadline).
|
||||
- Forecast update (expected pipeline/revenue if actions executed).
|
||||
|
||||
## Process
|
||||
1. **Data Pull** – collect metrics from connected sources (ads, marketing automation, CRM).
|
||||
2. **Pacing & Health Check** – compare actual vs plan; flag channels outside thresholds.
|
||||
3. **Insights** – group findings by audience, creative, offer, channel.
|
||||
4. **Recommendations** – propose reallocations, creative swaps, additional tests.
|
||||
5. **Communication** – create summary for campaign manager + stakeholders.
|
||||
|
||||
---
|
||||
77
plugin.lock.json
Normal file
77
plugin.lock.json
Normal file
@@ -0,0 +1,77 @@
|
||||
{
|
||||
"$schema": "internal://schemas/plugin.lock.v1.json",
|
||||
"pluginId": "gh:gtmagents/gtm-agents:plugins/campaign-orchestration",
|
||||
"normalized": {
|
||||
"repo": null,
|
||||
"ref": "refs/tags/v20251128.0",
|
||||
"commit": "06d135774b89caeb32960b7b961be1050ba773bf",
|
||||
"treeHash": "cc93f9d56b758f81535b348b4566f9e83d6ba2163e01d12e40fd3b17cb887f12",
|
||||
"generatedAt": "2025-11-28T10:17:07.893721Z",
|
||||
"toolVersion": "publish_plugins.py@0.2.0"
|
||||
},
|
||||
"origin": {
|
||||
"remote": "git@github.com:zhongweili/42plugin-data.git",
|
||||
"branch": "master",
|
||||
"commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390",
|
||||
"repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data"
|
||||
},
|
||||
"manifest": {
|
||||
"name": "campaign-orchestration",
|
||||
"description": "Multi-channel campaign coordination and optimization",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
"content": {
|
||||
"files": [
|
||||
{
|
||||
"path": "README.md",
|
||||
"sha256": "1f3c5f855c0bc663d1ad13a127e43ccab2847f48cb1be5f7c686c757515fd9ef"
|
||||
},
|
||||
{
|
||||
"path": "agents/channel-coordinator.md",
|
||||
"sha256": "152ead487ddbd838579b3b626f4f0486b8c4bf4568e4522982c041b82dd3b32a"
|
||||
},
|
||||
{
|
||||
"path": "agents/campaign-manager.md",
|
||||
"sha256": "2e6c400ffefc4f51631b55755fb6c97edb21143bcc5cbd603e700779992d0174"
|
||||
},
|
||||
{
|
||||
"path": "agents/performance-optimizer.md",
|
||||
"sha256": "dd4a9aa9f55517b876006300311519939297ed875a08d26ed5e0174ecd223bd9"
|
||||
},
|
||||
{
|
||||
"path": ".claude-plugin/plugin.json",
|
||||
"sha256": "84db612d5e4b04af7918aa693e8ab6ce9dd1a01f6fb8b26a853bea3696608981"
|
||||
},
|
||||
{
|
||||
"path": "commands/coordinate-channels.md",
|
||||
"sha256": "a30f37c389aee21912a416293456b50e78232276e07c8ed912a598898d187673"
|
||||
},
|
||||
{
|
||||
"path": "commands/optimize-performance.md",
|
||||
"sha256": "e02c417680e4b6323a1a3fd4234a6626e3c72d54199a2d0ea45741848add87e0"
|
||||
},
|
||||
{
|
||||
"path": "commands/launch-campaign.md",
|
||||
"sha256": "8e4dc5f13eee3c4a4c12a2b14b083ebb3b7ef46c24a71f4a7967a4ad2fbda85e"
|
||||
},
|
||||
{
|
||||
"path": "skills/campaign-planning/SKILL.md",
|
||||
"sha256": "7c12ee01f066067ecc3980cfa14b783e09a6179cb2cebf3859e1c4eed04875f2"
|
||||
},
|
||||
{
|
||||
"path": "skills/channel-integration/SKILL.md",
|
||||
"sha256": "8f10062342e36b5b7b53381f6c1b0a8340b782f6e389abe15bbec4d1a2a756f5"
|
||||
},
|
||||
{
|
||||
"path": "skills/performance-tracking/SKILL.md",
|
||||
"sha256": "b08dc18eb7a4b08fab57407b85acf23fd50dadf36ec8b182f56bee1e0926e36a"
|
||||
}
|
||||
],
|
||||
"dirSha256": "cc93f9d56b758f81535b348b4566f9e83d6ba2163e01d12e40fd3b17cb887f12"
|
||||
},
|
||||
"security": {
|
||||
"scannedAt": null,
|
||||
"scannerVersion": null,
|
||||
"flags": []
|
||||
}
|
||||
}
|
||||
32
skills/campaign-planning/SKILL.md
Normal file
32
skills/campaign-planning/SKILL.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
name: campaign-planning
|
||||
description: Use when developing campaign strategy, briefs, KPIs, and workback schedules before execution.
|
||||
---
|
||||
|
||||
# Campaign Planning Skill
|
||||
|
||||
## When to Use
|
||||
- Before launching multi-channel GTM efforts.
|
||||
- When stakeholder alignment on goals, personas, and offers is needed.
|
||||
- During quarterly planning or major product launches.
|
||||
|
||||
## Framework
|
||||
1. **Set Objectives** – tie to revenue/pipeline targets, define primary KPIs.
|
||||
2. **Audience & Offers** – map personas, stages, ICP tiers, and value propositions.
|
||||
3. **Messaging Architecture** – craft key narrative, proof points, CTA hierarchy.
|
||||
4. **Channel Mix** – select channels, budget split, cadence, sequencing logic.
|
||||
5. **Workback Plan** – create timeline with dependencies, approvals, and resource allocation.
|
||||
6. **Risk Assessment** – identify blockers (legal, creative bandwidth, data access) and mitigations.
|
||||
|
||||
## Templates
|
||||
- **Campaign Brief**: See `templates/campaign_brief.md` for goal, audience, and KPIs.
|
||||
- **RACI matrix** for decision-making.
|
||||
- **Timeline Gantt template** with creative/ops milestones.
|
||||
|
||||
## Tips
|
||||
- Host a kickoff with every execution lead to walk through the brief and capture risks live.
|
||||
- Keep KPIs to one primary and two secondary to avoid diffused focus.
|
||||
- Bake review/QA milestones into the workback to prevent last-minute rework.
|
||||
- Maintain a single source-of-truth dashboard so partner teams see timing, assets, and blockers.
|
||||
|
||||
---
|
||||
33
skills/channel-integration/SKILL.md
Normal file
33
skills/channel-integration/SKILL.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
name: channel-integration
|
||||
description: Use when synchronizing messaging, timing, and measurement across multiple campaign channels.
|
||||
---
|
||||
|
||||
# Channel Integration Skill
|
||||
|
||||
## When to Use
|
||||
- Running campaigns that span email, social, paid media, events, web, PR.
|
||||
- Need to prevent message fatigue or conflicting offers.
|
||||
- Ensuring consistent tracking/UTM taxonomy across channels.
|
||||
|
||||
## Framework
|
||||
1. **Messaging Matrix** – align offer, CTA, creative angle per channel/persona.
|
||||
2. **Cadence Alignment** – stagger sends/posts to avoid overlap; define quiet periods.
|
||||
3. **Asset Repository** – maintain single source of truth for approved copy/creative.
|
||||
4. **Tracking Consistency** – standardize UTMs, naming conventions, analytics tags.
|
||||
5. **Feedback Loop** – daily standup with channel owners to share insights/risks.
|
||||
6. **Escalation Path** – define who can approve changes when conflicts arise.
|
||||
|
||||
## Templates
|
||||
- Channel calendar template (email, paid, social, events, partner).
|
||||
- UTM builder/validation sheet.
|
||||
- Real-time channel status dashboard (Ready, QA, Live, Blocked).
|
||||
- Message/source-of-truth sheet mapping audience × channel × CTA.
|
||||
|
||||
## Tips
|
||||
- Use a common taxonomy for statuses (Draft, QA, Scheduled, Live) so every team reads the board the same way.
|
||||
- Hold 15-minute syncs during peak launch weeks, async updates otherwise.
|
||||
- Automate delivery of performance snapshots back to planners so adjustments happen fast.
|
||||
- Designate a single owner for conflict resolution to avoid channel tug-of-war.
|
||||
|
||||
---
|
||||
32
skills/performance-tracking/SKILL.md
Normal file
32
skills/performance-tracking/SKILL.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
name: performance-tracking
|
||||
description: Use when establishing measurement frameworks, dashboards, and optimization rhythms for live campaigns.
|
||||
---
|
||||
|
||||
# Performance Tracking Skill
|
||||
|
||||
## When to Use
|
||||
- Before launch to define metrics, data sources, and reporting cadence.
|
||||
- During active campaigns to monitor pacing vs goals and trigger optimizations.
|
||||
- Post-campaign retros to capture learnings and benchmarks.
|
||||
|
||||
## Framework
|
||||
1. **Metric Hierarchy** – define business (pipeline, revenue), leading (MQL, CTR), and diagnostic metrics (CPC, landing page CVR).
|
||||
2. **Data Plumbing** – map sources (ad platforms, MA, CRM, BI) and ensure consistent IDs/UTMs.
|
||||
3. **Dashboard Build** – create executive + operator views with automated refresh.
|
||||
4. **Alerting** – set thresholds for spend pacing, CPA, conversion drops, SLAs.
|
||||
5. **Insight Cadence** – daily standups, weekly deep dives, end-of-campaign retros.
|
||||
6. **Documentation** – record hypotheses, experiments, and outcomes.
|
||||
|
||||
## Templates
|
||||
- KPI tree worksheet.
|
||||
- Dashboard spec (dataset, visualization, owner, refresh schedule).
|
||||
- Optimization log (date, insight, action, result).
|
||||
|
||||
## Tips
|
||||
- Automate alert routing (Slack, email) so anomalies are actioned quickly.
|
||||
- Pair dashboards with narrative summaries to help execs interpret shifts.
|
||||
- Capture experiment context in the optimization log to prevent repeating failed tests.
|
||||
- Align BI/RevOps early so new metrics get logged before launch.
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user