What problem does it solve? Teams lose track of which release is active, which stories are ready, and what has already shipped when release state lives in scattered notes. This Skill centralizes the release lifecycle by reading roadmap.yaml, release files, and the shipped ledger to drive status checks, release creation, build gating, and shipping. ## Core Features & Use Cases - Release status overview: Shows the active release's story progress by readiness status, parked stories blocking the ship, the release pipeline, shipped ledger, and backlog count. - Release creation: Derives a slug, suggests goals from backlog stubs and project KPIs, and invokes feature-planner Mode B to move groomed stories into a new release file. - Build gate and ship ritual: Enforces at most one in_progress release, transitions ready releases to active, and runs the Phase 5 ship ritual including versioning, tagging, release notes, and history archival. - Use Case: A product lead runs /archflow-release to see that three stories are still in review and one parked story blocks shipping, then answers the parked question and runs /archflow-release ship to cut version 1.4. ## Quick Start Ask the agent to run /archflow-release to show the current release pipeline status and active release progress.
