archflow-groomlisted

> Arguments are the text after the skill name. # /archflow-groom — Detail or refine a story Argument (`the text the user wrote after the skill name`): optional story id (e.g. `S2-11`). Empty → list stubs and ask which to groom. Grooming turns a bare stub (title + one line) into a `ready` story with acceptance criteria, subtasks, and gates, and **refines a story that is already in a release** when its scope turns out to be wrong. It is the canonical description of *how a story gets detailed* — `release.md` (feature-planner Mode B) and the phase-3 pull-forward both defer here rather than restating it. Grooming refines scope. It does NOT commit the story to a release or start a build — those stay separate on purpose, so a story can be made ready without anyone deciding when to ship it. ## Usage ``` /archflow-groom → list stubs in backlog.yaml, ask which to groom /archflow-groom S2-11 → groom that story, wherever it lives ``` **Two modes, chosen by where the story is, not by an argument.** A backlog story is groomed into `ready` (**backlog mode**). A story already in a release is refined in place with its gates re-derived (**release mode**). The user's question is "refine this story"; which file it happens to sit in is an implementation detail they should not have to know. ## Flow 1. Read `.archflow/current-phase.yaml` (for `mode`), `.archflow/project-settings.yaml` (for `project_type`) and `.archflow/backlog.yaml`. Resolve the id. With no argument,