ho-flowlisted

# Flow Set up the change, then run the phases in order. The phase skills do the work; this one decides which phase runs, and where the flow stops. ## Reading the request ``` solo <request> one agent runs every phase solo auto <request> the same, without pausing after the design relay <request> each phase hands off to another agent ``` If the request names no mode, use `mode` from `.ho/config.yaml`. If there is no config, use `solo` and say so. `auto` is an option on one task, never a mode and never a stored setting. It does not survive into the next request. ## Setting up If `.ho/` does not exist, create it: copy the protocol and config templates in, then tell the user what you added. Do not silently add a directory to someone's project. If one or more changes are already open and the request does not name one, list them and ask. Do not infer from recency, from ordering, or from which looks more prepared, and do not run all of them. Otherwise create `.ho/changes/YYYY-MM-DD-<slug>/change.yaml` with `status: draft`. ## Names These are the names. Do not invent variants — the next agent looks for exactly these: ``` .ho/config.yaml .ho/protocol.md .ho/changes/YYYY-MM-DD-<slug>/change.yaml .ho/changes/YYYY-MM-DD-<slug>/01-design.md .ho/changes/YYYY-MM-DD-<slug>/02-implementation.md .ho/changes/YYYY-MM-DD-<slug>/03-review.md ``` `status` is one of `draft`, `ready_for_implementation`, `implementing`, `ready_for_review`, `rework`, `complete`, `abandoned`. N