INPUT 01
Input 01
The relevant project and requirements
Stripe best practices
A source-backed stripe best practices workflow for software & product teams. Review its inputs, setup and geographic limits before your first draft.
Work typeProduct
SetupLocal tooling / APIs
ContextWorldwide
01 / What you bring
REQUIRED INPUTSGather the material before running the prompt. Follow the publisher’s full checklist for the specific task.
INPUT 02
Input 02
Runtime, access constraints, and acceptance criteria
INPUT 03
Input 03
The complete skill folder and any required supporting files
Publisher excerpt: “Guides Stripe integration decisions across API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties),…” Source ↗
02 / What you get
EXPECTED OUTPUTAn implementation plan, review, or tested change
DRAFT HANDOVERFOR HUMAN REVIEW
An implementation plan, review, or tested change
Evidence and supplied inputs
Assumptions and missing information
Draft output and review questions
This describes the intended handover. It is not a measured or executed result.
03 / Set it up
Codex: use the publisher’s Codex or Agent Skills setup path. Keep supporting scripts and references, inspect required permissions and validate a permitted sample.
STEP 01
Review the complete source
Review the linked source and the publisher’s current README before installing.
STEP 02
Keep the full workflow
Download or install the complete plugin/skill folder, preserving references and scripts. Do not paste a terminal command intended for another app.
STEP 03
Configure your workspace
Use the setup path for the platform you actually have; configure only the required apps and permissions.
STEP 04
Try a reviewable first draft
Start with a permitted sample and the starter prompt. Check the first result against your own normal review process.
Compatibility, tools & dependencies
Published in OpenAI’s Codex plugin examples. Requires the complete plugin and its documented app/MCP/runtime access; this is not automatically a ChatGPT web installation.
Geography-neutral workflow. Set Australian spelling, AUD, dates and business context explicitly; local compliance is not supplied by this label.
Named tools: Stripe. Actual access depends on your setup.
- The source references app or connector access; install/configure the complete plugin and confirm permissions.
- The source references local code or command-line tooling; check its runtime and package requirements before use.
Pinned source snapshot; review publisher release and installation notes.
Public instructions do not imply free access to AI products, apps or APIs.
04 / Your starter prompt
REPLACE THE BRACKETSUse stripe-best-practices for [business task]. Our business is in [country and state/territory], our currency is [currency], and the intended reader is [audience]. Use only the attached authorised inputs and approved policies. First identify missing information and unavailable tools. Prepare a draft for human review; cite the supplied evidence, separate assumptions, and do not send, publish, lodge, purchase or change records.
Fieldwork’s starter prompt. Keep the complete publisher workflow and replace the brackets before use.
05 / Before you rely on it
Review the draft before using it
Use a test environment, review permissions and dependencies, and validate changes against the actual application. Hosting and third-party tools may add cost.
This is a source-inspected starting point. Fieldwork has not run-tested this skill or measured time savings.