flow-next-setup
The flow-next-setup skill installs the flowctl CLI tool locally and generates CLAUDE.md and AGENTS.md documentation files for a project. Use this when a user requests /flow-next:setup to enable command-line access to flowctl and allow other AI agents to reference project instructions, though the flow-next plugin functions independently without this optional setup.
git clone --depth 1 https://github.com/gmickel/flow-next /tmp/flow-next-setup && cp -r /tmp/flow-next-setup/plugins/flow-next/skills/flow-next-setup ~/.claude/skills/flow-next-setupSKILL.md
# Flow-Next Setup (Optional) Wire this repo to the plugin: the versioned docs snippet plus flow-next configuration. **Fully optional** - flow-next works without this via the plugin. ## Benefits - Other AI agents (Codex, Cursor, etc.) can read instructions from CLAUDE.md/AGENTS.md ## Workflow Read [workflow.md](workflow.md) and follow each step in order. `workflow.md` is the common router. Resolve each documented gate before reading its direct `references/*.md` target. When a branch says **MUST read exactly one**, read that complete reference before acting; never preload sibling host or Ralph references. Unknown/malformed routing state uses the safe/common fallback named at that gate. ## Notes - **Fully optional** - standard plugin usage works without local setup - Copies nothing into the repo - plugin updates need no per-repo re-run, on any host - Safe to re-run - needed only when the snippet schema bumps or configuration/seeds change
Synthesize the current conversation context into a flow-next spec at `.flow/specs/<spec-id>.md` via `flowctl spec create + spec set-plan` — agent-native, source-tagged, with mandatory read-back before write. Triggers on /flow-next:capture, "capture spec", "lock down what we discussed", "make a spec from this conversation", "convert conversation to spec". Optional `mode:autofix` token runs without questions and requires `--yes` to commit. Optional `--rewrite <spec-id>` overwrites an existing spec; `--from-compacted-ok` overrides the incomplete-evidence refusal after compaction; `--override-strategy` proceeds despite a contradiction with an active STRATEGY.md track (and prompts to record the override as a decision); `--no-plan` sets the spec-level `no_plan` field after the write (explicit opt-in — never inferred).
Render a cognitive-aid PR body from flow-next state and open via gh. Triggers on /flow-next:make-pr with optional spec id and flags (--draft, --ready, --no-mermaid, --base <ref>, --memory, --dry-run). Auto-detects spec from current branch when no id given. NOT Ralph-blocked — autonomous loops can surface a draft PR for human review.
Audit `.flow/memory/` entries against the current codebase and decide Keep / Update / Consolidate / Replace / Delete / Harden per entry. Triggers on /flow-next:audit, "audit memory", "review memory", "refresh learnings", "sweep stale memory", "consolidate overlapping memory entries", "graduate a recurring lesson into a gate". Optional `mode:autofix` token in arguments runs without questions and marks ambiguous as stale (Harden is never auto-applied). Optional scope hint after the mode token (concept, category, module, or path) narrows what gets audited.
Show spec dependency graph and execution order. Use when asking 'what's blocking what', 'execution order', 'dependency graph', 'what order should specs run', 'critical path', 'which specs can run in parallel'.
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".
[deprecated alias] Renamed to flow-next-spec-completion-review in flow-next 1.0 — invoke the new skill. Removed in 2.0.
Export RepoPrompt context to a markdown file for review with an external LLM (ChatGPT, Claude web, etc.). Use when you want Carmack-level review but prefer an external model. Triggers on "export context", "export for external review", "export plan for ChatGPT", "export impl review context", "review with an external model", "export review context".