What problem does it solve? Coordinating an App Store release involves staging metadata, attaching builds, validating readiness, and submitting for review, and mistakes like duplicate submissions or unvalidated uploads can block a release. This Skill provides a guarded, lane-based workflow for driving a release from an approved plan to App Store review using the asc CLI. ## Core Features & Use Cases - Release lane selection: Choose between staging an existing build, submitting a prepared version, publishing an IPA or local build, or assembling a multi-item review submission. - Readiness gating: Run asc validation with optional strict mode, and route Game Center, IAP, or other blockers to the correct preparation or diagnosis flow before submitting. - Multi-item submissions: Assemble a single review submission containing the app version plus IAP, subscription, subscription-group, or Game Center version items, with dry-run and confirmation safeguards. - Use Case: You have build 42 processed and metadata ready in ./metadata for version 1.2.3. Use this Skill to dry-run the staging plan, confirm the mutation, validate the version, and submit it for App Store review without creating duplicate submissions. ## Quick Start Use the asc-release-flow skill to stage build BUILD_ID for app APP_ID version 1.2.3 with metadata from ./metadata, then submit it for App Store review after a dry run.