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.
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…
$ npx skills add gmickel/flow-next --skill flow-next-flow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gmickel/flow-next flow-next-flow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "flow-next-flow" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next-flow into .claude/skills/flow-next-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next-flow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next-flowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add gmickel/flow-next --skill flow-next-flow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gmickel/flow-next flow-next-flow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gmickel/flow-next.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/flow-next/skills/flow-next-flow .agents/skills/flow-next-flow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "flow-next-flow" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next-flow into .agents/skills/flow-next-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next-flow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gmickel/flow-next --skill flow-next-flow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gmickel/flow-next flow-next-flow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gmickel/flow-next.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/flow-next/skills/flow-next-flow .cursor/skills/flow-next-flow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "flow-next-flow" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next-flow into .cursor/skills/flow-next-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next-flow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/gmickel/flow-next.git --path plugins/flow-next/skills/flow-next-flow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add gmickel/flow-next --skill flow-next-flow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gmickel/flow-next flow-next-flow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gmickel/flow-next.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/flow-next/skills/flow-next-flow .gemini/skills/flow-next-flow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "flow-next-flow" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next-flow into .gemini/skills/flow-next-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next-flow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install gmickel/flow-next flow-next-flowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add gmickel/flow-next --skill flow-next-flow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gmickel/flow-next.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/flow-next/skills/flow-next-flow .github/skills/flow-next-flow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "flow-next-flow" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next-flow into .github/skills/flow-next-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next-flow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gmickel/flow-next --skill flow-next-flow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gmickel/flow-next flow-next-flow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gmickel/flow-next.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/flow-next/skills/flow-next-flow .opencode/skills/flow-next-flow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "flow-next-flow" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next-flow into .opencode/skills/flow-next-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next-flow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
flow-next-flowConductor 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". 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.
Read from SKILL.md and the folder at commit 09e291e. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
AskUserQuestionReadBashGrepGlobWriteEditTaskSkillFrom allowed-tools in the SKILL.md frontmatter.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: AskUserQuestion, Read, Bash, Grep, Glob, Write, Edit, Task, SkillAutomated 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.
The full file from gmickel/flow-next at commit 09e291e, republished under its MIT licence (© gmickel). 440 words, ~1,302 tokens.
.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.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.
CRITICAL: flowctl is BUNDLED - NOT installed globally. which flowctl will fail (expected). Define once; subsequent blocks (here and in workflow.md) use $FLOWCTL:
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"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:
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.
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 runsWith --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.
references/route-matrix.md at the route step.references/prototype-before-ask.md); at most one question per hop.stage: <name> - skipped(<kind>: <detail>)).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).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
SKILL.md and 16 other files (references) in plugins/flow-next/skills/flow-next-flow of gmickel/flow-next.
Open the folder on GitHubat commit 09e291e
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Flow Next Flow this skillgmickel/flow-next | 707 | — | ~1.3k | Automated safety check: Notes | MIT | |
| Reproduce Chat Statesdifferent-ai/openwork | 24k | — | ~673 | Automated safety check: Pass | Custom licence | |
| Dynamo Jira TicketDynamoDS/Dynamo | 2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Minimal Run And Auditlllllllama/RigorPilot-Skills | 497 | 2 repos | ~691 | Automated safety check: Pass | MIT | |
| Moav E2EMotherofallVPNs/MoaV | 448 | — | ~1.9k | Automated safety check: Notes | MIT | |
| Anchor Reprolynxlangya/techne | 105 | 1 repos | ~1.2k | Automated safety check: Pass | MIT |
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.
DynamoDS/Dynamo
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
lllllllama/RigorPilot-Skills
Rigor Run skill for README-first deep learning repo reproduction.
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.
lynxlangya/techne
Reproduce a behavioral bug before fixing it, record the failing probe, and verify the fix with the same probe.
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…
gmickel/flow-next
Resolve PR review feedback. An agent skill from gmickel/flow-next.
gmickel/flow-next
Resolve PR review feedback — fetch unresolved threads, triage, dispatch per-thread resolver agents, validate, commit, reply + resolve via GraphQL.
gmickel/flow-next
Manage .flow/ tasks and specs. An agent skill from gmickel/flow-next.
gmickel/flow-next
Audit .flow/memory/ entries against the current codebase and decide Keep / Update / Consolidate / Replace / Delete / Harden per entry.
gmickel/flow-next
Save the current conversation as a source-tagged flow-next spec, then offer review or editing.
gmickel/flow-next
Decision-map discovery for one oversized unclear idea before capture.
Categories
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".
Flow Next Flow fits situations like: the user states any of these without naming a skill; --auto runs unattended.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.