Command workflow: /ship-it
Use this as a host-agnostic workflow. Adapt command names and capabilities to the active coding-agent host.
Workflow contract
yamldescription: "Full ship pipeline for an iOS RN app: pre-submission audit, screenshots, metadata, EAS build, EAS submit, review notes" argument-hint: "<context>"
/ship-it
Orchestrate the complete ship pipeline. Run this when ready to release.
External action gate
This workflow can complete local validation and prepare store assets. Building with EAS, uploading a binary, adding testers, submitting for review, and changing phased-release availability are external actions. Obtain explicit confirmation for each action after identifying the exact developer account, app, build, store target, and release status.
Workflow
- Run
pre-submission-auditskill on the current Expo project. Halt on any CRITICAL. - Run
accessibility-auditskill — surface failures. - Run
prep-app-store-listingskill — refresh metadata for en-US (and FIGS+J if localized). - Run
design-screenshotsskill — verify 10-shot framework + captions ready. - Run
write-review-notesskill — generate App Review notes + demo account. - Use
eas-submit-testflightto prepare, but not execute, the build and upload commands. - Request a specific confirmation before starting a build; after it completes, request a separate confirmation before upload to TestFlight.
- Wait for TestFlight processing and present the result. Ask again before any App Store submission.
- After a confirmed App Store submission, use
phased-releaseonly to prepare the staged-release plan until each availability change is approved.
End with a release summary, prepared commands, and outstanding approvals. Do not promise an App Review timeline.


