Skip to content
Back to skills

Pricing Governance

ASecurity

Use to run pricing councils, track decisions, and enforce approval workflows.

  • 396 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added February 7, 2026
businessgoperformance

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add gtmagents/gtm-agents --skill pricing-governance --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pricing Governance?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Pricing Governance
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gtmagents-pricing-governance/badge)](https://www.skillsdirectory.com/skills/gtmagents-pricing-governance)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: pricing-governance
description: Use to run pricing councils, track decisions, and enforce approval workflows.
---

# Pricing Governance Playbook Skill

## When to Use
- Facilitating pricing council meetings or steering committees.
- Logging approvals, assumptions, and launch timing for pricing changes.
- Auditing pricing experiments or discount policy adjustments.

## Framework
1. **Council Charter** – define members, meeting cadence, decision rights, and escalation paths.
2. **Decision Log** – capture proposals, outcomes, rationales, and follow-up actions.
3. **Approval Matrix** – map thresholds (discount %, price change scope) to required approvers.
4. **Communication Hooks** – standardize templates for stakeholder updates and launch checklists.
5. **Audit Trail** – store artifacts (models, decks, FAQs) and post-launch performance reviews.

## Templates
- Council agenda + minutes doc.
- Decision log spreadsheet with filters.
- Launch readiness checklist with owners/dates.

## Tips
- Keep logs centralized to reduce drift across regions.
- Pair with `enablement-kit` to ensure decisions convert to frontline training.
- Schedule retro sessions at 30/60/90 days post-launch to validate assumptions.

---

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…