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,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.
---