derive-tests
Turn documented intent into a test-coverage map — inventory the tests that exist today, derive use-case cases from the system docs, separate existing coverage…
Design a pricing strategy — models, competitive analysis, willingness-to-pay estimation, and pricing experiments
> /plugin marketplace add phuryn/pm-skillsHow it fires
How this command gets triggered: by you, by Claude, or both.
/pricingContext preview
What this command does when you run it.
Design a pricing strategy — models, competitive analysis, willingness-to-pay estimation, and pricing experiments
description: Design a pricing strategy — models, competitive analysis, willingness-to-pay estimation, and pricing experiments argument-hint: "<product or pricing question>"
Build a pricing strategy from first principles: analyze pricing models, estimate willingness to pay, benchmark against competitors, and design pricing experiments.
/pricing SaaS project management tool moving from free to paid /pricing Should we switch from per-seat to usage-based pricing? /pricing [upload competitor pricing pages or current pricing data]
Ask:
Apply the **pricing-strategy** and **monetization-strategy** skills:
Evaluate applicable models:
For each relevant model: pros, cons, fit for your product, revenue projection approach.
Using web research:
If the user has survey data or customer feedback:
If no data:
## Pricing Strategy: [Product] **Date**: [today] **Current pricing**: [if applicable] ### Recommended Model: [Model Name] **Why this model**: [rationale tied to product value delivery] ### Pricing Structure | Tier | Price | Includes | Target Segment | Key Limit | |------|-------|---------|---------------|-----------| ### Free / Trial Strategy [What's free, what's gated, conversion triggers] ### Competitive Benchmark | Competitor | Model | Price Range | Positioning | |-----------|-------|-----------|------------| ### Revenue Projections | Scenario | Assumptions | Year 1 ARR | Year 2 ARR | |----------|-----------|-----------|-----------| | Conservative | [X] | [Y] | [Z] | | Expected | [X] | [Y] | [Z] | | Optimistic | [X] | [Y] | [Z] | ### Migration Plan [If changing pricing: how to transition existing customers] - Grandfathering approach - Communication plan - Timeline ### Pricing Experiments | Experiment | What We're Testing | Method | Duration | |-----------|-------------------|--------|----------| ### Risks and Mitigations | Risk | Likelihood | Impact | Mitigation | |------|-----------|--------|-----------| ### Key Metrics to Track - Conversion rate by tier - Average revenue per user (ARPU) - Upgrade/downgrade rates - Churn by price sensitivity - Price elasticity signals
Save as markdown.
68 PM skills and 42 chained workflows across 9 plugins. Claude Code, Cowork, and more. From discovery to strategy, execution, launch, growth, and shipping AI-built code. Designed for Claude Code and Cowork. Skills compatible with other AI assistants.
Repo: phuryn/pm-skills
Turn documented intent into a test-coverage map — inventory the tests that exist today, derive use-case cases from the system docs, separate existing coverage…
Reverse-engineer an AI-built codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus…
Static performance audit of AI-built code — find N+1 queries and request waterfalls, over-fetching, missing indexes, and caching opportunities, ranked by…
Static security audit of AI-built code — map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed…
Turn a vibe-coded repo into a reviewer-ready shipping packet — document the app, wire agent context, run security and performance audits, map test coverage,…
Perform cohort analysis on user data — retention curves, feature adoption, and engagement trends