flowlisted

# flow Skill (router) A flow is a story from initialization to completion. The user does NOT need to know CLI commands - recognize the intent and route it yourself. ## Trigger Examples -> Intent | User says (RU/EN) | Intent | Do | |---|---|---| | "Создай фло: <описание проблемы>" / "create a flow for ..." | init from description | `keryx flow init --title "<формализованный заголовок>"`, then follow [init.md](init.md) | | "Создай фло на основании <issue URL>" / "make a flow from this issue" / вставил issue-ссылку + "сделай" | init from issue | `keryx flow init --issue <url>`, then [init.md](init.md) | | "Заведи стори / инициализируй задачу / start a story" | init | ask for a problem description or issue link if missing, then init | | "Какие фло активны? / статус по фло / where are we on 003" | status | `keryx flow list` / `flow status <id>` | | "Отметь задачу T2 / добавь задачу в фло" | manage | [manage.md](manage.md): `flow task done/add` | | "Имплементация готова, PR создан" | accept implementation | [manage.md](manage.md): verify draft PR, `flow implemented --pr <url>` | | "Заверши фло / закрой стори / finish the flow" | complete | [complete.md](complete.md): confirm ACs, `flow complete` | | "Фло застрял / поставь на паузу" | block | `flow block <id> --reason` / `flow unblock` | Ambiguous ("сделай эту фичу" without flow context): if the work is non-trivial and multi-step, propose starting a flow; for one-liners just do the work. ## Roles - Starting new work: [init.md]