archflow-releaselisted

> Arguments are the text after the skill name. # /archflow-release — Inspect and manage releases Arguments (`the text the user wrote after the skill name`): `new [name]`, `start [slug]`, `ship`, or empty for status. The release is the v2.0 outer-loop unit. This command surfaces the pipeline and drives the release-level lifecycle actions. It reads the index (`roadmap.yaml`), the active release file, and the shipped ledger; it does not itself write application code. ## Usage ``` /archflow-release → status: pipeline + active release progress + shipped ledger /archflow-release new [name] → create a release from the backlog (feature-planner Mode B) /archflow-release start [slug] → transition a ready release to in_progress (the build gate) /archflow-release ship → run the Phase 5 ship ritual for the active release ``` ## `release` (no argument) — status Read `.archflow/roadmap.yaml`. Print: - **Active release** (`active_release`): its goal, and story progress from `.archflow/releases/{active_release}.yaml` — count by readiness status (spec_ready / design_ready / contract_ready / ready / in_progress / review / parked / done), release_criteria met/total, and any stories carrying `started_ungated`. - **Parked stories**, each with its open `parked.question` and whether it blocks the ship. A release quietly stuck on an unanswered decision must be visible here, not only in an autopilot ledger. - **Pipeline** (`releases[]`): each planning/r