release-spec

Generate a Release Specification document for App Store submission.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/ano4l/SiteRent --skill release-spec-ano4l
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-spec
Source: https://github.com/ano4l/SiteRent/tree/main/skills/product/release-spec
Command: npx skills add https://github.com/ano4l/SiteRent --skill release-spec-ano4l

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

App stores require a cohesive, compliant, and well-structured release package. This Skill automates the creation of a complete release specification, consolidating product requirements, architecture references, testing criteria, privacy considerations, and marketing strategy into a single, ready-to-submit document.

Core Features & Use Cases

  • Generate a RELEASE_SPEC.md document that consolidates PRD, architecture, and testing inputs into App Store submission-ready content.
  • Include sections for privacy manifest, build/versioning notes, asset requirements, release timelines, and QA criteria.
  • Use Case: A product team preparing for a new app launch can generate a full spec from existing docs to ensure alignment and compliance.

Quick Start

Generate a complete App Store release specification using your PRD, ARCHITECTURE.md, and TEST_SPEC.md.

Frequently Asked Questions about 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 files?▼

To generate App Store release documentation, you can aggregate your PRD, ARCHITECTURE.md, and TEST_SPEC.md inputs to automatically produce a consolidated RELEASE_SPEC.md file tailored for app submission.

What is included in an App Store release specification document?▼

An App Store release specification document includes privacy manifest references, build and versioning notes, asset requirement lists, release timelines, and QA criteria to ensure governance and compliance.

Can I use this to prepare privacy disclosures for cross-platform mobile apps?▼

Yes, you can use this to prepare privacy disclosures and governance artifacts for cross-platform mobile apps, including iOS and macOS releases requiring compliant app submission packages.

How do I consolidate product requirements and architecture references into a submission-ready spec?▼

You can consolidate product requirements and architecture references by aggregating information from existing technical documents to output a single, submission-ready release specification with marketing planning and quality criteria.

What is the best way to automate release management docs for app submission?▼

The best way to automate release management docs is to extract product, architecture, and testing criteria directly into a structured release workflow, ensuring alignment and compliance without manual document stitching.

Do I need a separate TEST_SPEC.md to generate a complete release package?▼

You need a TEST_SPEC.md to satisfy the quality criteria requirements, as the release specification aggregates testing inputs alongside product requirements and architecture references to output complete governance artifacts.