skills.rest
venomez-viper
venomez-viperCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

release-spec

Aggregate product, architecture, and testing inputs into a RELEASE_SPEC.md for App Store submission.

1|Updated Mar 26, 2026
Search Tags:#documentation#qa#release#release-management#app-store
One-click install
npx skills add https://github.com/venomez-viper/PathWise --skill release-spec-venomez-viper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-spec
Source: https://github.com/venomez-viper/PathWise/tree/main/.claude/skills/product/release-spec
Command: npx skills add https://github.com/venomez-viper/PathWise --skill release-spec-venomez-viper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates comprehensive release documentation and deployment guidance for iOS/macOS apps, consolidating PRDs, architecture, testing plans, and ASO assets into a single RELEASE_SPEC.md to streamline submission.

Core Features & Use Cases

  • Inputs integrated: Pulls from product-plan (ASO), ARCHITECTURE.md, IMPLEMENTATION_GUIDE.md, and TEST_SPEC.md to assemble a complete release spec.
  • Output artifact: Produces RELEASE_SPEC.md with structured sections for pre-submission, build, QA, metadata, and legal/compliance reminders.
  • Use Case: A Release Manager uses it to generate a launch-ready specification before App Store submission, ensuring alignment across teams.

Quick Start

Generate a complete App Store release specification by aggregating product, architecture, and test specs and producing a RELEASE_SPEC.md.

Frequently Asked Questions about release-spec

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

FAQPage Schema
What is an App Store release specification and why do I need one for iOS submission?▼

An App Store release specification consolidates PRDs, architecture, testing plans, and ASO assets into a single document. It streamlines submission by documenting requirements, processes, and responsibilities for release readiness across pre-submission and compliance workflows.

How do I generate App Store release documentation from existing product and test specs?▼

Generate App Store release documentation by aggregating product-plan, architecture, implementation, and test spec inputs. The process pulls these files to assemble a structured RELEASE_SPEC.md covering pre-submission, build, QA, metadata, and legal compliance sections.

Can I use this release management workflow for macOS apps or is it limited to iOS?▼

The release management workflow applies to both iOS and macOS apps. It supports pre-submission, build, QA, metadata, and compliance workflows across Apple platforms to ensure complete release readiness before submission.

What's the best way to consolidate PRDs and ASO assets into a single release spec?▼

The best way to consolidate PRDs and ASO assets is to aggregate them alongside architecture and testing inputs. This produces a structured RELEASE_SPEC.md that aligns teams and documents requirements, processes, and responsibilities for launch readiness.

Do I need a TEST_SPEC.md file to create App Store submission documentation?▼

Yes, a TEST_SPEC.md file is required as an input. The documentation generation aggregates product, architecture, implementation, and testing plans to assemble a complete release specification for App Store submission.

Related Skills

Explore More Software Engineering Skills→
mazicimertmazicimert

product-development

Generate implementation specification documents from a product plan for iOS/macOS apps.

Community
Advanced
AradotsoAradotso
4

app-store-connect-cli

Automate App Store Connect build uploads, TestFlight publishing, and App Store submissions.

Official
Advanced
keep-starknet-strangekeep-starknet-strange
8

play-store-review-aso

Audit Google Play listings for policy compliance and ASO best practices.

Official
Intermediate
clawpod-appclawpod-app
46

deploy-checklist

Generates a deployment readiness checklist for pre-release verification.

Community
Intermediate