smithery/gtmagents

governance

Use to establish ownership, cadences, and compliance for customer journey programs.

Installation

$ npx skills add smithery/gtmagents --skill governance

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/gtmagents · top by installs.

npx skills add smithery/gtmagents

Browse all from smithery/gtmagents

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,420 B
  • docs SUMMARY.md 101 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Journey Governance Framework Skill

When to Use

  • Standing up or refreshing journey councils and review cadences.
  • Coordinating multi-team initiatives that impact customer experience.
  • Preparing executive updates or compliance reviews tied to journey changes.

Framework

  1. Ownership Model – define RACI across CX strategist, product, marketing, CS, ops, and exec sponsors.
  2. Cadences – set quarterly journey reviews, monthly initiative standups, and weekly execution syncs.
  3. Documentation – maintain living journey maps, backlog tracker, decision log, and KPI dashboards.
  4. Change Control – outline approval steps, testing requirements, and communication plans for journey changes.
  5. Measurement & Accountability – set KPIs per initiative, assign owners, and track progress vs targets.

Templates

  • Governance charter (mission, scope, roles, cadences, tooling).
  • Decision log (request, decision, rationale, owner, follow-up date).
  • KPI dashboard outline for exec reviews.

Tips

  • Pair governance reviews with updated VOC and telemetry so decisions stay grounded in customer data.
  • Keep documentation in a shared workspace with version history.
  • Rotate spotlight sections in reviews to feature wins, experiments, and unresolved risks.