Install & init

Install

npm install -g prodverdict
# per-run (from your own repo)
npx prodverdict@0.9.1 check access --config prodverdict.yml --fixtures --fixtures-dir path/to/scenario

Inside a prodverdict-sdk clone, npx prodverdict@… resolves the local workspace — use:

npx --package=prodverdict@0.9.1 prodverdict check access --fixtures ...

For a zero-credential first run, use the quickstart fixture demo (git clone the public SDK first).

Packages: prodverdict (CLI), @prodverdict/engine, @prodverdict/mcp.

Scaffold prodverdict.yml

Pick the stack closest to yours:

Template	Stack
nextjs-stripe	Next.js + Stripe + Postgres users
supabase-stripe	Supabase + Stripe + profiles
neon-stripe	Neon Postgres + Stripe
clerk-stripe	Clerk auth + Stripe billing
rails-stripe	Rails + Stripe
paddle-stripe	Paddle + Postgres
supabase-paddle	Supabase + Paddle + profiles

npx prodverdict init --list-stacks
npx prodverdict init --stack nextjs-stripe

Access + config (default)

init writes access and config contracts. Use --access-only to skip config.

Cursor / agent setup

npx prodverdict init --stack nextjs-stripe --mcp --cursor-rule

Creates:

• prodverdict.yml
• .cursor/mcp.json (local MCP)
• .cursor/rules/prodverdict-agent.mdc

Remote MCP (config + migration via GitHub)

npx prodverdict init --remote-mcp --project-id your-project-uuid

Requires a prodverdict.com project and API key. Billing secrets stay on your machine — remote MCP never reads Stripe or your database.

Validate YAML only

npx prodverdict validate --config prodverdict.yml

Map Stripe prices to plans

In prodverdict.yml, map price IDs to plan slugs:

plans:
  price_1ABCxxxPro: pro
  price_1ABCxxxStarter: starter

Without plans, price-to-plan drift rules are skipped.