release-spec_skill

Overview

This skill generates a complete App Store release specification for iOS/macOS apps, producing a ready-to-use RELEASE_SPEC.md to guide launch. It consolidates product, architecture, implementation, testing, and ASO inputs into a step-by-step submission guide. The output covers metadata, assets, privacy compliance, QA checkpoints, and a marketing rollout plan.

How this skill works

The skill reads prior artifacts (product plan with ASO, architecture, implementation guide, and test spec) and extracts actionable items: app name, screenshots, build config, privacy needs, and QA gates. It assembles a structured release document with quick-check checklists, App Store Connect metadata, asset specs, privacy manifest guidance, and a suggested beta-to-launch timeline. The result is an editable RELEASE_SPEC.md optimized for execution by release managers and engineering teams.

When to use it

• Preparing an initial App Store submission or major release
• Consolidating ASO, technical, and QA artifacts into a launch plan
• Before TestFlight beta to ensure compliance and assets are ready
• When you need a single source of truth for App Store Connect metadata
• Coordinating product, engineering, QA, and marketing for launch

Best practices

• Complete and approve ASO, ARCHITECTURE, IMPLEMENTATION_GUIDE, and TEST_SPEC before generating the spec
• Use the quick-start checklist to run a two-week pre-launch cadence and a one-week beta cadence
• Fill the privacy manifest from a code review of collected data and required APIs, then validate against Apple docs
• Produce localized screenshots and short preview videos for top target markets
• Archive a validated build in Xcode and run one final validation on the target device families before submission

Example use cases

• Create a release document for v1.0 that includes ASO-ready metadata and screenshots
• Prepare an enterprise-facing app with explicit privacy manifest entries and Required Reason APIs
• Run a coordinated TestFlight beta with a defined feedback loop and crash-free targets
• Hand off a reproducible submission checklist to a project manager or external release engineer
• Generate marketing-focused store copy and 'What’s New' notes for a feature release