asc-launch-workflow

ASC Launch Workflow

Use this skill as the coordinator for a full ASC launch/update pass:

1. localized metadata copy;
2. localized keyword fields;
3. localized ASC screenshot assets;
4. ASC API task JSON and, after explicit confirmation, optional ASC execution.

Each phase runs in a dedicated subagent to keep the coordinator's context lean. The coordinator builds the shared product brief, dispatches subagents with precise inputs, collects their file outputs and summaries, assembles the review bundle, and handles the ASC mutation confirmation directly with the user. The coordinator never performs the work of a child skill inline.

If any child skill is missing or cannot be loaded, stop before the affected phase and report the missing dependency.

Security And Live-Update Rules

Never ask the user to paste App Store Connect secrets, .p8 contents, JWTs, Authorization headers, or ~/.asc_secrets.

Never read or print ~/.asc_secrets, .p8 private keys, tokens, Authorization headers, or full request headers.

Treat App Store Connect writes as a two-step process:

1. Generate final ASC task JSON from reviewed artifacts.
2. Stop and ask the user to confirm the exact JSON before any POST, PATCH, DELETE, upload, submit, or state change.

Read-only ASC discovery may run when the task is clear and local access is available. Mutating ASC operations must never run in the same step that first creates the final JSON unless the user already explicitly approved that exact JSON.

Start Gate

Before starting any project inspection, subagent dispatch, hard dependency check, file generation, screenshot capture, App Store Connect discovery, or API task drafting, verify that the required inputs below are present.

Everything not listed here is either inferred from the project, defaulted automatically, or discovered at runtime. Do not ask the user for anything beyond this list.

Required inputs — the only things to block on:

Input	Required when	Why it cannot be inferred
Phases to run	Always	User decision; cannot be guessed
Target locales	Always	User decision; cannot be guessed
Pixelmator Pro PXD template path	screenshots phase	Stored in user's personal directory; not discoverable
Intended ASC operation (draft-only / generate-task-json / execute-after-confirmation)	asc-json or asc-execute phase	Determines whether live App Store mutations happen; must be explicit