Is this setup required to use Flow-Next?

No. It is fully optional; Flow-Next works without a local flowctl install via the plugin.

Will installing flowctl override my existing setup?

The setup is safe to re-run. It will detect an existing installation and offer to update.

Where does flowctl get installed and how is PATH updated?

Flowctl is copied into a .flow/bin directory and the PATH is updated to include that location.

flow-next-setup

npx machina-cli add skill gmickel/gmickel-claude-marketplace/flow-next-setup --openclaw

Files (1)

SKILL.md

843 B

Flow-Next Setup (Optional)

Install flowctl locally and add instructions to project docs. Fully optional - flow-next works without this via the plugin.

Benefits

flowctl accessible from command line (add .flow/bin to PATH)
Other AI agents (Codex, Cursor, etc.) can read instructions from CLAUDE.md/AGENTS.md
Works without Claude Code plugin installed

Workflow

Read workflow.md and follow each step in order.

Notes

Fully optional - standard plugin usage works without local setup
Copies scripts (not symlinks) for portability across environments
Safe to re-run - will detect existing setup and offer to update

Source

git clone https://github.com/gmickel/gmickel-claude-marketplace/blob/main/plugins/flow-next/skills/flow-next-setup/SKILL.md

View on GitHub

Overview

Flow-Next Setup provides an optional local install of the flowctl CLI and adds CLAUDE.md/AGENTS.md instructions to your project docs. It makes flowctl accessible from the command line by placing binaries in .flow/bin and updating PATH, and ensures other AI agents can read setup guidance. The feature is fully optional, and Flow-Next works without this setup via the plugin.

How This Skill Works

Triggered by /flow-next:setup, it copies setup scripts into .flow/bin, installs flowctl locally, and updates PATH so the CLI is usable from the terminal. It also creates or updates CLAUDE.md and AGENTS.md so other AI agents can read setup instructions. The process is safe to re-run and will detect an existing installation to offer updates, and you can follow workflow.md after setup.

When to Use It

You want to run flowctl locally for debugging or automation in your project.
Your project docs need CLAUDE.md/AGENTS.md instructions for AI agents to follow.
You prefer a portable setup that works without Claude Code plugin installed.
You are integrating Flow-Next in a CI/CD or multi-environment setup and want a repeatable install.
You want to re-run the setup to detect and update an existing installation.

Quick Start

Step 1: Trigger the setup by running the flow-next:setup flow.
Step 2: Install flowctl locally into .flow/bin and update PATH.
Step 3: Ensure CLAUDE.md/AGENTS.md exist in docs and test flowctl access.

Best Practices

Verify that .flow/bin is on your PATH after installation.
Copy scripts (not symlinks) to improve portability across environments.
Follow the workflow in workflow.md in conjunction with this setup.
Rerun the setup to detect existing installation and apply updates.
Keep CLAUDE.md and AGENTS.md up to date with current agent guidelines.

Example Use Cases

A developer runs /flow-next:setup to enable local CLI access during feature work.
Docs are updated with CLAUDE.md/AGENTS.md so agents can read instructions.
CI pipelines use the local flowctl to validate flows across environments.
Flow-Next is used in an environment without the Claude Code plugin installed.
A team re-runs setup to update to a newer flowctl version.

Frequently Asked Questions

Add this skill to your agents