Pricing and packaging change log

Pricing changes touch more places than almost any other change: the website, billing, contracts, sales decks, help docs, in-app limits. The log makes sure each change is recorded once and carried everywhere.

Before you start

If .agents/product-ops-context.md exists (or .claude/product-ops-context.md), read it first. Use the team, owners, tools, meetings, and metric definitions it already has, and only ask for what's missing or specific to this task. If it doesn't exist, go ahead with what you're given, and suggest running product-ops-context once so the next skill doesn't have to ask.

Step 1: Log the change

### [Short title, e.g. "Advanced reporting moves from Pro to Business"]
- **Effective date:** [date]
- **Type:** Price change / Feature moved between plans / Limit change / New plan / Plan retired / Discount or promo policy
- **What changed:**
  - Before: [plan, price, limit, or inclusion]
  - After: [plan, price, limit, or inclusion]
- **Applies to:** New customers / Existing customers at renewal / All customers immediately
- **Grandfathering:** [who keeps the old terms, and until when]
- **Approved by:** [person]
- **Reason:** [as given]
- **Source:** [link to decision, deck, or doc]

Rules:

• Before and after must be specific enough to check against billing.
• If the effective date, who it applies to, or grandfathering isn't stated, flag it. These are the three things that cause the most customer disputes.
• Record the change as decided. Proposals stay out of the log until approved.

Step 2: Track the rollout

For each change, check every place it has to land:

A change isn't done until every row that applies is Yes.

Step 3: Answer "what did this plan include?"

When asked what a plan included on a past date, read the log in date order up to that date and answer with the plan's state then, citing the entries used. If the log doesn't go back far enough, say so.

The log

# Pricing and packaging change log

| Date | Change | Plans affected | Applies to | Approved by | Rollout complete? |
|---|---|---|---|---|---|

[Full entries below, newest first]

## Open rollouts
- [Change]: still missing [where] — Owner: [name]

Never change prices, plans, or billing settings yourself. This skill records and tracks.

Related skills

• internal-enablement-brief — brief sales and support on the change
• decision-log — record who approved it and why
• deprecation-plan — when a plan is being retired