Stripe implementation planner

Plans which Stripe products a business needs and how they fit, by gathering requirements and running stripe tools plan before any code. Use when starting a Stripe integration or adding subscriptions, in-person payments or a marketplace.

CodingPack: Stripe skills90 linesstripe-implementation-planner
Author
Source
stripe/ai/skills/stripe-implementation-planner @ 119bc4a
License
MIT · Copyright (c) 2024–2025 Stripe

About this skill

What it does

Stripe's implementation planner chooses the Stripe products and integration architecture for a business before any code is written. The recommendation comes from the Stripe CLI command stripe tools plan, not the agent's memory; the skill covers how to feed it and how to treat its output.

First the agent collects what changes the answer: what is sold and to whom, how money is collected, whether this is a direct business, a platform or a marketplace, the sales channels, countries and any existing Stripe setup. It asks only for what is missing and keeps a multi-product request whole. Then it checks the CLI, installs it with npm install -g @stripe/cli if needed, creates a claimable test sandbox with stripe sandbox create when there is no account and the CLI requires a login, reads stripe tools plan --help and runs the planner with the full context. It refines the plan as the command directs, checks it against your requirements and calls it final only once the command confirms acceptance. You get a summary of setup, trade-offs and open decisions; code waits until then.

Eight products have no planner guidance: Atlas, Treasury, Radar, Issuing, Global Payouts, Capital, Sigma and Data Pipeline. For those the agent falls back on Stripe's docs and says so. Without the CLI it can use the stripe_implementation_planner tool of an authenticated Stripe MCP session.

The frontmatter pre-approves four commands: which stripe, stripe --version, stripe tools plan and stripe sandbox create.

When to use it, and when not

Use it for a first Stripe integration or a large expansion such as adding subscriptions, in-person payments or third-party sellers.

It rules out API upgrades, debugging, webhook troubleshooting, small code changes and PR review, and does not read existing integration code. It needs the Stripe CLI or MCP server.

How to run it

The install command below puts SKILL.md and the licence in place.

  • Claude Code: /stripe-implementation-planner, or ask for the skill by name.
  • Codex: $stripe-implementation-planner.
  • Cursor: type / in the Agent chat and pick stripe-implementation-planner.

Example: /stripe-implementation-planner We run a tutoring marketplace in the EU and UK: students pay per lesson or monthly, tutors are paid weekly. Plan the Stripe setup.

How it differs from similar skills

Stripe integration best practices from the same pack holds the rules for the code once products are chosen; the planner sends upgrades and code changes there. Writing implementation plans and Planning and task breakdown split an agreed spec into coding tasks. This skill settles which Stripe products belong in that spec.

Install

Run one command — it saves SKILL.md and the files it uses into your agent's skills folder. Claude Code and Codex pick up a new skill without a restart; if it does not show up, restart the agent.

Claude Code — macOS, Linux
curl -fsSL --create-dirs -o ~/.claude/skills/stripe-implementation-planner/SKILL.md https://anymodel.org/en/skills/stripe/stripe-implementation-planner/SKILL.md -o ~/.claude/skills/stripe-implementation-planner/LICENSE https://anymodel.org/en/skills/stripe/stripe-implementation-planner/LICENSE
Codex, Cursor — macOS, Linux
curl -fsSL --create-dirs -o ~/.agents/skills/stripe-implementation-planner/SKILL.md https://anymodel.org/en/skills/stripe/stripe-implementation-planner/SKILL.md -o ~/.agents/skills/stripe-implementation-planner/LICENSE https://anymodel.org/en/skills/stripe/stripe-implementation-planner/LICENSE
Claude Code — Windows PowerShell
foreach ($f in 'SKILL.md','LICENSE') { $p = Join-Path "$HOME\.claude\skills\stripe-implementation-planner" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/stripe/stripe-implementation-planner/$f" -UseBasicParsing -OutFile $p }
Codex, Cursor — Windows PowerShell
foreach ($f in 'SKILL.md','LICENSE') { $p = Join-Path "$HOME\.agents\skills\stripe-implementation-planner" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/stripe/stripe-implementation-planner/$f" -UseBasicParsing -OutFile $p }

Any other agent: save the file into its skills folder, or give it the link to the file: https://anymodel.org/en/skills/stripe/stripe-implementation-planner/SKILL.md

SKILL.md

Raw

Stripe Implementation Planner

Use the stripe tools plan CLI command to obtain personalized product and implementation guidance based on the user’s business model, requirements, and constraints. Use it before writing integration code when possible.

When to use this skill

Use this skill for initial Stripe product selection and integration architecture, or when an existing integration is materially expanded, such as adding subscriptions, in-person payments, or third-party sellers.

For an existing Stripe setup, use this skill to plan new products or use cases. This skill does not inspect existing integration code or produce a code migration plan.

Don’t start a planning workflow for API upgrades, availability questions, debugging, narrow implementation changes, product explanations, or PR review alone. Address those requests directly. For API upgrades, troubleshooting, and code changes, use the stripe-best-practices skill if it’s available, or current Stripe documentation. For availability questions, consult current product-availability documentation.

An existing integration or a request involving Stripe code isn’t, by itself, a reason to run the planner. Respect explicit requests to skip planning.

Coverage limits

No product-specific planner guidance for:

  • Atlas (company incorporation)
  • Treasury (embedded accounts and money movement)
  • Radar (fraud and risk rules)
  • Issuing (virtual and physical cards)
  • Global Payouts (worldwide third-party payouts)
  • Capital (loans and cash advances)
  • Sigma (SQL reporting)
  • Data Pipeline (warehouse sync)

For requests involving only these products, skip CLI installation, authentication, drafts, decision trees, and accept calls. Use current Stripe documentation or an applicable skill. Coverage or account permissions must not block documentation guidance.

For mixed requests, plan the supported requirements, preserve the unsupported requirements, and supplement them with current documentation or applicable skills. State the coverage limits. Don’t present a partial plan as the complete solution.

Workflow

  1. Gather enough context to describe the user’s needs accurately. Use context already available from the conversation and project. Ask only for missing information that could materially change the recommendation:

    • What’s their business model? What are they selling? Who are their customers?
    • How do they collect payments? For example, one-time, recurring, invoiced, or usage-based
    • Whether they’re a direct business, platform, or marketplace
    • Whether they accept payments online, in a mobile app, or in person
    • Relevant countries, currencies, implementation constraints, and existing Stripe setup if it exists
  2. Preserve the user’s full requirements. Don’t collapse a multi-product or mixed-channel request into a narrower use case.

  3. Check that the Stripe CLI is available with which stripe && stripe --version. If it’s missing, install it with npm install -g @stripe/cli. If installation fails, read the Stripe CLI installation guide and follow the instructions appropriate for the user’s environment. Verify the installation with stripe --version.

  4. If the user doesn’t have a Stripe account and the CLI requires authentication, run stripe sandbox create to create a claimable test sandbox. Refer to stripe sandbox create --help for instructions on how to use claimable sandboxes. Then retry only as directed by the CLI. Explain that a sandbox is a Stripe test environment.

  5. Run stripe tools plan --help for the latest usage instructions.

  6. Run the planner with the user’s complete business and implementation context:

stripe tools plan --message "<complete business and implementation context>"
  1. Follow the current help and command responses to generate and refine the plan.

  2. Before finalizing, evaluate the plan against the user’s requirements. Adapt the recommendation when the output doesn’t reflect the constraints, and resolve any material gaps or decisions with the user as needed.

  3. Finalize the plan by following the current command instructions. Only describe the plan as finalized after the command confirms successful acceptance. Then summarize the recommended setup, material tradeoffs, and unresolved decisions in terms of the user’s requirements.

Critical rules

  • Prefer the CLI path. If the CLI is unavailable and the user’s authenticated Stripe MCP session exposes stripe_implementation_planner, use the MCP tool. Don’t assume the MCP tool is available or authenticated.
  • Don’t run the planner with a vague prompt when the missing context could change the recommendation. Ask focused questions first.
  • Don’t treat a product omitted from the output as evidence that it’s irrelevant.
  • When the request extends beyond the planner’s supported scope, supplement the plan with current Stripe documentation and clearly identify which guidance came from outside the planner.
  • Treat the plan as a starting point, not an unquestionable answer. Check it against the user’s stated requirements, geographic needs, compatibility constraints, and existing implementation.
  • Don’t dump raw planner JSON on the user unless they explicitly ask for it. Summarize the recommendation, tradeoffs, and unresolved decisions.
  • For supported planning requests, don’t write integration code until the planning step is complete unless the user explicitly asks to skip planning.

Connect through AnyModel API

This skill runs on whatever model your agent uses. Point Claude Code, Codex or Cursor at AnyModel to run it on Claude, GPT, Gemini and more with one key — pay per token, no subscription.

More from the pack Stripe skills