What is the Stripe Implementation Planner skill?
Stripe Implementation Planner is a finance skill by Stripe for Claude Code, Cursor, Codex and other AI coding agents. 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.
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 it
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.
What the SKILL.md covers
- When to use this skill
- Coverage limits
- Workflow
- Critical rules
- Author
- Stripe
- Pack
- stripe/ai (11 skills)
- Category
- Finance, #106 of 283
- Alyn Score
- 67 / 99
- Files
- 1
- License
- MIT
- Last updated
- 27 h ago
- Works with
- Claude Code, Claude, Cursor, Codex, Gemini CLI, Copilot
Stripe Implementation Planner compared to similar skills
| Skill | Alyn Score | GitHub stars | Updated |
|---|---|---|---|
| Stripe Implementation Planner · Stripe | 67 | 2.1k | 27 h ago |
| Make Plan · thedotmack | 68 | 118k | 16 h ago |
| Agent Payment X402 · affaan-m | 90 | 304k | 22 h ago |
| SEO Plan · AgriciDaniel | 85 | 30k | 21 h ago |
Install Stripe Implementation Planner
Pick your agent. Every command is ready to paste.
npx alyn-cli add stripe-implementation-plannerDetects your agents (Claude Code, Cursor, Codex and 70+ more) and installs to the right folder. Add -g to install globally.
npx skills add stripe/ai --skill stripe-implementation-plannerOr use the open skills CLI directly.
01
Install it
Run the command above, or upload the folder in Claude.
02
Ask naturally
Describe the task. Your agent loads stripe-implementation-planner when the request matches its description.
03
Name it if needed
If it does not trigger, say “use the stripe-implementation-planner skill”. In Codex, type $stripe-implementation-planner.
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
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
Preserve the user’s full requirements. Don’t collapse a multi-product or mixed-channel request into a narrower use case.
Check that the Stripe CLI is available with
which stripe && stripe --version. If it’s missing, install it withnpm 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 withstripe --version.If the user doesn’t have a Stripe account and the CLI requires authentication, run
stripe sandbox createto create a claimable test sandbox. Refer tostripe sandbox create --helpfor instructions on how to use claimable sandboxes. Then retry only as directed by the CLI. Explain that a sandbox is a Stripe test environment.Run
stripe tools plan --helpfor the latest usage instructions.Run the planner with the user’s complete business and implementation context:
stripe tools plan --message "<complete business and implementation context>"
Follow the current help and command responses to generate and refine the plan.
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.
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.
Tips for Stripe Implementation Planner
- • Start a fresh session after installing so your agent picks up the new skill.
- • It is part of a pack with 11 skills. Install only the ones you need with --skill to keep triggers precise.
- • If two skills overlap, mention the one you want by name.
Questions about Stripe Implementation Planner
What does the Stripe Implementation Planner skill do?
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.
How do I install Stripe Implementation Planner?
Run "npx alyn-cli add stripe-implementation-planner" in your project. The Alyn CLI installs it for Claude Code, Cursor, Codex and 70+ other agents. In Claude on the web, upload the skill folder as a ZIP under Customize > Skills.
Does Stripe Implementation Planner work in Cursor and Codex?
Yes. Stripe Implementation Planner uses the open SKILL.md format, so it works in Claude Code, Claude, Cursor, OpenAI Codex, Gemini CLI, GitHub Copilot and other agents that support agent skills.
When should I use the Stripe Implementation Planner skill?
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.
What is inside the Stripe Implementation Planner skill?
The SKILL.md covers When to use this skill, Coverage limits, Workflow, Critical rules.
What is a good alternative to Stripe Implementation Planner?
Make Plan by thedotmack is the highest-ranked similar skill from another creator, with an Alyn Score of 68 compared to 67 for Stripe Implementation Planner.
Is Stripe Implementation Planner free?
Stripe Implementation Planner is open source on GitHub under the MIT license. It is free to install; check the license before commercial use.
Who made Stripe Implementation Planner?
Stripe Implementation Planner is published by Stripe in the stripe/ai repository, together with 10 other skills.



