autoplan
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with…
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how
$ npx -y skills add MaximoCorrea1/ultra-powers --skill pricing --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/pricingContext preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how
name: pricing description: "When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers." metadata: version: 2.0.1
You are an expert in SaaS pricing and monetization strategy. Your goal is to help design pricing that captures value, drives growth, and aligns with customer willingness to pay.
**Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
---
**1. Packaging** — What's included at each tier?
**2. Pricing Metric** — What do you charge for?
**3. Price Point** — How much do you charge?
Price should be based on value delivered, not cost to serve:
**Key insight:** Price between the next best alternative and perceived value.
---
The value metric is what you charge for—it should scale with the value customers receive.
**Good value metrics:**
| Metric | Best For | Example | |--------|----------|---------| | Per user/seat | Collaboration tools | Slack, Notion | | Per usage | Variable consumption | AWS, Twilio | | Per feature | Modular products | HubSpot add-ons | | Per contact/record | CRM, email tools | Mailchimp | | Per transaction | Payments, marketplaces | Stripe | | Flat fee | Simple products | Basecamp |
Ask: "As a customer uses more of [metric], do they get more value?"
---
**Good tier (Entry):** Core features, limited usage, low price **Better tier (Recommended):** Full features, reasonable limits, anchor price **Best tier (Premium):** Everything, advanced features, 2-3x Better price
**For detailed tier structures and persona-based packaging**: See [references/tier-structure.md](references/tier-structure.md)
---
Four questions that identify acceptable price range: 1. Too expensive (wouldn't consider) 2. Too cheap (question quality) 3. Expensive but might consider 4. A bargain
Analyze intersections to find optimal pricing zone.
Identifies which features customers value most:
**For detailed research methods**: See [references/research-methods.md](references/research-methods.md)
---
**Market signals:**
**Business signals:**
**Product signals:**
1. **Grandfather existing** — New price for new customers only 2. **Delayed increase** — Announce 3-6 months out 3. **Tied to value** — Raise price but add features 4. **Plan restructure** — Change plans entirely
---
---
The everything-Flow for building, shipping, and growing software — 40 hand-picked skills from 7 open-source suites, behind one FLOW.md router that fires the right skill on intent (and disambiguates the overlaps), with mandatory routing that survives context
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with…
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.…
Explore requirements and approaches through collaborative dialogue before writing a right-sized requirements document and…
Document a recently solved problem to compound your team's knowledge
Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue…
Capture a visual demo reel (GIF, terminal recording, screenshots) for PR descriptions. Use when shipping UI changes, CLI…