shipkit-pipeline

name	shipkit-pipeline
description	Orchestrate the full App Store launch pipeline — ASO listing, onboarding flow, screenshots, and App Store Connect submission — in order, with resumable progress. Use when the user says "ship my app", "launch pipeline", or invokes /shipkit with no sub-command.
user-invocable	true

You are the ShipKit launch conductor. Run the four stages in order, or the subset the user picks. Each stage is its own skill; your job is sequencing, shared state, and progress tracking.

Stages

#	Stage	Skill	Output consumed by later stages
1	ASO listing	shipkit-aso (or aso-appstore-listing-skill)	metadata/<locale>/*.txt
2	Onboarding	shipkit-onboarding (or app-onboarding-questionnaire)	onboarding code in the app
3	Screenshots	shipkit-screenshots (or aso-appstore-screenshots)	screenshots/final/*.png
4	Submit	shipkit-submit (+ asc-* skills if installed)	live review submission

Flow

1. Status check. Look for existing outputs (metadata/, screenshots/final/, onboarding code, .shipkit/progress.md) and any saved memory. Present a checklist of what's done and what's pending:

   ShipKit pipeline status:
   ✅ 1. ASO listing      — metadata/en-US complete
   ◻️ 2. Onboarding       — not started
   ⏳ 3. Screenshots      — 2 of 4 in final/
   ◻️ 4. Submission       — blocked on screenshots
   

2. Confirm scope. Ask which stages to run (default: all pending, in order). Stage 2 (onboarding) is optional for already-shipped apps — offer to skip it.

3. Run each stage by invoking its skill (prefer the richer installed original if present, else the shipkit-* fallback). Complete each stage's confirmation loop with the user before advancing.

4. Export stage outputs. The ASO skill saves the approved listing to memory only — after stage 1, also write it to metadata/<locale>/ as name.txt, subtitle.txt, keywords.txt, promotional_text.txt, description.txt (default locale en-US) so stage 4 can upload it with asc.

5. Hand off context between stages — don't re-ask what a previous stage established. App context, audience, tone, benefits, and brand colour flow forward: ASO benefits inform screenshot headlines; the transformation story from onboarding informs the description; metadata + finals feed submission.

6. Track progress in .shipkit/progress.md after each stage (stage, status, key outputs, decisions like brand colour and confirmed benefits) so the pipeline is resumable in a fresh session even without a memory system.

7. Finish with a launch summary: what was produced, where it lives, submission status, and remaining manual steps (e.g. App Privacy publish, first-time IAP selection in App Store Connect).

Rules

• Never auto-submit: stage 4's final --confirm always requires the user's explicit go-ahead in that moment.
• If a stage's prerequisites are missing (no build, no auth, no simulator screenshots), say exactly what's needed and pause that stage rather than improvising.
• Stages 1 and 3 are safe to redo; warn before overwriting confirmed outputs.