LandryPouth

flow-next

Rank the current project state into the one command worth running right now — a blocked story, a "done" claim with no captured verify behind it, stale proof, a proven story with unshipped work, or a planned story with no worktree yet. Read-only, no side effects, scoped to the checkout it runs from. Use when you don't know what to do next. Wraps `ai-flow next`.

flow-review

Review a diff before merge against project rules, architecture, tests, security, and story acceptance criteria — findings first, ranked by severity, each grounded in a file and line. Use when asked whether a change is safe, to catch blocking issues, or to check the work before a pull request goes out. Runs as a quick checklist by default; each dimension has an opt-in deep section for refactors, cross-module change, and high-risk work.

flow-setup

Scaffold Coding Flow into the current project from Claude Code (runs the published `init`). Use once per repo, right after installing the plugin, so setup happens in one place without switching to a terminal. Use when the user wants to install, set up, or scaffold Coding Flow in a repository.

flow-ship

Push the current branch and open or update one pull request against the base, with the latest verify evidence attached to the PR body. Use when a story is verified and ready for review or merge. Wraps `ai-flow ship`; it is idempotent (one feature = one branch = one PR) and refreshes the proof without overwriting the human text of the description.

flow-status

Show where every epic and story actually stands — proof-derived state (verified / stale / blocked / planned), the worktree linked to each story, and the branch policy reminder. Read-only, no side effects. Use any time you want to know the state of the project without leaving Claude Code, not just after running a workflow skill. Wraps `ai-flow status`.