playbooks

home / skills / gtmagents / gtm-agents / brand-governance-os

brand-governance-os skill

/plugins/brand-strategy/skills/brand-governance-os

This skill helps scale brand governance by automating intake, reviews, QA, and training across campaigns and regional teams.

npx playbooks add skill gtmagents/gtm-agents --skill brand-governance-os

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
1.4 KB
---
name: brand-governance-os
description: Operating system for intake, approvals, QA, and training across brand
  stakeholders.
---

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

---

Overview

This skill is an operating system for intake, approvals, QA, and training across brand stakeholders. It centralizes request routing, standardized review workflows, automated pre-launch checks, and governance reporting. The system is built to help teams scale consistent brand decisions while maintaining speed and visibility.

How this skill works

The skill exposes an intake layer with configurable forms, SLAs, and auto-assignment rules to route requests to the right reviewers. Review workflows use checklists, scoring rubrics, and severity-tagged feedback to capture decisions and required actions. QA automation runs pre-launch audits such as screenshot diffs, accessibility, and localization checks. Training and reporting modules provide certification paths, knowledge updates, dashboards, and escalation logs.

When to use it

  • Standing up or scaling a brand governance program across teams and regions.
  • Coordinating cross-functional approvals for campaigns, product surfaces, or creative assets.
  • Tracking compliance, exceptions, and escalation paths for high-risk launches.
  • Standardizing reviews to reduce rework and speed up time-to-market.
  • Implementing training and certification for reviewers and approvers.

Best practices

  • Define fast-lane criteria for low-risk requests to preserve velocity.
  • Use clear review checklists and scoring rubrics to produce consistent outcomes.
  • Rotate reviewers periodically to spread institutional knowledge and reduce bottlenecks.
  • Capture structured feedback with severity tags and explicit action owners.
  • Automate pre-launch QA (diffing, accessibility, localization) to catch regressions early.

Example use cases

  • An enterprise marketing team centralizes campaign intake and routes creative to regional legal and localizers.
  • A product organization enforces UI copy and accessibility checks before feature launches.
  • A distributed brand council runs certification paths and documents decision logs for executive reporting.
  • A revenue ops team uses dashboards to monitor throughput, cycle time, and compliance rates.
  • A creative studio applies fast-lane rules for templates while routing bespoke work through full review.

FAQ

Can this skill handle different risk levels and SLAs?

Yes. Intake forms capture risk level and the system applies SLA and routing rules so high-risk items follow stricter workflows.

How does QA automation integrate with reviews?

Automated checks run pre-launch and attach results to the review ticket, highlighting failures for reviewers to address before approval.