mcpField
B
brand-governance-os

brand-governance-os

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

About brand-governance-os

A skill for establishing and scaling brand governance across campaigns, product surfaces, and regions. It organizes intake, reviews, QA, training, reporting, and escalation through workflows and templates.

Key features

  1. 01Request intake and routing rules
  2. 02Copy, design, product, and legal reviews
  3. 03Pre-launch QA and accessibility checks
  4. 04Training and enablement materials
  5. 05Governance reporting and escalation

Use cases

  1. 01Starting a brand governance program
  2. 02Coordinating approvals across campaigns and regions
  3. 03Tracking compliance, exceptions, and escalations

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill brand-governance-os

After installing, type/brand-governance-osin Claude Code to confirm it loaded.

Bundled filesassets/governance_checklist.md

Details

From the project README

Brand Governance OS Skill

When to Use

  • Standing up or scaling brand governance programs.
  • Coordinating approvals across campaigns, product surfaces, and regional teams.
  • Tracking compliance, exceptions, and escalations.

Framework

  1. Intake Layer – request forms, SLAs, routing rules, auto-assign logic.
  2. Review Workflows – checklists for copy, design, product, legal; scoring rubrics.
  3. QA Automation – pre-launch audits, screenshot diffing, accessibility + localization checks.
  4. Training & Enablement – office hours, certification paths, knowledge base updates.
  5. Reporting & Escalation – dashboards, exception logs, policy updates, exec summaries.

Templates

  • Governance Checklist: See assets/governance_checklist.md for review criteria.
  • Intake form with fields for campaign type, stage, risk level, required reviewers.
  • Feedback doc with structured comments, severity tags, and action owners.
  • Governance dashboard template covering throughput, cycle time, and compliance.

Tips

  • Provide "fast lane" criteria for low-risk requests to keep velocity high.
  • Rotate reviewers to avoid bottlenecks and expose more teams to best practices.
  • Pair with run-brand-governance-council to automate agenda + decision logs.

Comments

Markdown supported