Flow Workflows

flow-workflows

Guided `feat` / `bug` workflows for terminal coding agents: a ticket reaches an open MR/PR through explicit, reviewable phases, not one big prompt. For developers running Claude Code (or opencode, Gemini CLI, Codex CLI) on real repos with tickets, reviewers and a deploy. You get named phases, an artifact on disk after each one, hard gates the agent never crosses alone, and an autonomy dial from "ask me everything" to "run it and record what you decided".

Quickstart

/plugin marketplace add mashware/flow-workflows
/plugin install flow@flow-plugins
/flow:init      # writes FLOW.md for this repo — auto-detects, asks the minimum
/flow:next      # routes you to init, resume or status, depending on where you are

Your first feature:

/flow:feat:start PROJ-123   # read the ticket, size it (XS/S/M/L), create the branch
/flow:feat:design           # architecture, DB, APIs, risks → 03-design.md
/flow:feat:build            # implement following the design, keep a log
/flow:feat:review           # multi-agent code review (mandatory)
/flow:feat:ship             # commit, push, open the MR/PR — after you confirm the preview

No ticket? `/flow:feat:start` with no arguments drafts the work from the conversation you just had.

The two chains

feat  start → brainstorm → design → plan → build → review → validate → ship
                (M/L)              (M/L)  └─── repeats per MR/PR of a train ───┘

bug   start → diagnose → investigate → fix → validate → review → postmortem → ship
                                                                   (M/L)

after ship, before merge:  green ⟲   pipeline red / conflicts / behind base
                           respond ⟲ reviewer threads: triage, debate, change, reply

size prunes:  XS  start → build → review → ship     S  + design (abridged) + validate
              M/L full chain; plan splits the work into stacked MR/PRs

Commands you will use every day

Command	What it does