Agent skill

Flow Next Flow

by gmickel in gmickel/flow-next

Conductor for whatever the user has - an idea or a request for a change, a spec or task id, a tracker issue, a branch or a path, a pasted bug report or console output, a how or why question about…

MITAuto-check: notesTesting & QA

Install Flow Next Flow

skills CLI
$ npx skills add gmickel/flow-next --skill flow-next-flow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install gmickel/flow-next flow-next-flow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/gmickel/flow-next.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/flow-next/skills/flow-next-flow .claude/skills/flow-next-flow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
flow-next-flow
GitHub stars
707
Token cost
~1.3k tokens
SKILL.md length
440 words
Files
17 (incl. references)
Skills in repo
43
Repo updated
First seen
Licence
MIT

At a glance

Conductor for whatever the user has - an idea or a request for a change, a spec or task id, a tracker issue, a branch or a path, a pasted bug report or console output, a how or why question about…

  • The user states any of these without naming a skill
  • SKILL.md covers Preamble, Mode detection, Autonomy refusal - runs right… and Invariants (every run), plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • --auto runs unattended

What it does

Flow Next Flow is an agent skill from gmickel/flow-next. Conductor for whatever the user has - an idea or a request for a change, a spec or task id, a tracker issue, a branch or a path, a pasted bug report or console output, a how or why question about the code, something slow to speed up, a cleanup that keeps behaviour, a design fork to settle, or "what should I do next". Use when the user states any of these without naming a skill; --auto runs unattended.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 17 other files, including reference files (for example `auto.md`, `references/backlog-mode.md` and `references/defect-intake.md`).

It sits in Testing & QA, covering QA and bug reports. The repository describes itself as: Faster than your agent alone. And better. A workflow plugin that takes a bug, idea or ticket to a verified pull request: specs, cross-model review by risk, live QA, receipts in… The licence is MIT.

When your agent uses it

  • The user states any of these without naming a skill
  • --auto runs unattended

Example prompts

  • “what should I do next”
  • “/flow-next-flow”

Requirements

  • Pre-approved tools (allowed-tools): AskUserQuestion, Read, Bash, Grep, Glob, Write, Edit, Task, Skill

What it can do on your machine

Read from SKILL.md and the folder at commit 09e291e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • AskUserQuestion
    • Read
    • Bash
    • Grep
    • Glob
    • Write
    • Edit
    • Task
    • Skill

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Flow Next Flow loads about 1.3k tokens when it runs, and up to ~22k if it reads all its reference files. Until then it costs about 105 tokens; SKILL.md has 440 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~105
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~22k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: AskUserQuestion, Read, Bash, Grep, Glob, Write, Edit, Task, Skill

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from gmickel/flow-next at commit 09e291e, republished under its MIT licence (© gmickel). 440 words, ~1,302 tokens.

Download SKILL.mdSave it as .claude/skills/flow-next-flow/SKILL.md (or your agent's skills folder). This skill also uses 16 other files; get the full folder from GitHub.
name
flow-next-flow
description
Conductor for whatever the user has - an idea or a request for a change, a spec or task id, a tracker issue, a branch or a path, a pasted bug report or console output, a how or why question about the code, something slow to speed up, a cleanup that keeps behaviour, a design fork to settle, or "what should I do next". Use when the user states any of these without naming a skill; --auto runs unattended.
allowed-tools
AskUserQuestion, Read, Bash, Grep, Glob, Write, Edit, Task, Skill
user-invocable
false

/flow-next:flow - the conductor

Flow chooses the next step so the user does not have to. It reads what it was given, routes from the shared routing reference, runs the routed stage skill, and continues until the next decision that belongs to a human. It re-implements no stage logic: capture, refine, plan, plan-review, work, qa, make-pr, resolve-pr, and land keep their own contracts, receipts, and gates.

Role: conductor, inline (no context: fork) so AskUserQuestion stays reachable. On hosts without it, fall back to a plain-text numbered prompt with a final Other - type your own answer option.

Read workflow.md for the hop loop. Read a reference only at the step that names it.

Preamble

CRITICAL: flowctl is BUNDLED - NOT installed globally. which flowctl will fail (expected). Define once; subsequent blocks (here and in workflow.md) use $FLOWCTL:

bash
FLOWCTL="${DROID_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}/scripts/flowctl"
[ -x "$FLOWCTL" ] || FLOWCTL="<plugin-root>/scripts/flowctl"   # <plugin-root> = the directory two levels above this skill's SKILL.md file (the harness gave you that file's absolute path when the skill loaded); substitute it literally
[ -x "$FLOWCTL" ] || FLOWCTL=".flow/bin/flowctl"

Mode detection

Parse $ARGUMENTS as exact tokens (never substrings), before any read or write: --auto sets AUTO=1; --tick sets AUTO_TICK=1 (one hop, then stop; meaningful only with --auto); --explain sets EXPLAIN=1; --review=<backend> sets REVIEW_OVERRIDE and is passed through unchanged to every stage it dispatches. The destination parse is shared by both modes:

bash
FLOW_UNTIL=""
FLOW_DESTINATION_ERROR=0
LAND_AUTHORIZED=0
LAND_SCOPE_SPEC=""
LAND_SCOPE_PR=""
AUTO=0
for ARG in $ARGUMENTS; do
  case "$ARG" in
    --auto) AUTO=1 ;;
    --until=merge) FLOW_UNTIL=merge ;;
    --until|--until=*) FLOW_DESTINATION_ERROR=1 ;;
  esac
done
if [ "$FLOW_DESTINATION_ERROR" = 1 ]; then
  if [ "$AUTO" = 1 ]; then
    echo 'PILOT_VERDICT=NEEDS_HUMAN spec=- stage=- reason="invalid destination; use --until=merge"'
  else
    echo 'NEEDS_HUMAN: invalid destination; use --until=merge'
  fi
  exit 1
fi
export FLOW_UNTIL

--until=merge authorizes landing the selected item in this invocation; read references/tail.md at that boundary. Consent is current host context, never recovered from an environment variable, old transcript or receipt. Consume destination tokens rather than passing them to a build stage; everything else is the starting point, verbatim.

AUTO=1: read auto.md and follow it. Attended runs never load it.

Show full SKILL.md (196 more words)Show less

Autonomy refusal - runs right after the token parse

Attended flow and flow --auto are two drivers and are never nested. Without --auto, flow is attended: under any autonomy marker (scan the marker namespace: FLOW_AUTONOMOUS, AUTONOMOUS=1, a mode:autonomous token), stop before any read or write:

NEEDS_HUMAN: /flow-next:flow is attended - run /flow-next:flow --auto for unattended runs

With --auto there is no marker refusal, because --auto sets FLOW_AUTONOMOUS and mode:autonomous for the stages it dispatches. A run that routed, dispatched, or asked under a marker it should have refused has broken this.

Invariants (every run)

  • Read working-rules.md before the first route step and follow it on every route.
  • Route on content and context, never on input kind, from references/route-matrix.md at the route step.
  • Ask only on a fork that is material and not observable (references/prototype-before-ask.md); at most one question per hop.
  • Never fabricate a review, QA or completion verdict. Every stage flow skips is recorded with its reason (stage: <name> - skipped(<kind>: <detail>)).
  • Invoke stage skills; never re-implement their steps inline. Land owns merge (only with current scoped consent, per references/tail.md); make-pr owns spec close. Never dispatch another flow or a loop from inside a run, and never force-push.
  • --explain writes nothing and dispatches nothing (references/explain.md).

Report shape (every stop)

Flow stopped at: <the human decision, "PR exists", or the observed landing outcome>
Route taken: <hop 1> -> <hop 2> -> ...   (an inline pick reads `prospect [picked: <candidate>]`)
stage: <name> - ran [<start>..<end>] | skipped(<policy|config|empty|error|reach|signal absent|despite unresolved risk>: <detail>) | failed(<reason>: <detail>)   (one line per stage reached)
Next: <natural-language prompt or slash command, or the decision the user must make>

© gmickel, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 16 other files (references) in plugins/flow-next/skills/flow-next-flow of gmickel/flow-next.

  • SKILL.md
  • auto.md
  • references/backlog-mode.md
  • references/defect-intake.md
  • references/explain.md
  • references/gate-selection-more.md
  • references/gate-selection.md
  • references/no-argument.md
  • references/plan-vs-no-plan.md
  • references/prototype-before-ask.md
  • references/qa-auto.md
  • references/qa-stage.md
  • references/route-matrix-more.md
  • references/route-matrix.md
  • references/spec-count.md
  • references/tail.md
  • workflow.md

Open the folder on GitHubat commit 09e291e

Compare with similar skills

Flow Next Flow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Flow Next Flow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Flow Next Flow this skillgmickel/flow-next707—~1.3kAutomated safety check: NotesMIT
Reproduce Chat Statesdifferent-ai/openwork24k—~673Automated safety check: PassCustom licence
Dynamo Jira TicketDynamoDS/Dynamo2k—~1.1kAutomated safety check: PassApache-2.0
Minimal Run And Auditlllllllama/RigorPilot-Skills4972 repos~691Automated safety check: PassMIT
Moav E2EMotherofallVPNs/MoaV448—~1.9kAutomated safety check: NotesMIT
Anchor Reprolynxlangya/techne1051 repos~1.2kAutomated safety check: PassMIT

Similar skills

  • Reproduce Chat States

    different-ai/openwork

    Fires known chat states in the running OpenWork desktop app, such as provider errors, retries and tool steps, so you can check how each renders.

    24k GitHub stars~673 tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Dynamo Jira Ticket

    DynamoDS/Dynamo

    Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.

    2k GitHub stars~1.1k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Minimal Run And Audit

    lllllllama/RigorPilot-Skills

    Rigor Run skill for README-first deep learning repo reproduction.

    497 GitHub starsUsed in 2 repos~691 tokens
    Testing & QAAuto-check passed
  • Moav E2E

    MotherofallVPNs/MoaV

    Run and debug MoaV's end-to-end tests — real protocol connectivity (client-test.sh) and the moav CLI smoke test — against a LIVE server, via the self-hosted e2e workflow or a local test VPS.

    448 GitHub stars~1.9k tokensUpdated yesterday
    Testing & QAAuto-check: notes
  • Anchor Repro

    lynxlangya/techne

    Reproduce a behavioral bug before fixing it, record the failing probe, and verify the fix with the same probe.

    105 GitHub starsUsed in 1 repo~1.2k tokens
    Testing & QAAuto-check passed
  • Creating A Coral Task

    Human-Agent-Society/CORAL

    Author a new CORAL task — the three pieces that must line up (task.yaml, seed/, a packaged grader/), the coral init → coral validate → smoke-test loop, and how to pick a grader pattern (stdout…

    1k GitHub stars~2.2k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

More from gmickel/flow-next

All 43 skills in this repo
  • Flow Next Resolve PR

    gmickel/flow-next

    Resolve PR review feedback. An agent skill from gmickel/flow-next.

    707 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Flow Next Resolve PR

    gmickel/flow-next

    Resolve PR review feedback — fetch unresolved threads, triage, dispatch per-thread resolver agents, validate, commit, reply + resolve via GraphQL.

    707 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Flow Next

    gmickel/flow-next

    Manage .flow/ tasks and specs. An agent skill from gmickel/flow-next.

    707 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed
  • Flow Next Audit

    gmickel/flow-next

    Audit .flow/memory/ entries against the current codebase and decide Keep / Update / Consolidate / Replace / Delete / Harden per entry.

    707 GitHub stars~3.1k tokensUpdated yesterday
    Auto-check: notes
  • Flow Next Capture

    gmickel/flow-next

    Save the current conversation as a source-tagged flow-next spec, then offer review or editing.

    707 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check: notes
  • Flow Next Chart

    gmickel/flow-next

    Decision-map discovery for one oversized unclear idea before capture.

    707 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check: notes

Categories

Questions about Flow Next Flow

What does Flow Next Flow do?

Conductor for whatever the user has - an idea or a request for a change, a spec or task id, a tracker issue, a branch or a path, a pasted bug report or console output, a how or why question about…. Flow Next Flow is an agent skill from gmickel/flow-next. Conductor for whatever the user has - an idea or a request for a change, a spec or task id, a tracker issue, a branch or a path, a pasted bug report or console output, a how or why question about the code, something slow to speed up, a cleanup that keeps behaviour, a design fork to settle, or "what should I do next".

When should I use Flow Next Flow?

Flow Next Flow fits situations like: the user states any of these without naming a skill; --auto runs unattended.

How do I install Flow Next Flow in Claude Code?

Run `npx skills add gmickel/flow-next --skill flow-next-flow -a claude-code`. Or copy the skill folder (plugins/flow-next/skills/flow-next-flow in gmickel/flow-next) into .claude/skills/flow-next-flow in your project. Claude Code loads it when a task matches its description.

How do I install Flow Next Flow in Codex?

Run `npx skills add gmickel/flow-next --skill flow-next-flow -a codex`. Or copy the skill folder (plugins/flow-next/skills/flow-next-flow in gmickel/flow-next) into .agents/skills/flow-next-flow in your project. Codex loads it when a task matches its description.

Can I use Flow Next Flow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gmickel/flow-next --skill flow-next-flow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/flow-next-flow, .gemini/skills/flow-next-flow, .github/skills/flow-next-flow and .opencode/skills/flow-next-flow in your project.

What does Flow Next Flow need to run?

SKILL.md names no scripts, command-line tools or credentials: Flow Next Flow is instructions for the agent only. Its frontmatter pre-approves these tools: AskUserQuestion, Read, Bash, Grep, Glob, Write, Edit, Task, Skill.

Does Flow Next Flow access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Flow Next Flow safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Flow Next Flow use?

Flow Next Flow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Flow Next Flow use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 21k tokens, read only when the agent opens those files.

What are the alternatives to Flow Next Flow?

Skills that share tags, products or a category with Flow Next Flow: Reproduce Chat States (different-ai/openwork, 24k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars), Minimal Run And Audit (lllllllama/RigorPilot-Skills, 497 stars) and Moav E2E (MotherofallVPNs/MoaV, 448 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Flow Next Flow?

gmickel (a GitHub user) maintains it in gmickel/flow-next, which has 707 GitHub stars. The repository holds 43 skills in this directory. The repository was last updated on October 7, 2026.

Source: gmickel/flow-next on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.