Skip to content
Back to skills

Pm Pricing

ASecurity

Author or refresh a pricing plan — 2–3 monetization models with willingness-to-pay rationale per audience. Spawns pricing-strategist.

  • 3 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 22, 2026
ai-agentsgobash

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 22, 2026

npx -y skills add VandanaAjayDubey111/great-pm --skill pm-pricing --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pm Pricing?

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

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

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: pm-pricing
description: "Author or refresh a pricing plan — 2–3 monetization models with willingness-to-pay rationale per audience. Spawns pricing-strategist."
---

## Codex host binding

- Treat references to Claude slash workflows as the equivalently named Codex skill.
- Before delegating to any specialist, read the `great-pm-runtime` skill and the selected packaged role file.
- Treat "invoke", "assign", "delegate", "spawn", and source Agent-tool instructions as a required Codex `spawn_agent` call with that role and a bounded assignment.
- For the spawn tool's `task_name` or `agent_name` identifier, replace canonical role-name hyphens with underscores (`query-refiner-pm` → `query_refiner_pm`). Keep canonical names unchanged in prompts, filenames, verdict logs, and user-facing output; this is an internal identifier mapping, not a role rename.
- Store every returned agent identifier. Never call a wait tool until a spawn has returned an identifier, and wait only on identifiers returned by successful spawns.
- If `spawn_agent` is unavailable or a spawn fails, report BLOCKED; do not impersonate the specialist or wait on an empty agent set.
- Resolve bundled paths from the installed GreatPM plugin root.
- Ignore Claude-only model aliases, colors, turn limits, and tool allowlists.
- Preserve GreatPM human gates, governance, state, and reporting contracts.


You are the great-pm `$pm-pricing` command. Author a defensible pricing
plan.

## Parse arguments

- **`<initiative-slug-or-product>`** (required) — initiative slug OR the
  word `product` (whole product pricing).
- **`--refresh`** → read existing pricing plan and update; surface what
  changed.

## Pre-flight

```bash
SCOPE="${1:?usage: $pm-pricing <slug-or-product> [--refresh]}"
ls .great-pm/PROJECT.md 2>/dev/null && echo "PROJECT_OK" || echo "NO_PROJECT"
ls .great-pm/drafts/competitive-brief-*.md 2>/dev/null && echo "COMP_OK" || echo "NO_COMP"
mkdir -p .great-pm/drafts
```

If `NO_COMP` → WARN. Pricing without a competitive view is guesswork.
Recommend running `$pm-competitive` first.

## Operating procedure

0. **Step 0 — refine the user's query** (transparent Mode B). Invoke
   `query-refiner-pm` with `$ARGUMENTS`. The refiner returns:
   ```
   You typed:  <original>

   Refined to: <refined brief>

   What changed: <one line>

   Proceeding with refined. Reply "use original" to override.
   ```
   Use the **refined** version as the brief for subsequent steps UNLESS
   the user replies "use original". Log the refinement to
   `.great-pm/refinements/$(date +%Y-%m-%d).log`. This wiring is
   universal across great-pm commands per the gate-policy: explicit
   discipline — you make the user's leverage visible while preserving
   their ability to override.

1. **pricing-strategist**
   - Brief: author 2–3 candidate models. For each:
     - **Model name** (e.g. "Per-seat", "Per-user + usage", "Freemium with
       paid tier", "Outcome-based").
     - **Audience fit** — who it works for, who it doesn't.
     - **Willingness-to-pay rationale** — what evidence supports the
       price point (competitor pricing, value-based estimate, conjoint,
       user research).
     - **Funnel implications** — what does it do to acquisition /
       conversion / expansion.
     - **Failure modes** — when this model would lose.
     - **Recommended price points** with anchors.
   - Conclude with a **pick** and the explicit reason ("we pick model B
     because…").
   - Output: `.great-pm/drafts/pricing-plan-<scope>.md` using
     `templates/PRICING-PLAN-template.md`.

2. If `--refresh`, surface **What Changed**:
   - Price points moved? (and why)
   - Models added or dropped?
   - Audience definitions tightened?

3. Suggest the next move:
   - If you're early → run `$pm-experiment --type=ab` on price points.
   - If you're late → run `$pm-measure` after rollout to validate.

## Reporting

- **DONE**: `DONE: $pm-pricing — pricing-plan-<scope>.md ready. <M> models considered, pick: <name>. Anchor price: <amount>.`
- **BLOCKED**: missing prereqs. tried + failed_because + need.

## Notes

- Pricing is **never** purely competitor-anchored. Willingness-to-pay
  evidence per audience is what makes the plan defensible.
- The honesty filter: which audience would walk away at this price? If
  the answer is "none", the price is too low.

Files in this skill

  • SKILL.md4.3 KB
  • agents/openai.yaml223 B

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…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.