Initial commit

This commit is contained in:
Zhongwei Li
2025-11-29 18:31:11 +08:00
commit aaf4d5d426
13 changed files with 417 additions and 0 deletions

View File

@@ -0,0 +1,25 @@
{
"name": "partnership-development",
"description": "Partner strategy, co-selling, and co-marketing governance for ecosystem growth",
"version": "1.0.0",
"author": {
"name": "GTM Agents",
"email": "opensource@intentgpt.ai"
},
"skills": [
"./skills/partner-ecosystem-map/SKILL.md",
"./skills/joint-solution-blueprint/SKILL.md",
"./skills/partner-revenue-desk/SKILL.md",
"./skills/co-marketing-governance/SKILL.md"
],
"agents": [
"./agents/partner-strategy-director.md",
"./agents/partner-co-sell-lead.md",
"./agents/partner-program-architect.md"
],
"commands": [
"./commands/design-partner-ecosystem.md",
"./commands/build-co-sell-playbook.md",
"./commands/run-partner-qbr.md"
]
}

3
README.md Normal file
View File

@@ -0,0 +1,3 @@
# partnership-development
Partner strategy, co-selling, and co-marketing governance for ecosystem growth

View File

@@ -0,0 +1,27 @@
---
name: partner-co-sell-lead
description: Orchestrates co-selling motions, pipeline governance, and field enablement with partners.
model: sonnet
---
# Partner Co-Sell Lead Agent
## Responsibilities
- Manage joint pipeline hygiene, forecasting, and attribution across partners.
- Align partner managers, sales, and marketing on co-selling plays.
- Coordinate enablement, incentives, and deal support for partner-sourced opportunities.
- Track co-selling performance, unblock escalations, and share success stories.
## Workflow
1. **Pipeline Intake** ingest joint opportunities, validate data quality, and rank by impact.
2. **Governance Cadence** run weekly co-sell standups, assign actions, and escalate blockers.
3. **Enablement & Support** distribute decks, proof points, incentives, and reference kits.
4. **Forecast & Reporting** publish coverage, win rates, and attribution insights to leadership.
5. **Feedback Loop** collect partner + AE feedback to evolve plays and incentives.
## Outputs
- Co-sell pipeline dashboard with coverage + forecast.
- Weekly action tracker for partner + AE teams.
- Win story library + enablement kits for high-impact deals.
---

View File

@@ -0,0 +1,27 @@
---
name: partner-program-architect
description: Designs partner onboarding, enablement, and lifecycle programs.
model: haiku
---
# Partner Program Architect Agent
## Responsibilities
- Build onboarding paths, certification tracks, and enablement kits per partner tier.
- Coordinate marketing, product, and CS resources for partner success.
- Track partner engagement, accreditation, and pipeline contribution.
- Operate partner community, communications, and feedback loops.
## Workflow
1. **Program Design** define onboarding steps, credentials, and engagement milestones.
2. **Content & Tools** assemble playbooks, asset hubs, and automation workflows.
3. **Activation & Support** run workshops, office hours, and escalation channels.
4. **Performance Tracking** monitor engagement, certification, and revenue metrics.
5. **Iteration** capture partner feedback, update curriculum, and share updates.
## Outputs
- Partner program blueprint with journeys, assets, and SLAs.
- Enablement content calendar + resource hub index.
- Engagement report with metrics, highlights, and next actions.
---

View File

@@ -0,0 +1,28 @@
---
name: partner-strategy-director
description: Defines partner ecosystem strategy, segmentation, and operating model.
model: sonnet
---
# Partner Strategy Director Agent
## Responsibilities
- Map ecosystem tiers, ideal partner profiles, and whitespace opportunities.
- Build multi-year partner roadmap aligned to revenue and product goals.
- Align legal, finance, marketing, and sales on partnership motions.
- Track portfolio performance, escalate risks, and spotlight breakout partners.
## Workflow
1. **Market Scan** analyze ecosystem trends, competitor alliances, and customer demand.
2. **Portfolio Design** prioritize partner types, tiers, incentives, and investment levels.
3. **Operating Model** define governance, scorecards, enablement, and co-selling frameworks.
4. **Review Cadence** run quarterly portfolio reviews with leadership and partner teams.
5. **Playbook Iteration** document learnings, refresh ICPs, and share best practices.
## Outputs
- Partner strategy memo + roadmap.
- Tiering/scorecard definitions with KPIs, incentives, and SLAs.
- Leadership briefings with investment recommendations.
---

View File

@@ -0,0 +1,34 @@
---
name: build-co-sell-playbook
description: Creates a partner co-selling playbook with cadences, enablement, and attribution rules.
usage: /partnership-development:build-co-sell-playbook --partner "Nimbus AI" --motion enterprise --incentives spiff,spif --targets 3MM
---
# Command: build-co-sell-playbook
## Inputs
- **partner** partner or alliance name/ID.
- **motion** sell-with motion (enterprise, midmarket, channel, marketplace, MSSP).
- **incentives** comma-separated incentives (spiff, rebate, MDF, overlay, attach bonus).
- **targets** revenue/opportunity goal for the motion.
- **audience** field | partner-team | exec | async; changes fidelity and outputs.
## Workflow
1. **Discovery & Alignment** capture joint value prop, ICP overlap, and mutual goals.
2. **Play Design** define stages, responsibilities, enablement assets, and required approvals.
3. **Attribution & Governance** outline tracking, CRM stages, and escalation channels.
4. **Enablement Kit** package talk tracks, ROI assets, pricing guidance, and case studies.
5. **Launch & Measurement** define targets, reporting cadence, and success scorecard.
## Outputs
- Co-sell playbook PDF/deck with steps, owners, and SLAs.
- Enablement bundle (battlecard, talk track, ROI calculator references).
- KPI dashboard spec with attribution + reporting requirements.
## Agent/Skill Invocations
- `partner-co-sell-lead` drives pipeline governance + enablement.
- `partner-program-architect` ensures onboarding + certification hooks are embedded.
- `joint-solution-blueprint` skill codifies solution architecture and value prop.
- `co-marketing-governance` skill wires in awareness + demand-gen workflows.
---

View File

@@ -0,0 +1,34 @@
---
name: design-partner-ecosystem
description: Builds partner ecosystem strategy, tiering, and investment plan.
usage: /partnership-development:design-partner-ecosystem --markets enterprise,smb --focus services,technology --horizon 12m
---
# Command: design-partner-ecosystem
## Inputs
- **markets** target markets or segments (enterprise, midmarket, smb, geo).
- **focus** partner types (technology, services, channel, marketplace, alliances).
- **horizon** planning window (6m, 12m, 24m).
- **capacity** optional number of net-new partners to onboard.
- **constraints** budget, compliance, or integration limits.
## Workflow
1. **Market & Customer Insights** evaluate demand signals, buyer requests, and product roadmap alignment.
2. **Partner Profiling** define ideal partner characteristics, value props, and differentiation.
3. **Tiering & Incentives** design tiers, benefits, KPIs, and investment requirements.
4. **Operating Model** outline governance, onboarding, enablement, and co-selling expectations.
5. **Roadmap & Investment Plan** prioritize recruits, resourcing, and success metrics for the planning horizon.
## Outputs
- Partner ecosystem strategy doc with roadmap + investment plan.
- Tiering model + scorecards for evaluating and managing partners.
- KPIs and governance cadence for leadership approval.
## Agent/Skill Invocations
- `partner-strategy-director` leads strategy and roadmap creation.
- `partner-program-architect` translates tiers into enablement programs.
- `partner-ecosystem-map` skill visualizes current vs target coverage.
- `partner-revenue-desk` skill models revenue impact and incentives.
---

View File

@@ -0,0 +1,35 @@
---
name: run-partner-qbr
description: Produces partner QBR/EBR packet with pipeline, GTM programs, and action items.
usage: /partnership-development:run-partner-qbr --partner "Nimbus AI" --window quarter --audience exec --format deck
---
# Command: run-partner-qbr
## Inputs
- **partner** partner/alliance name or ID.
- **window** time horizon (quarter, half, year, custom).
- **audience** exec | partner-leadership | field | async.
- **format** deck | memo | dashboard | loom.
- **focus** optional emphasis (pipeline, co-marketing, product, success, expansion).
## Workflow
1. **Data Gathering** assemble pipeline, revenue, marketing, and enablement metrics.
2. **Insight Layer** highlight trends, wins, blockers, and benchmark comparisons.
3. **Joint Initiatives** summarize in-flight programs, dependencies, and budget usage.
4. **Action & Decision Log** capture required approvals, investments, and follow-ups.
5. **Packaging** tailor presentation + briefing notes for requested audience + format.
## Outputs
- QBR/EBR deck or memo with KPIs, highlights, and blockers.
- Action tracker with owners, due dates, and status.
- Executive summary + talking points for partner and internal sponsors.
## Agent/Skill Invocations
- `partner-strategy-director` curates narrative + investment asks.
- `partner-co-sell-lead` provides pipeline + forecast insights.
- `partner-program-architect` updates enablement + activation status.
- `co-marketing-governance` skill injects program performance + next steps.
- `partner-ecosystem-map` skill visualizes coverage vs goals.
---

81
plugin.lock.json Normal file
View File

@@ -0,0 +1,81 @@
{
"$schema": "internal://schemas/plugin.lock.v1.json",
"pluginId": "gh:gtmagents/gtm-agents:plugins/partnership-development",
"normalized": {
"repo": null,
"ref": "refs/tags/v20251128.0",
"commit": "04d802bbb4cb3ee1c3a773f4ad16646a75ecc814",
"treeHash": "d41fca0ff98718435d946f0e9dbfee3e038b6514b3b30b526c864af00324b590",
"generatedAt": "2025-11-28T10:17:15.872263Z",
"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": "partnership-development",
"description": "Partner strategy, co-selling, and co-marketing governance for ecosystem growth",
"version": "1.0.0"
},
"content": {
"files": [
{
"path": "README.md",
"sha256": "0d83f85ce1ddea3366e0732d6842d6824cdd900ccb4c68fd74cc8c6881e4bfa2"
},
{
"path": "agents/partner-program-architect.md",
"sha256": "d3e7c8132f13fb981910bcb42f11ed020351b395c022e9dfb4f889c31edffbad"
},
{
"path": "agents/partner-strategy-director.md",
"sha256": "267966aa9f8d134f4fdc11a4b51bf7197efc1865eff5db655b20149ee97e85d6"
},
{
"path": "agents/partner-co-sell-lead.md",
"sha256": "455a54e277bbb40ad77789cb60a0aea2ebe757daae1e6ffc53c1a00560c8397e"
},
{
"path": ".claude-plugin/plugin.json",
"sha256": "53d322af02c18a468f239f7841ed90f318e5fd5b806cb4eb70ccc603c4ad3fc6"
},
{
"path": "commands/run-partner-qbr.md",
"sha256": "df787c71390fcbbcf96a427c5f266a4ee29a9cc72e86faa7ab71b3d24b0d6253"
},
{
"path": "commands/design-partner-ecosystem.md",
"sha256": "c88fc36df52a3a451226b76ea80dec643186b266f74e196c43f9ad8a159f2862"
},
{
"path": "commands/build-co-sell-playbook.md",
"sha256": "b068325a93c7b01d93a7e8f82ea0cba5c821fe3347c19af485b652396a879ab2"
},
{
"path": "skills/partner-ecosystem-map/SKILL.md",
"sha256": "8b21f0cb65eb658755e4b5d96ee6779180fac389ae8afef87244c6f86876102c"
},
{
"path": "skills/co-marketing-governance/SKILL.md",
"sha256": "715cb985a920fcae648992fdd8daf973a776baa93f128239f964efa26763a208"
},
{
"path": "skills/joint-solution-blueprint/SKILL.md",
"sha256": "caf7dda83255699e14b962ecea307b568b56c07cc8a7fde16fa48bf92dd1e5d3"
},
{
"path": "skills/partner-revenue-desk/SKILL.md",
"sha256": "49e86e872005d4d66e5d05c41627e3b3b8e7530f0da5f6c596cd5a9c3c7ccafe"
}
],
"dirSha256": "d41fca0ff98718435d946f0e9dbfee3e038b6514b3b30b526c864af00324b590"
},
"security": {
"scannedAt": null,
"scannerVersion": null,
"flags": []
}
}

View File

@@ -0,0 +1,31 @@
---
name: co-marketing-governance
description: Governance playbook for joint marketing programs, MDF, and performance
reviews.
---
# Co-Marketing Governance Skill
## When to Use
- Planning joint campaigns, launches, or events with partners.
- Managing MDF budgets, approvals, and performance tracking.
- Preparing partner QBRs or exec updates focused on demand-generation impact.
## Framework
1. **Program Intake** business case, audience, KPIs, required assets, legal/compliance checks.
2. **Approval Workflow** decision matrix for marketing, partner, and finance stakeholders.
3. **Execution Cadence** sprint plan, shared tracking sheets, and content governance.
4. **Measurement & Attribution** agreed metrics (MQLs, pipeline, revenue, influence) + reporting cadence.
5. **Closeout & Learnings** retro template, MDF reconciliation, and next-play recommendations.
## Templates
- Co-marketing brief + approval form.
- MDF budget tracker with forecast vs actuals.
- Post-campaign report outline with KPIs and narrative prompts.
## Tips
- Align messaging with joint solution blueprints to keep storytelling consistent.
- Attach MDF approval deadlines to campaign calendars to avoid delays.
- Pair with `run-partner-qbr` to highlight impact and secure additional investment.
---

View File

@@ -0,0 +1,31 @@
---
name: joint-solution-blueprint
description: Template for documenting co-built solutions, integrations, and GTM motions
with partners.
---
# Joint Solution Blueprint Skill
## When to Use
- Launching or refreshing a co-built integration or packaged service.
- Equipping field teams with architecture, value props, and proof points.
- Coordinating enablement across product, marketing, and partner teams.
## Framework
1. **Use Case Definition** target persona, pain point, and success metrics.
2. **Architecture Overview** system diagram, data flows, dependencies, security notes.
3. **Value Narrative** customer outcomes, ROI proof, competitive differentiation.
4. **Go-To-Market Plays** positioning, pricing principles, launch checklist, asset library.
5. **Support & Lifecycle** roles, escalation paths, roadmap commitments.
## Templates
- One-page solution brief with messaging + CTA.
- Architecture diagram checklist.
- Launch plan with tasks, owners, and deadlines.
## Tips
- Keep diagrams simple enough for sales decks, with appendix for technical deep dives.
- Include customer stories or beta insights to increase credibility.
- Pair with `build-co-sell-playbook` so reps know how to pitch + progress deals.
---

View File

@@ -0,0 +1,30 @@
---
name: partner-ecosystem-map
description: Visualization toolkit for mapping partner landscape, coverage, and priorities.
---
# Partner Ecosystem Map Skill
## When to Use
- Planning partner strategy, territorial coverage, or whitespace analysis.
- Presenting ecosystem status to executives or cross-functional stakeholders.
- Tracking progress against partner recruitment and ramp goals.
## Framework
1. **Segmentation Layer** partner type, region, vertical, solution fit, maturity.
2. **Value Layer** pipeline contribution, ARR influenced, co-sell velocity, joint wins.
3. **Health Layer** certification status, enablement completion, NPS, engagement cadence.
4. **Gaps & Targets** highlight priority segments needing recruits or investment.
5. **Narrative Hooks** pair visuals with summary insights, risks, and next plays.
## Templates
- Ecosystem matrix with rows (partner type) × columns (value/health metrics).
- Geo overlay map for territory coverage vs whitespace.
- Executive summary slide linking visuals to investment requests.
## Tips
- Keep visuals updated monthly so leadership trusts the snapshot.
- Link each gap to a specific recruiting or enablement initiative.
- Pair with `design-partner-ecosystem` for streamlined planning packages.
---

View File

@@ -0,0 +1,31 @@
---
name: partner-revenue-desk
description: Operating model for tracking, attributing, and accelerating partner-sourced
revenue.
---
# Partner Revenue Desk Skill
## When to Use
- Forecasting partner-sourced/ influenced revenue for leadership updates.
- Monitoring incentives, SPIFs, and MDF utilization tied to partner pipeline.
- Coordinating RevOps, finance, and partner teams on attribution disputes.
## Framework
1. **Revenue Taxonomy** sourced vs influenced vs co-sell, stage definitions, SLAs.
2. **Process Flow** intake → validation → attribution → approval → reporting.
3. **Data Stack** CRM objects, PRM integrations, BI dashboards, alerting.
4. **Incentive Hooks** payout rules, MDF governance, exception workflows.
5. **Escalation Paths** playbooks for disputes, double counting, or compliance risks.
## Templates
- Revenue desk runbook with RACI + cadence.
- Attribution audit checklist.
- MDF utilization tracker with projected ROI.
## Tips
- Align definitions with finance early; lock requirements before launching SPIFs.
- Automate alerts for stalled partner deals to keep velocity high.
- Pair with `build-co-sell-playbook` and `run-partner-qbr` for closed-loop reporting.
---