What problem does it solve? Coordinating an App Store release involves many error-prone steps—staging metadata, attaching builds, validating readiness, uploading IPAs, and submitting for review. This Skill turns that into a guided, gated workflow using the asc CLI, with dry-run previews and confirmation requirements before any mutation. ## Core Features & Use Cases - Release lane selection: Choose between staging an existing build, submitting a prepared version, publishing from an IPA or local Xcode project, or assembling multi-item review submissions. - Readiness gating: Run asc validate checks, enforce digital-goods gates for IAPs and subscriptions, and route blockers to asc-submission-health instead of burying remediation. - Multi-item submissions: Assemble review submissions containing the app version plus IAP, subscription, subscription-group, and Game Center version items via the references guide. - Use Case: You have build 42 processed and metadata in ./metadata. Run a dry-run of asc release stage, confirm the plan, then submit with asc review submit --confirm and hand off monitoring to asc-submission-health. ## Quick Start Ask the agent to stage version 1.2.3 of your app with the existing build and metadata directory, run a dry run first, then submit it for App Store review after confirmation.
