| name | pricing-packaging-planner |
| slug | aaron-pricing-packaging-planner |
| displayName | Pricing Packaging Planner · 发布定价打包 |
| summary | 发布定价/梯度打包/早鸟优惠/保证设计 |
| description | Use when the user asks to "plan launch pricing", "design pricing tiers / packaging", or "set up a launch discount / early-bird offer"; produces a launch pricing and packaging plan — tier structure and naming, a value-to-price map aligned to the message house, a launch-offer ladder with a true deadline reason, beta / early-adopter pricing with a post-launch graduation path, and guarantee / refund terms — with every price claim and offer term submitted to memory/events/claims.ndjson. Not for the canonical offer / claim record — use offer-claims-registry; not for paid-newsletter subscription economics — use newsletter-monetization-planner; not for ad bidding — use bid-strategy-planner. 发布定价/梯度打包/早鸟优惠/保证设计 |
| version | 20.1.0 |
| license | Apache-2.0 |
| compatibility | Claude Code and compatible agent-skill hosts |
| homepage | https://github.com/aaron-he-zhu/aaron-marketing-skills |
| when_to_use | Use when deciding what a launch will charge and how it is packaged: tier structure and tier naming, mapping tiers to the message-house value pillars, launch discounts with a real deadline reason, beta or early-adopter pricing and its graduation path to the GA price, and guarantee / refund design. The pricing lever of the RAMP Assemble phase — feeds the RAMP A pricing / packaging sub-item. The live offer record stays with offer-claims-registry; subscription-newsletter economics stay with newsletter-monetization-planner. |
| argument-hint | <product / offer> [launch goal: b2b / devtool / mobile] [current pricing if any] [launch date] |
| metadata | {"author":"aaron-he-zhu","version":"20.1.0","discipline":"launch","phase":"assemble","geo-relevance":"low","hermes":{"tags":["marketing","launch","assemble"],"category":"launch"},"openclaw":{"emoji":"🚀","homepage":"https://github.com/aaron-he-zhu/aaron-marketing-skills"}} |
Pricing Packaging Planner
Plans what a launch charges and how it is packaged — tier structure and naming, a value-to-price map tied to the message-house pillars, a launch-offer ladder with a true deadline reason, beta / early-adopter pricing with its graduation path, and guarantee / refund design. It sits in the Assemble phase of the RAMP loop and feeds the RAMP A sub-item "pricing & packaging clear (tiers, launch-offer terms, guarantee/refund)"; the pricing state it declares per stage (a live pricing page when GA promises public paid availability) is also what the R1 stage-truth check reads downstream. It works one lever — pricing/packaging — and hands off.
Every price claim, discount term, and guarantee wording it drafts is a candidate, not a live offer: it submits them to memory/events/claims.ndjson via an authorized operation: propose request to registry-events.py, and offer-claims-registry — whose offers.md is the live-offer SSOT — formalizes them.
Scope guard: this skill designs launch pricing and packaging only. It does not own the canonical offer / claim record (offer-claims-registry is the sole writer of memory/claims/ — this skill submits candidates), model paid-subscription newsletter economics (newsletter-monetization-planner), plan ad bids or auction strategy (bid-strategy-planner), or compute the RAMP profile result / run the RAMP vetoes (launch-readiness-auditor).
Quick Start
Plan launch pricing for [product]. ICP: [who]. Current pricing: [tiers / none — new product]. Launch goal: [B2B / dev-tool / mobile].
Design a 3-tier packaging with names for [product] — what goes in each tier, what each costs, and which value pillar each sells.
Set up a launch discount / early-bird offer for [launch date] — with a real deadline reason and the post-launch price path.
Skill Contract
Expected output: a launch pricing/packaging plan — named tiers with per-tier contents, a value-to-price map aligned to the message-house pillars, a launch-offer ladder with a true deadline rationale, a beta / early-adopter price with its declared graduation path, and guarantee / refund terms — plus the claim/term candidates routed to the registries and the standard handoff summary.
