flow-next-setup_skill

This skill helps you set up flowctl locally and document CLAUDE.md instructions to enable reliable flow-next workflows.
  • Python

458

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill gmickel/gmickel-claude-marketplace --skill flow-next-setup

  • SKILL.md821 B
  • workflow.md10.0 KB

Overview

This skill provides an optional local setup for flowctl and creates CLAUDE.md / AGENTS.md instructions in your repo. It lets teams run Flow-Next workflows from the command line and surface agent guidance files for other tooling. Use it when you want a portable, local way to coordinate plan-first workflows and multi-model gates.

How this skill works

The setup copies a flowctl binary into .flow/bin and adds usage instructions to CLAUDE.md and AGENTS.md in the repository. It also ensures scripts are copied (not symlinked) for portability, detects existing installs, and can update the files safely on re-run. The plugin remains functional without this local install; this is an optional convenience layer for CLI access and agent interoperability.

When to use it

  • You want CLI access to flowctl for local development or CI tasks
  • You need human- or tool-readable CLAUDE.md/AGENTS.md for other AI agents or code-review tools
  • You plan to run Ralph autonomous mode or overnight runs with local orchestration
  • You want a portable setup that works across machines without symlink issues
  • You prefer an explicit, repo-contained installation for auditability

Best practices

  • Keep .flow/bin in your PATH for easy CLI invocation and document this in CONTRIBUTING.md
  • Commit CLAUDE.md and AGENTS.md so other agents and reviewers have stable instructions
  • Run the setup on CI agents to ensure reproducible environments and avoid per-machine differences
  • Re-run the setup when updating Flow-Next versions to let it detect and apply safe updates
  • Treat the local install as optional; maintain plugin-based workflows for users who prefer no local artifacts

Example use cases

  • Developer installs flowctl locally to run plan-first workflows and iterate rapidly from the terminal
  • Team adds CLAUDE.md/AGENTS.md so Codex, Cursor, or other agents can follow the same repo-specific guidance
  • CI pipeline runs the setup step to ensure flowctl is available for automated multi-model review gates
  • Maintainer enables Ralph autonomous mode for overnight coding while keeping instructions embedded in the repo
  • Contributor re-runs setup to update helper scripts without breaking other environments

FAQ

No. The plugin works without a local install. This setup is optional and intended for convenience and interoperability.

Will setup overwrite existing files or links?

The installer copies scripts (not symlinks) and detects existing installs. It will offer safe updates rather than blindly overwriting.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational