Plugin

flow

Flow turns Claude into a project partner who manages your backlog. Say "park this for later," and it queues the idea. Say "what's next?" and it finds the highest-priority ready item and offers to start, handling the bookkeeping so you stay in flow. It works as a lightweight scrum board with three ways to interact: talk to Claude conversationally, drag cards on the built-in Kanban board, or run multiple agents in parallel, each with filtered views. All three read and write the same backlog.json, no sync step, no drift. Lanes are fully configurable. Start with the default agile flow (Backlog → Refined → Ready → In Progress → Code Review → Done) or define your own columns and gate rules. The board, the API, and the agent all enforce them consistently. Conversational management: Add, reorder, refine, and complete items by talking naturally; no commands to memorize. Built-in Kanban board: Drag-and-drop web UI that syncs with the agent in real time; launch with one command. Multi-agent support: Leader agents assign work, worker agents get filtered views of only their items, plus unassigned ready work. Agent-initiated items: Claude adds bugs, tech debt, and follow-ups he discovers while working, linking them back to the source task. Linked items: Connect related items with typed links (blocks, follow-up, discovered-during, related) and a reason. Configurable lanes: Define your own workflow columns and gate rules; the board, REST API, and agent all enforce them at every layer. Threaded refinement: Structured Q&A threads on items keep discussions organized; tag @Agent for async responses Concurrency safe: Optimistic versioning and atomic writes prevent data loss when board and agent write simultaneously

• Published source
• Repository

Analysed

11 October 2026

Last observed

12 October 2026

What the code does

• Runs shell commands Code that starts system commands on the machine it runs on.
• Sends data to outside servers Code that posts data to network addresses.

Having a capability is not wrongdoing; many tools need these to do their job. It tells you what to check before you install.

This is public metadata, not a safety certification or complete assessment. Static analysis cannot establish what a tool does at runtime.