flow

01 / The methodology

A practice.
Not a pipeline.

Start with a real problem, plan only when it helps, let agents work on independent pieces in parallel, and check that what ships works. Adopt one skill or all of them; the workflow bends to the work.

The starters are the exception: they are deliberately opinionated, so a new project skips the setup debates and deploys on day one. Prefer other choices? Keep the practice and bring your own repo.

Intent → Plan? → Build → Ship

One Flow.
Whatever the task.

  1. 01 / Always

    Intent

    Know what matters and why. A plain request is enough; “explore this” asks in proportion to the change, nothing for a fix.

    explore
  2. 02 / When useful

    Plan?

    Agree on the approach in conversation. Say “spec it” and “break it down” only for a bet worth tracking.

    to-spec
  3. 03 / Parallel

    Build

    “Build it” implements the change, reviews and checks it, and ends with a verified branch that is not merged yet.

    build
  4. 04 / Proof

    Ship

    “Ship it” builds when the branch is not verified yet, lands it, and confirms the shipped commit is live.

    ship

Explore and Align are independent practices.

Explore product uncertainty before you build. Align the actual product to its vision, metrics, and roadmap. Neither is a mandatory stage of every change.

Find the right skill

Right-sized planning

Same practice.
Different needs.

There is no required order: start anywhere, skip any step. Say a phrase and the matching skill runs.

  • Quick fix

    Start with the request. No spec, no questions: build, check once, and ship it.

    "build it" → "ship it", or just "ship it"

  • Shaped idea

    Explore asks in proportion to the change; build the confirmed brief directly.

    "explore this" → "build it" → "ship it"

  • Tracked work

    Work worth tracking gets a spec and verifiable tasks before the build.

    "explore this" → "spec it" → "break it down" → "build it" → "ship it"

  • New project

    Start bootstraps from flow-next or flow-mono; explore runs alongside when you describe the product.

    "start a Next.js project" (explore alongside when you describe the product)

Every other skill can run at any time and never blocks delivery.

What Flow holds to

Product before process.

  1. Product before code

    Build useful software, not just completed tasks.

  2. Preserve intent

    Keep product, design, architecture, and significant decisions understandable and current.

  3. Human-directed, agent-executed

    Agents carry out the work, including setup and operations; people decide, and handle only the steps that need them, such as sign-in and secrets (decision 0049).

  4. Minimal process

    Use only the structure and skills the task requires; skills compose, and no sequence is mandatory. Humans say what and why; agents choose how.

  5. Evidence over claims

    Verify outcomes through tests, reviews, and real-world checks in proportion to risk: agents judge what needs evidence, and project scripts run the checks.

  6. Claude Code first, portable where free

    Use the host's built-ins instead of restating them; skills stay plain Markdown so other agents keep the method (decision 0062).

  7. Improve through use

    Develop Flow using Flow, and simplify it through real experience.

  8. Agent-first, API-first

    Build every product for agents and people; define consequential capabilities as contracts before interfaces.

Jump to, or try a question