appstore-release-plannerlisted

# App Store Release Planner Use this as the decision front door for App Store release readiness. Do not duplicate the execution workflow here; after the decision, read the focused skill that owns the next action. ## Routing - Use `appstore-release-director` when the user wants an end-to-end release from local repo through upload, TestFlight, review, and evidence. - Use `appstore-review-readiness` for concrete validation, staging/submission, status monitoring, cancellation, and blocker repair commands. - Use `appstore-archive-uploader` when the next unresolved step is version/build numbering, archive, export, upload, or processed build selection. - Use `appstore-metadata-sync`, `appstore-screenshot-validator`, `appstore-signing-setup`, `appstore-pricing-planner`, `appstore-subscription-localizer`, or `appstore-testflight-coordinator` when the blocker is clearly in that narrower surface. ## Answer Order 1. Ready now or not. 2. Blocking issues. 3. Public API fixes vs experimental web-session/manual fixes. 4. Next exact command. Resolve `APP_ID`, version, `VERSION_ID`, and `BUILD_ID`; ensure `asc auth login` or `ASC_*`; use canonical `./metadata` when staging. ## Decision Path 1. Establish release target: app, platform, version, build, submission state, and whether this is a first submission. 2. Check whether the next missing evidence belongs to metadata, screenshots, signing, pricing/availability, subscriptions/IAP, App Privacy, review details, Game Center, build process