Run any Skill in Manus with one click

flow-next-setup

Stars667

Forks52

UpdatedJuly 22, 2026 at 07:50

Optional local install of flowctl CLI and CLAUDE.md/AGENTS.md instructions, plus an optional model-routing scaffold for the project instruction file. Use when user runs /flow-next:setup.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

gmickel

gmickel/flow-next

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

6 files

SKILL.md

readonly

name	flow-next-setup
description	Optional local install of flowctl CLI and CLAUDE.md/AGENTS.md instructions, plus an optional model-routing scaffold for the project instruction file. Use when user runs /flow-next:setup.
user-invocable	false

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

More from this repository

same repository

flow-next-drive

gmickel/flow-next

Drive any UI surface like a real user - a web app, a Chromium-backed desktop app (Electron / WebView2, reached over CDP), or a genuinely native app (macOS AppKit/SwiftUI, or a non-CDP webview) reached via the Cua Driver / Computer Use. Detects the surface, picks the best available driver, degrades gracefully. Use to navigate sites, verify deployed UI, test web or desktop apps, capture baseline screenshots, drive a sign-in flow, scrape data, fill forms, run an e2e check, or inspect current page state. Triggers on "check the page", "verify UI", "test the site", "test this app", "drive the app", "automate this desktop app", "read docs at", "look up API", "visit URL", "browse", "screenshot", "scrape", "e2e test", "login flow", "capture baseline", "see how it looks", "inspect current", "before redesign", "Electron app", "native app".

2026-07-22667

flow-next-impl-review

gmickel/flow-next

Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.

2026-07-22667

flow-next-make-pr

gmickel/flow-next

Open a PR with a cognitive-aid body rendered from flow-next spec state via gh. Use whenever asked to make or open a PR in a flow-next repo.

2026-07-22667

flow-next-pilot

gmickel/flow-next

Single-tick autonomous build-loop conductor. Advances one ready spec one stage per tick, emits PILOT_VERDICT. Use when asked to pilot a spec or backlog.

2026-07-22667

flow-next-plan-review

gmickel/flow-next

Carmack-level review of a flow-next spec or plan via the configured backend. Use when asked to review a plan or spec.

2026-07-22667

flow-next-plan

gmickel/flow-next

Plan a feature into a flow-next spec with tasks in .flow/. Use when asked to plan, spec out, or break down work (fn-N ids).

2026-07-22667

Run any Skill with one click