asc-release-flow

1# App Store release orchestration
2 
3Use this skill to carry a release from an approved plan to App Store review.
4 
5## Ownership boundary
6 
7This skill owns:
8 
9- staging metadata and attaching a build;
10- publishing an IPA or building locally;
11- submitting a prepared version;
12- assembling a multi-item review submission.
13 
14Use [the preparation section](references/multi-item-submissions.md#prepare-every-item) for Game Center item preparation or attachment blockers. Use that reference's assembly and submission sections only after the app version is staged and the multi-item lane is selected. Switch to `asc-submission-health` for other validation blockers, a stuck submission, cancellation, or retry decisions.
15 
16Switch skills within the current task, preserving resolved targets, authorization, and verified progress. A failing gate blocks dependent mutations, not diagnosis or independent authorized work. Continue authorized repairs and resume this flow; request new authority only when repairs exceed the agreed scope.
17 
18## Preconditions
19 
20- Resolve `APP_ID`, the version string, `VERSION_ID` when needed, and `BUILD_ID` when a build already exists.
21- Configure auth with `asc auth login` or `ASC_*` environment variables.
22- Confirm the intended platform. Use `IOS` unless the app targets another platform.
23- Keep canonical metadata in `./metadata` when the workflow applies metadata.
24- Require a dry run before a mutating high-level command, then require `--confirm` for submission.
25…