mcpField
J
joint-solution-blueprint

joint-solution-blueprint

github.com/gtmagentsMarketing & growth42863 installsUpdated 30w ago
Repository

About joint-solution-blueprint

A skill for structuring co-built integrations and packaged services, from use-case definition through launch and support. It gives product, marketing, partner, and field teams shared architecture, value, and planning materials.

Key features

  1. 01Use-case and success-metric definition
  2. 02Architecture and data-flow outline
  3. 03Customer value narrative
  4. 04Go-to-market planning
  5. 05Support and lifecycle roles
  6. 06Solution brief and launch templates

Use cases

  1. 01Launching a jointly built integration
  2. 02Preparing field teams with technical and value details
  3. 03Coordinating product, marketing, and partner enablement

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill joint-solution-blueprint

After installing, type/joint-solution-blueprintin Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported