product-release-spec

Generate RELEASE_SPEC.md from product plans, architecture, test specs, and ASO metadata.

4|1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/AutisticAF/claude-code-apple-dev-plugin --skill product-release-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-release-spec
Source: https://github.com/AutisticAF/claude-code-apple-dev-plugin/tree/main/skills/product-release-spec
Command: npx skills add https://github.com/AutisticAF/claude-code-apple-dev-plugin --skill product-release-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of App Store release documentation by consolidating product plans, architecture details, testing specs, and ASO metadata.

Core Features & Use Cases

  • Generates a complete RELEASE_SPEC.md that guides release planning, privacy manifest, asset preparation, and submission steps.
  • Cross-references inputs from product plans (product-plan-*.md), architecture docs (docs/ARCHITECTURE.md), implementation guide (docs/IMPLEMENTATION_GUIDE.md), and test specs (docs/TEST_SPEC.md) to ensure alignment.
  • Supports iterative updates as plans evolve and keeps release artifacts synchronized with App Store metadata.

Quick Start

Provide the app plan, architecture guide, and test specs, then invoke this skill to generate the RELEASE_SPEC.md.

Frequently Asked Questions about product-release-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate App Store release documentation from existing project specs?

Generate App Store release documentation by providing your product plans, architecture details, implementation guide, and test specs to consolidate them into a single RELEASE_SPEC.md file. This ensures alignment between your technical inputs and App Store metadata.

What is included in a complete App Store release specification for iOS and macOS apps?

A complete App Store release specification includes release planning guidance, privacy manifest details, asset preparation steps, and submission workflows. It cross-references architecture docs and test specs to align technical inputs with ASO metadata.

Can I use product plans and test specs to create App Store ASO metadata?

Yes, you can use product plans and test specs to create App Store ASO metadata. The workflow cross-references product-plan files and docs/TEST_SPEC.md inputs to ensure your submission metadata aligns with your actual app architecture and functionality.

How do I keep release artifacts synchronized with App Store metadata as plans evolve?

Keep release artifacts synchronized with App Store metadata by applying iterative updates to your RELEASE_SPEC.md as plans evolve. The workflow supports re-consolidating product plans and architecture docs to maintain alignment throughout the pre-submission process.

What inputs are required to automate iOS app pre-submission workflows and privacy compliance?

Required inputs for iOS app pre-submission workflows include product-plan files, docs/ARCHITECTURE.md, docs/IMPLEMENTATION_GUIDE.md, and docs/TEST_SPEC.md. Providing these allows the generation of privacy compliance details and submission steps.