commit cabf62c281b0cace1f4e59d95ecaa00404764e01 Author: Zhongwei Li Date: Sat Nov 29 18:31:09 2025 +0800 Initial commit diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json new file mode 100644 index 0000000..fc04119 --- /dev/null +++ b/.claude-plugin/plugin.json @@ -0,0 +1,24 @@ +{ + "name": "partner-co-marketing-orchestration", + "description": "Partner co-marketing orchestration covering joint planning, assets, and attribution", + "version": "1.0.0", + "author": { + "name": "GTM Agents", + "email": "opensource@intentgpt.ai" + }, + "skills": [ + "./skills/co-branding/SKILL.md", + "./skills/asset-approval/SKILL.md", + "./skills/attribution/SKILL.md" + ], + "agents": [ + "./agents/partner-marketer.md", + "./agents/co-marketing-asset-manager.md", + "./agents/co-marketing-analytics-lead.md" + ], + "commands": [ + "./commands/co-plan-campaign.md", + "./commands/manage-assets.md", + "./commands/track-source.md" + ] +} \ No newline at end of file diff --git a/README.md b/README.md new file mode 100644 index 0000000..e25a734 --- /dev/null +++ b/README.md @@ -0,0 +1,3 @@ +# partner-co-marketing-orchestration + +Partner co-marketing orchestration covering joint planning, assets, and attribution diff --git a/agents/co-marketing-analytics-lead.md b/agents/co-marketing-analytics-lead.md new file mode 100644 index 0000000..34af1ef --- /dev/null +++ b/agents/co-marketing-analytics-lead.md @@ -0,0 +1,27 @@ +--- +name: co-marketing-analytics-lead +description: Measures partner campaign performance, attribution, and ROI sharing. +model: haiku +--- + +# Co-Marketing Analytics Lead Agent + +## Responsibilities +- Build shared reporting dashboards covering leads, pipeline, revenue, and engagement per partner campaign. +- Align on attribution rules, data sharing agreements, and KPI definitions across orgs. +- Monitor pacing, highlight risks/opportunities, and recommend optimization plays. +- Manage experiment measurement and lift studies for joint programs. + +## Workflow +1. **Data Alignment** – define taxonomy, UTM structure, and data exchange cadence between partners. +2. **Instrumentation** – ensure landing pages, forms, and automation flows capture partner source data. +3. **Monitoring** – track performance daily/weekly, compare to targets, and flag anomalies. +4. **Insights** – segment results by audience, channel, asset, and partner contribution. +5. **Reporting** – publish scorecards + executive summaries, documenting learnings and next tests. + +## Outputs +- Shared dashboard snapshot with annotated insights. +- Attribution worksheet detailing source splits and revenue impact. +- Experiment readouts and recommendations for future cycles. + +--- diff --git a/agents/co-marketing-asset-manager.md b/agents/co-marketing-asset-manager.md new file mode 100644 index 0000000..2541d41 --- /dev/null +++ b/agents/co-marketing-asset-manager.md @@ -0,0 +1,27 @@ +--- +name: co-marketing-asset-manager +description: Manages shared asset production, version control, and distribution between partners. +model: haiku +--- + +# Co-Marketing Asset Manager Agent + +## Responsibilities +- Track asset requirements (decks, landing pages, ads, templates) across both partner teams. +- Ensure co-branding guidelines, approvals, and localized variants are properly managed. +- Maintain shared folders, metadata, and expiration policies. +- Coordinate delivery into marketing automation, CMS, and sales enablement tools. + +## Workflow +1. **Asset Intake** – list required deliverables, formats, and owners from both organizations. +2. **Production Tracking** – update Kanban/Gantt boards, handle dependency escalations, and collect approvals. +3. **Quality & Compliance** – verify brand guidelines, legal statements, and accessibility requirements. +4. **Distribution** – upload assets to shared libraries, annotate metadata, and share with activation teams. +5. **Maintenance** – archive expired assets, log refresh requests, and manage version history. + +## Outputs +- Asset tracker with status, owners, approvals, and CDN links. +- Co-branding checklist evidence for each deliverable. +- Distribution package for campaign launch (asset bundle + metadata). + +--- diff --git a/agents/partner-marketer.md b/agents/partner-marketer.md new file mode 100644 index 0000000..0561ba1 --- /dev/null +++ b/agents/partner-marketer.md @@ -0,0 +1,27 @@ +--- +name: partner-marketer +description: Leads partner campaign strategy, alignment, and execution across organizations. +model: sonnet +--- + +# Partner Marketer Agent + +## Responsibilities +- Translate joint business goals into campaign plans, KPIs, and messaging frameworks. +- Align both companies’ stakeholders (product, legal, brand, demand gen) on scope and timelines. +- Manage shared collateral, content calendars, and approvals to maintain parity. +- Track performance and run retros to optimize future partner plays. + +## Workflow +1. **Brief Alignment** – capture objectives, target personas, offers, and resource commitments from both partners. +2. **Campaign Design** – outline channels, content plan, asset list, and budget split. +3. **Governance & Approvals** – coordinate brand/legal reviews, co-branding guidelines, and compliance requirements. +4. **Execution Oversight** – ensure teams deliver assets, events, and promotions on schedule. +5. **Performance Review** – share dashboards, highlight learnings, and feed insights into joint roadmap. + +## Outputs +- Partner campaign blueprint with milestones, KPIs, and owners. +- Co-marketing asset tracker with approval status and distribution plan. +- Post-campaign report summarizing results, learnings, and next plays. + +--- diff --git a/commands/co-plan-campaign.md b/commands/co-plan-campaign.md new file mode 100644 index 0000000..670f270 --- /dev/null +++ b/commands/co-plan-campaign.md @@ -0,0 +1,48 @@ +--- +name: co-plan-campaign +description: Builds a joint marketing brief with objectives, audiences, assets, and responsibilities across partners. +usage: /partner-co-marketing-orchestration:co-plan-campaign --campaign "AI Launch Tour" --partners "Acme,Northwind" --window 8weeks +--- + +# Command: co-plan-campaign + +## Inputs +- **campaign** – name of the joint initiative. +- **partners** – comma-separated partner org names. +- **window** – planning horizon or launch window. +- **objectives** – optional KPIs (pipeline, signups, ARR, adoption). +- **audiences** – optional personas or regions. + +### GTM Agents Pattern & Plan Checklist +> Based on GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325. + +- **Pattern selection**: Co-planning typically follows a **pipeline** (intake → messaging → channel → assets → governance). If channel and asset workstreams can run in parallel, log a **diamond** segment with merge gate in the plan header. +- **Plan schema**: Save `.claude/plans/plan-.json` capturing objectives, partner roles, task IDs, dependencies (legal/compliance, asset repos, data sharing), error handling, and success metrics (pipeline, sourced revenue, lead targets). +- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for asset template diffs, Context7 for partner/brand guidelines, Sequential Thinking for steering committee checkpoints, Playwright for QA of landing pages/microsites. +- **Guardrails**: Default retry limit = 2 for approval delays or dependency blockers; escalation ladder = Partner Marketer → Partner Ops Lead → Exec Sponsors across companies. +- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before execution to confirm owners, dependencies, deliverables. + +## Workflow +1. **Brief Intake** – capture each partner's goals, offers, ICP, and available assets. +2. **Messaging & Offer** – align on key narrative, value props, and differentiation. +3. **Channel Plan** – map owned, shared, and paid channels with cadence + owners. +4. **Asset Requirements** – detail creative needs, content formats, localization, and compliance. +5. **Governance Packet** – document approvals, brand guidelines, legal checkpoints, and comms plan. + +## Outputs +- Joint campaign brief (objectives, audience, narrative, KPIs, timeline). +- Asset + channel tracker with partner assignments and due dates. +- Risk + dependency log for cross-org coordination. +- Plan JSON entry stored/updated in `.claude/plans` for audit trail. + +## Agent/Skill Invocations +- `partner-marketer` – leads agenda and stakeholder alignment. +- `co-branding` skill – enforces visual + messaging standards. +- `asset-manager` – tracks deliverables and approval workflow. + +## GTM Agents Safeguards +- **Fallback agents**: note substitutes (e.g., Partner Ops covering Partner Marketer) when stakeholders unavailable. +- **Escalation triggers**: if approvals or legal checkpoints miss SLA twice or partners deviate from guardrails, escalate to governance council per GTM Agents rip-cord. +- **Plan maintenance**: update plan JSON/change log whenever objectives, owners, or compliance requirements change to keep audit parity. + +--- diff --git a/commands/manage-assets.md b/commands/manage-assets.md new file mode 100644 index 0000000..71283e6 --- /dev/null +++ b/commands/manage-assets.md @@ -0,0 +1,48 @@ +--- +name: manage-assets +description: Coordinates co-branded asset production, approvals, and distribution across partners. +usage: /partner-co-marketing-orchestration:manage-assets --campaign "AI Launch Tour" --repo drive --approvers "brand,legal" +--- + +# Command: manage-assets + +## Inputs +- **campaign** – reference campaign/program name. +- **repo** – asset repository (Drive, Dropbox, SharePoint, DAM) to track. +- **approvers** – comma-separated stakeholder groups (brand, legal, product, partner). +- **locales** – optional list of localization requirements. +- **compliance** – optional flags for regulated industries. + +### GTM Agents Pattern & Plan Checklist +> Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325. + +- **Pattern selection**: Asset management typically runs **pipeline** (inventory → guardrails → approvals → versioning → distribution). If approvals across partners can run in parallel, document a **diamond** segment and merge gate in the plan. +- **Plan schema**: Save `.claude/plans/plan-.json` capturing campaign, repositories, task IDs, partner owners, dependency graph (legal, translation, DAM), error handling, and success metrics (approval SLA, asset quality, localization coverage). +- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for asset diff reviews, Context7 for partner brand/legal guidance, Sequential Thinking for cross-org approval cadences, Playwright for accessibility/landing page QA if needed. +- **Guardrails**: Default retry limit = 2 for failed approvals/uploads; escalation ladder = Asset Manager → Partner Ops → Joint governance council. +- **Review**: Use `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before execution to confirm owners, dependencies, deliverables. + +## Workflow +1. **Inventory Setup** – pull required asset list from `co-plan-campaign`, map owners + due dates. +2. **Co-branding Guardrails** – apply templates, logos, disclaimers, and accessibility checks per partner. +3. **Approval Routing** – trigger review workflows, capture feedback, and log decisions. +4. **Version Control** – store final assets with metadata (version, locale, usage notes). +5. **Distribution** – package assets for activation teams with instructions, tracking parameters, and expiration dates. + +## Outputs +- Asset tracker (status, owner, reviewer, link, compliance notes). +- Approval log referencing evidence + timestamps. +- Distribution bundle with metadata sheet and partner instructions. +- Plan JSON entry stored/updated in `.claude/plans` for audit trail. + +## Agent/Skill Invocations +- `co-marketing-asset-manager` – oversees production + routing. +- `asset-approval` skill – enforces review workflows and evidence capture. +- `co-branding` skill – validates visual/messaging requirements. + +## GTM Agents Safeguards +- **Fallback agents**: document substitutes (e.g., Partner Marketer covering Asset Manager) when leads unavailable. +- **Escalation triggers**: if approvals exceed SLA twice, compliance issues arise, or assets violate guardrails, escalate per GTM Agents rip-cord to partner governance committee. +- **Plan maintenance**: update plan JSON/change log whenever repositories, approvers, or compliance scopes shift. + +--- diff --git a/commands/track-source.md b/commands/track-source.md new file mode 100644 index 0000000..b97cf03 --- /dev/null +++ b/commands/track-source.md @@ -0,0 +1,48 @@ +--- +name: track-source +description: Aligns attribution, dashboards, and ROI reporting for partner co-marketing campaigns. +usage: /partner-co-marketing-orchestration:track-source --campaign "AI Launch Tour" --window 30d --detail full +--- + +# Command: track-source + +## Inputs +- **campaign** – joint campaign identifier matching briefs/assets. +- **window** – time range for analysis (7d, 30d, campaign duration). +- **detail** – summary | full report depth. +- **dimensions** – optional breakdowns (partner, channel, asset, region). +- **attribution_model** – optional override (first-touch, last-touch, multi-touch). + +### GTM Agents Pattern & Plan Checklist +> Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325. + +- **Pattern selection**: Tracking/reporting usually runs **pipeline** (gather → normalize → attribute → insights → reporting). If normalization + attribution can run in parallel (separate partners), log a **diamond** segment with merge gate. +- **Plan schema**: Save `.claude/plans/plan-.json` with campaign, data sources, task IDs, dependency graph (CRM, MAP, analytics), error handling, and success metrics (attribution confidence, SLA adherence, partner satisfaction). +- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for data model diffs, Context7 for partner taxonomy docs, Sequential Thinking for readout cadence, Playwright for dashboard QA if embedded. +- **Guardrails**: Default retry limit = 2 for failed data pulls or reconciliation mismatches; escalation ladder = Co-marketing Analytics Lead → RevOps/Finance partners → Exec sponsors. +- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before execution to confirm agents, dependencies, deliverables. + +## Workflow +1. **Data Gathering** – ingest analytics/CRM data from both partners using shared taxonomy + UTM parameters. +2. **Normalization** – reconcile schemas, currencies, and funnel stages; dedupe overlapping records. +3. **Attribution Calculation** – apply agreed model to allocate pipeline/revenue across partners + channels. +4. **Insight Generation** – highlight top-performing assets, audience segments, and drop-off points. +5. **Reporting Package** – produce dashboards, executive summary, and recommended optimizations. + +## Outputs +- Attribution dashboard snapshot with partner/source breakdown. +- Revenue/pipeline contribution table vs targets. +- Optimization action list referencing asset or channel adjustments. +- Plan JSON entry stored/updated in `.claude/plans` for audit trail. + +## Agent/Skill Invocations +- `co-marketing-analytics-lead` – validates data + insights. +- `attribution` skill – enforces methodology consistency. +- `partner-marketer` – receives recommendations for next sprint. + +## GTM Agents Safeguards +- **Fallback agents**: note substitutes (e.g., Partner Marketer covering Analytics Lead) if specialists unavailable. +- **Escalation triggers**: if attribution accuracy drops below guardrails twice or partners dispute sourced pipeline, escalate to revenue/partner governance board per GTM Agents rip-cord. +- **Plan maintenance**: update plan JSON/change log when models, data sources, or reporting cadences change to maintain audit parity. + +--- diff --git a/plugin.lock.json b/plugin.lock.json new file mode 100644 index 0000000..0160bf0 --- /dev/null +++ b/plugin.lock.json @@ -0,0 +1,77 @@ +{ + "$schema": "internal://schemas/plugin.lock.v1.json", + "pluginId": "gh:gtmagents/gtm-agents:plugins/partner-co-marketing-orchestration", + "normalized": { + "repo": null, + "ref": "refs/tags/v20251128.0", + "commit": "2a7fc4f073bd60e62445386a6343eb05c1f84044", + "treeHash": "5ddce5f35cf1b489eab448a47a611a303516d2cdaaffd4a12402c86dfbe53507", + "generatedAt": "2025-11-28T10:17:20.282566Z", + "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": "partner-co-marketing-orchestration", + "description": "Partner co-marketing orchestration covering joint planning, assets, and attribution", + "version": "1.0.0" + }, + "content": { + "files": [ + { + "path": "README.md", + "sha256": "6b7d6c097afe12772599689e6042e2d532b8186af0e8ed2882570b4497ea028b" + }, + { + "path": "agents/co-marketing-asset-manager.md", + "sha256": "a7c709f96f6be311458a80a4ee3073981efcc7380e2e757432aa27233225ad36" + }, + { + "path": "agents/co-marketing-analytics-lead.md", + "sha256": "c07c3506d6f86c6b39648a87c69e1a95d9a8a9b316b1b71c2056aee217eacd2c" + }, + { + "path": "agents/partner-marketer.md", + "sha256": "56374984ccb5afe103a3e44ef8a612c02e6238675b446b22997c3537611c44f3" + }, + { + "path": ".claude-plugin/plugin.json", + "sha256": "dda9cbd29f071ab6086b8cce2a407e1365d0d7790a842686f224ca414210d805" + }, + { + "path": "commands/co-plan-campaign.md", + "sha256": "0f866b0a73b6240f5e5859485dcda4e7be85b3ef9b8fe259672df9c9f1d24553" + }, + { + "path": "commands/manage-assets.md", + "sha256": "8deffd8cf5e8fd404ef88ca6e7e9266c6be215a99aeb5c95fb4b54a58147c216" + }, + { + "path": "commands/track-source.md", + "sha256": "38ea76a7b1d7efa149b5097f2ac26e67d95d065bfa8d124ab00737e22bcf841b" + }, + { + "path": "skills/asset-approval/SKILL.md", + "sha256": "1962c3b3396b8a14f82fb91df23dcfcb45338ddbbbb5943bca9c9f00731bb218" + }, + { + "path": "skills/attribution/SKILL.md", + "sha256": "8b28faa0596d285625e81933f9f13d0818c3ef69201945339376e9504ed111da" + }, + { + "path": "skills/co-branding/SKILL.md", + "sha256": "78b9871c4bac95a6ff2912bd9b7f22d41253ed30f28ab513c839cd80479f5420" + } + ], + "dirSha256": "5ddce5f35cf1b489eab448a47a611a303516d2cdaaffd4a12402c86dfbe53507" + }, + "security": { + "scannedAt": null, + "scannerVersion": null, + "flags": [] + } +} \ No newline at end of file diff --git a/skills/asset-approval/SKILL.md b/skills/asset-approval/SKILL.md new file mode 100644 index 0000000..7a33e06 --- /dev/null +++ b/skills/asset-approval/SKILL.md @@ -0,0 +1,31 @@ +--- +name: asset-approval +description: Use to manage co-marketing asset reviews with traceable evidence and + SLAs. +--- + +# Asset Approval Workflow Skill + +## When to Use +- Coordinating creative reviews across multiple partner stakeholders. +- Auditing compliance for regulated industries. +- Preventing go-live delays caused by unclear feedback loops. + +## Framework +1. **Review Matrix** – define reviewers per asset type (brand, legal, product, regional) and required evidence. +2. **SLA Cadence** – set response times, reminder schedule, and escalation triggers. +3. **Feedback Channels** – standardize annotation tools, version naming, and acceptance criteria. +4. **Sign-off Logging** – capture final approvals with timestamps, approver names, and file hashes. +5. **Change Control** – document post-approval edits, expiration dates, and refresh plans. + +## Templates +- Approval tracker (asset → reviewer → status → notes → evidence link). +- SLA chart outlining response times by priority level. +- Change request form for post-approval edits. + +## Tips +- Use shared storage with permissions per partner to prevent accidental edits. +- Pair with `co-branding` skill to auto-check brand compliance before review. +- Automate reminders via project tools to keep cross-company teams on schedule. + +--- diff --git a/skills/attribution/SKILL.md b/skills/attribution/SKILL.md new file mode 100644 index 0000000..5be4f42 --- /dev/null +++ b/skills/attribution/SKILL.md @@ -0,0 +1,31 @@ +--- +name: attribution +description: Use to define measurement, data sharing, and ROI reporting for joint + campaigns. +--- + +# Co-marketing Attribution Playbook Skill + +## When to Use +- Planning measurement strategy for joint campaigns or events. +- Reconciling attribution discrepancies between partner analytics stacks. +- Preparing executive or partner reports on shared pipeline/revenue impact. + +## Framework +1. **Taxonomy Alignment** – agree on UTM structure, campaign IDs, stages, and conversion definitions. +2. **Data Exchange** – determine cadence, format, security requirements, and normalization rules. +3. **Attribution Models** – select methods (first/last/multi-touch, split attribution, weighted models) and document assumptions. +4. **Governance** – define owners for metric updates, dispute resolution, and audit trails. +5. **Storytelling** – package dashboards and narratives for stakeholders, highlighting joint impact and next steps. + +## Templates +- Attribution worksheet (source → partner → funnel stage → revenue). +- Data sharing checklist (fields, format, frequency, security). +- Reporting deck outline (KPIs, insights, actions). + +## Tips +- Run attribution dry-runs before launch to catch data gaps. +- Include qualitative context (partner reach, brand lift) alongside quantitative metrics. +- Pair with `track-source` command to keep reports consistent across cycles. + +--- diff --git a/skills/co-branding/SKILL.md b/skills/co-branding/SKILL.md new file mode 100644 index 0000000..858797d --- /dev/null +++ b/skills/co-branding/SKILL.md @@ -0,0 +1,31 @@ +--- +name: co-branding +description: Use to enforce visual, messaging, and legal standards across partner + campaigns. +--- + +# Co-branding Guidelines Skill + +## When to Use +- Designing shared assets, landing pages, and creative for partner initiatives. +- Reviewing partner-submitted collateral before distribution. +- Training agencies or external teams on brand usage. + +## Framework +1. **Brand Hierarchy** – determine logo lockups, dominance rules, color usage, and typography. +2. **Messaging Alignment** – define shared narrative, value props, boilerplate, and CTA guidance. +3. **Legal/Compliance** – include disclaimers, TM/® usage, privacy statements, and required approvals. +4. **Localization** – document translation rules, regional references, and regulatory considerations. +5. **Version Control** – track asset versions, expiry dates, and update cadence. + +## Templates +- Co-branding checklist (logos, copy, disclaimers, accessibility, localization). +- Messaging matrix (audience → key message → proof points → CTA). +- Visual reference guide with approved mockups. + +## Tips +- Keep editable templates in shared workspaces to reduce iteration time. +- Pair with `asset-approval` skill for evidence tracking. +- Log exceptions with rationale and expiration date. + +---