release▌

Purpose: Take a project from "code is ready" to "tagged and ready to push."

Write customer-focused press releases before building to align stakeholders on product vision. \n \n Follows Amazon's Working Backwards methodology: start with a press release and FAQ before engineering begins, forcing clarity on customer value and problem solved \n Structured template covers headline, problem statement, solution (outcomes not features), executive quote, supporting details, and call to action \n Serves as a planning and alignment tool, not a launch-day marketing document; helps

Centralized release campaign management using RELEASE.md as the single source of truth for all release data, deliverables, and timelines. \n \n Organizes release information across 18 sections covering project snapshot, metadata, narrative, DSP strategy, marketing, PR, physical production, touring, budget, and performance tracking \n Automatically infers artist and release from user context, then creates, reads, or updates the corresponding RELEASE.md document in the releases/{release-slug}/ fol

End-to-end release workflows for TestFlight and App Store distribution. \n \n Supports iOS, macOS, visionOS, and tvOS with platform-specific build formats ( .ipa for iOS/visionOS/tvOS, .pkg for macOS) \n One-command publishing via asc publish testflight or asc publish appstore , or manual multi-step workflows for granular control \n Includes build upload, version attachment, TestFlight group distribution, and App Store submission with optional polling and confirmation \n Requires valid credentia

Professional press releases in AP style with inverted pyramid structure and fact-checking. \n \n Covers all major release types: product launches, funding announcements, partnerships, milestones, and executive hires \n Includes detailed AP style formatting rules, headline guidelines, dateline conventions, and quote attribution standards \n Provides research workflows using inference.sh CLI to verify claims, check market data, and gather industry context before writing \n Features section-by-sect

Automated multi-language release workflow with auto-detected version files and semantic versioning. \n \n Supports Node.js, Python, Rust, Claude Plugin, and generic projects with automatic configuration detection \n Generates changelogs in multiple languages (English, Chinese, Japanese, Korean, German, French, Spanish) with proper section translations and third-party contributor attribution \n Groups commits by skill/module, creates separate conventional commits per group, and updates README fil