What problem does it solve? Backlog stories often start as bare stubs with just a title and one line, making them impossible to build against. This Skill turns those stubs into ready stories with acceptance criteria, subtasks, and gates, and safely refines stories already committed to a release without destroying verified work. ## Core Features & Use Cases - Backlog grooming: Elicits acceptance criteria and subtasks from the user, derives design/contract gates from true scope, and marks the story ready in backlog.yaml. - Release refinement: Edits stories already in a release file in place, re-deriving gates and regressing status only when a gate reopens, while preserving met/completed flags as verification evidence. - Status safety checks: Halts on done or archived stories, and stops to ask before touching stories that are in progress or under review. - Use Case: A product manager realizes a story in the active release needs a new API endpoint. Running /archflow-groom S2-11 updates the acceptance criteria, flips needs_contract to true, and regresses the story to spec_ready so the contract step runs again before building. ## Quick Start Ask the agent to run /archflow-groom S2-11 to refine that story's acceptance criteria, subtasks, and gates in place.