INPUT 01
Input 01
The relevant project and requirements
A source-backed stripe docs workflow for software & product teams. Review its inputs, setup and geographic limits before your first draft.
Gather the material before running the prompt. Follow the publisher’s full checklist for the specific task.
INPUT 01
The relevant project and requirements
INPUT 02
Runtime, access constraints, and acceptance criteria
INPUT 03
The complete skill folder and any required supporting files
Publisher excerpt: “Use when the user or agent needs to read, search, or look up Stripe documentation or API reference.…” Source ↗
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.
Codex: use the publisher’s Codex or Agent Skills setup path. Keep supporting scripts and references, inspect required permissions and validate a permitted sample.
ChatGPT: manual instruction adaptation. Read the source, supply the required context and files, and configure available tools yourself. This is not a native ChatGPT plugin installation.
STEP 01
Review the linked source and the publisher’s current README before installing.
STEP 02
Download or install the complete plugin/skill folder, preserving references and scripts. Do not paste a terminal command intended for another app.
STEP 03
Use the setup path for the platform you actually have; configure only the required apps and permissions.
STEP 04
Start with a permitted sample and the starter prompt. Check the first result against your own normal review process.
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. ChatGPT is a manual instruction/prompt adaptation only; no native plugin installation or publisher-tested ChatGPT execution is claimed.
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.
Pinned source snapshot; review publisher release and installation notes.
Public instructions do not imply free access to AI products, apps or APIs.
Use stripe-docs 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.
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.