Catalog
stripe/stripe-implementation-planner

stripe

stripe-implementation-planner

Plans Stripe product selection and integration architecture for an initial Stripe setup or a material expansion of an existing setup. Use when the user needs personalized recommendations based on their business model, payment models, sales channels, geography, or platform requirements, including requests to plan and build an integration. Don't use for API-version upgrades, product-availability questions, existing-integration debugging, webhook troubleshooting, narrow code changes, product explanations, PR review alone, unrelated implementation planning, or when the user explicitly asks to skip planning.

v1.0LATEST
NewUpdated Nov 15, 2026

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.
Files1
1 files · 1.1 KB

Select a file to preview

Overall Score

87/100

Grade

A

Excellent

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

90

Quality

88

Clarity

85

Completeness

83

Summary

Guides AI agents through Stripe product selection and integration planning using the Stripe CLI's `stripe tools plan` command. The skill gathers business context from users, validates the CLI environment, and runs a personalized planner that recommends Stripe products and architecture based on payment models, sales channels, geography, and platform constraints. It includes clear guardrails on scope, coverage limits for unsupported products, and instructions to treat the plan as a starting point, not final.

Detected Capabilities

shell execution (stripe CLI commands)environment validation (which, --version)interactive workflowdocumentation reference

Trigger Keywords

Phrases that agents use to match this skill to user intent.

plan stripe integrationstripe product selectionpayment architecture designstripe multi-channel setupsubscription or marketplace expansionpayment infrastructure planning

Risk Signals

INFO

Bash command execution for Stripe CLI tools (which, stripe --version, stripe tools plan, stripe sandbox create)

Workflow section, steps 3-6
INFO

Reference to external documentation (docs.stripe.com/cli/install)

Step 3
INFO

CLI flag usage (--message, --help)

Steps 5-6

Referenced Domains

External domains referenced in skill content, detected by static analysis.

docs.stripe.com

Use Cases

  • Plan initial Stripe product selection for new businesses
  • Design integration architecture for multi-channel payment setup (online, mobile, in-person)
  • Recommend Stripe products for subscription or marketplace expansion
  • Evaluate payment infrastructure for specific geographies and currencies
  • Integrate Stripe into existing platforms with new use cases or channels
  • Document architectural tradeoffs and product recommendations for payment systems

Quality Notes

  • Clear scope boundaries: skill explicitly states when NOT to use it (API upgrades, debugging, narrow changes, product explanations, PR review alone)
  • Well-documented coverage limits: lists 8 unsupported Stripe products and guidance for mixed requests
  • Practical workflow with validation checkpoints: environment checks, account setup, plan refinement, final evaluation against user requirements
  • Emphasis on gathering sufficient context before running planner prevents vague recommendations
  • Explicit instruction to treat plan as starting point, not final answer, and to summarize recommendations in user-friendly terms rather than dumping raw JSON
  • Critical rules section reinforces quality standards (prefer CLI, don't assume MCP, supplement outside scope, check output against requirements)
  • Allowed tools clearly restrict agent to read-only CLI commands (which, version check, planner invocation, sandbox creation) — no destructive operations or file writes
  • Clear guidance on preserving multi-product requirements and supplementing unsupported features with documentation
  • Emphasis on user autonomy: respect explicit requests to skip planning, don't assume planner output is complete
Model: claude-haiku-4-5-20251001Analyzed: Nov 15, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Use stripe/stripe-implementation-planner in your dev environment

Command Palette

Search for a command to run...