A plugin for Claude Code

From idea to done,
one slice at a time.

Flow runs a piece of work and keeps its state on disk, so it picks up days later in a new session. It comes back to you at two points in every slice.

Two kinds of work

One flow, whether you write code or run a project.

/flow:dev

Software work, in a repository

Takes the work from idea to a branch merged after your ok, locally or by pull request when you set it up. Ships presets for Astro, DatoCMS and Rails, which you can extend with your own guidelines or replace, works with any stack, and never edits your CLAUDE.md.

  • Resumes an interrupted work in a new session
  • Plans, builds and reviews with its own agents
  • Records the changelog and the version
/flow:project

Projects that people carry out

For work that takes weeks or months: a renovation, a client engagement, a strategy, a personal plan. It lives in a folder, never in a code repo.

  • Plans one slice at a time
  • Hands software slices over to /flow:dev
  • Archives the project when it closes

How a slice goes

Define it first.
Then build it, one slice at a time.

Each phase closes before the next opens. The detailed plan of a slice is written right before it starts, so it carries what the previous slices taught.

  1. 01

    Brainstorm

    For an idea that isn't clear yet. Finds out what you want, and why, before anything is framed.

    /flow:brainstorm
  2. 02

    Grill

    Settles the points still vague, in rounds of numbered questions, each with a recommended answer.

    /flow:grill
  3. 03

    Frame

    Writes down the problem worth solving and why it was chosen over the alternatives.

  4. 04

    Shape

    When there's more than one way to build it: shaping and breadboarding, through the shaping-skills plugin.

  5. 05

    Design

    When the work touches a screen, draws it from your design system or as a Claude artifact, and feeds corrections back into the shaping.

    /flow:design
  6. 06

    Slice

    Cuts the work into slices you can see working, and checks their impact on the code with two agents.

Then, slice by slice

Planned right before it starts and reviewed by a fresh agent. Built task by task by Flow's agents, each task reviewed. Back to you after the plan and at the close. Each slice runs in its own subagent, so your session stays light.

State on disk

Close the session. The work stays.

Everything Flow knows about a work is a file in your repo or your project folder. A new session reads it and picks up where the last one stopped, days later.

Changelog and version
Each finished work is recorded, and the version is bumped.
Decisions
Written, updated and checked against the code, one file each.
Memory search
Looks through a repo's, or a folder of projects', memory before anything new is written.
Your guidelines
One Markdown file per concern in docs/guidelines/, each with a one-line description. Every slice gets the ones that concern it, next to your stack's preset.
Territories
Decisions, changelog, guidelines or product context can live in another tool, through an adapter. With nothing set, they stay in docs/.
your-project/docs
work/
    2026-10-26-home-page/
        STATUS.md
        slices.md
        V2-plan.md
    archive/
    archived.md
decisions-log/
    2026-10-25-soft-dependencies.md
guidelines/
    testing.md
CHANGELOG.md
development-guidelines.md

Install

Install it once.
Use it in every project.

$claude plugin marketplace add spleenteo/flow --scope user
$claude plugin install flow@flow --scope user
$claude plugin install shaping-skills@flow --scope user

Then run /flow:dev in the project you'll work in. The start check lists what's missing, with the commands to run. Coming from an older Flow? The README has the upgrade steps.