zhongwei/gh-gtmagents-gtm-agents-plugins-partner-co-marketing-orchestration
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial commit

Browse Source
This commit is contained in:
Zhongwei Li
2025-11-29 18:31:09 +08:00
commit cabf62c281
12 changed files with 422 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

48
commands/co-plan-campaign.md Normal file
View File

@@ -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-<timestamp>.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.
---

48
commands/manage-assets.md Normal file
View File

@@ -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-<timestamp>.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.
---

48
commands/track-source.md Normal file
View File

@@ -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-<timestamp>.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.
---