Agent skill

Flow Next

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

Install Flow Next

skills CLI

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

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

GitHub CLI

$ gh skill install gmickel/flow-next flow-next --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 .claude/skills/flow-next && 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/

Paste into Claude Code

Install the "flow-next" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next into .claude/skills/flow-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next", 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

$skill-installer install https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next

Type 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.

skills CLI

$ npx skills add gmickel/flow-next --skill flow-next -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install gmickel/flow-next flow-next --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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 .agents/skills/flow-next && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "flow-next" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next into .agents/skills/flow-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next", 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.

skills CLI

$ npx skills add gmickel/flow-next --skill flow-next -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install gmickel/flow-next flow-next --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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 .cursor/skills/flow-next && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "flow-next" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next into .cursor/skills/flow-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next", 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

$ gemini skills install https://github.com/gmickel/flow-next.git --path plugins/flow-next/skills/flow-next

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add gmickel/flow-next --skill flow-next -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install gmickel/flow-next flow-next --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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 .gemini/skills/flow-next && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "flow-next" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next into .gemini/skills/flow-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next", 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.

GitHub CLI

$ gh skill install gmickel/flow-next flow-next

Installs 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).

skills CLI

$ npx skills add gmickel/flow-next --skill flow-next -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ 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 .github/skills/flow-next && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "flow-next" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next into .github/skills/flow-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next", 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.

skills CLI

$ npx skills add gmickel/flow-next --skill flow-next -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install gmickel/flow-next flow-next --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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 .opencode/skills/flow-next && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "flow-next" agent skill from https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next into .opencode/skills/flow-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flow-next", 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.

Facts

Skill name: flow-next
GitHub stars: 707
Token cost: ~1.6k tokens
SKILL.md length: 306 words
Files: 2 (incl. references)
Skills in repo: 43
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

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

Works in 3 steps: Find relevant spec → Create task → Add description + acceptance (combined)
Tasks that involve OAuth and OpenID Connect
SKILL.md covers Preamble, Quick Reference, Common Patterns and ID Format, plus 1 more section
Calls jq

What it does

Flow Next is an agent skill from gmickel/flow-next. Manage .flow/ tasks and specs. Triggers: 'show me my tasks', 'list specs', 'what tasks are there', 'add a task', 'create task', 'what's ready', 'task status', 'show fn-1-add-oauth'. NOT for /flow-next:plan or /flow-next:work.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/declined.md`).

It sits in Backend & APIs, covering OAuth and OpenID Connect. 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

Tasks that involve OAuth and OpenID Connect

Example prompts

“show me my tasks”
“list specs”
“what tasks are there”
“/flow-next”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

Find relevant spec
Create task
Add description + acceptance (combined)

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 nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- jq
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 loads about 1.6k tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 59 tokens; SKILL.md has 306 words of instructions outside code blocks.

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

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 passed

The automated check found no risky patterns in SKILL.md.

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). 306 words, ~1,571 tokens.

Download SKILL.mdSave it as .claude/skills/flow-next/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: flow-next
description: Manage .flow/ tasks and specs. Triggers: 'show me my tasks', 'list specs', 'what tasks are there', 'add a task', 'create task', 'what's ready', 'task status', 'show fn-1-add-oauth'. NOT for /flow-next:plan or /flow-next:work.

Flow-Next Task Management

Quick task operations in .flow/. For planning features use /flow-next:plan, for executing use /flow-next:work.

Preamble

CRITICAL: flowctl is BUNDLED — NOT installed globally. which flowctl will fail (expected). Define once; subsequent blocks 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"

Discover all commands/options:

bash

$FLOWCTL --help
$FLOWCTL <command> --help   # e.g., $FLOWCTL task --help

Quick Reference

bash

# Check if .flow exists
$FLOWCTL detect --json

# Initialize (if needed)
$FLOWCTL init --json

# List everything (specs + tasks grouped)
$FLOWCTL list --json

# List all specs
$FLOWCTL specs --json

# List all tasks (or filter by spec/status)
$FLOWCTL tasks --json
$FLOWCTL tasks --spec fn-1-add-oauth --json
$FLOWCTL tasks --status todo --json

# View spec with all tasks
$FLOWCTL show fn-1-add-oauth --json
$FLOWCTL cat fn-1-add-oauth              # Spec markdown

# View single task
$FLOWCTL show fn-1-add-oauth.2 --json
$FLOWCTL cat fn-1-add-oauth.2            # Task spec

# What's ready to work on?
$FLOWCTL ready --spec fn-1-add-oauth --json

# Create task under existing spec
$FLOWCTL task create --spec fn-1-add-oauth --title "Fix bug X" --json

# Set task description and acceptance (combined, fewer writes; unique per-task temp paths)
$FLOWCTL task set-spec fn-1-add-oauth.2 --description "${TMPDIR:-/tmp}/flow-desc-fn-1-add-oauth.2.md" --acceptance "${TMPDIR:-/tmp}/flow-accept-fn-1-add-oauth.2.md" --json

# Or use stdin with heredoc (no temp file):
$FLOWCTL task set-description fn-1-add-oauth.2 --file - --json <<'EOF'
Description here
EOF

# Start working on task
$FLOWCTL start fn-1-add-oauth.2 --json

# Mark task done (unique per-task temp paths)
echo "What was done" > "${TMPDIR:-/tmp}/flow-summary-fn-1-add-oauth.2.md"
echo '{"commits":["abc123"],"tests":["npm test"],"prs":[]}' > "${TMPDIR:-/tmp}/flow-evidence-fn-1-add-oauth.2.json"
$FLOWCTL done fn-1-add-oauth.2 --summary-file "${TMPDIR:-/tmp}/flow-summary-fn-1-add-oauth.2.md" --evidence-json "${TMPDIR:-/tmp}/flow-evidence-fn-1-add-oauth.2.json" --json

# Validate structure (one spec; repo-wide through a counts-and-errors projection)
$FLOWCTL validate --spec fn-1-add-oauth --json
$FLOWCTL validate --all --json | jq '{valid, total_specs, total_tasks, total_errors, total_warnings, root_errors, failing: [.specs[] | select(.errors | length > 0) | {spec, errors}]}'

Common Patterns

"Add a task for X"

Find relevant spec:

bash

# List all specs
$FLOWCTL specs --json

# Or show a specific spec to check its scope
$FLOWCTL show fn-1 --json

Create task:

bash

$FLOWCTL task create --spec fn-N --title "Short title" --json

Add description + acceptance (combined):

bash

# Unique per-task temp paths — written + consumed in this one block
cat > "${TMPDIR:-/tmp}/flow-desc-fn-N.M.md" << 'EOF'
**Bug/Feature:** Brief description

**Details:**
- Point 1
- Point 2
EOF
cat > "${TMPDIR:-/tmp}/flow-accept-fn-N.M.md" << 'EOF'
- [ ] Criterion 1
- [ ] Criterion 2
EOF
$FLOWCTL task set-spec fn-N.M --description "${TMPDIR:-/tmp}/flow-desc-fn-N.M.md" --acceptance "${TMPDIR:-/tmp}/flow-accept-fn-N.M.md" --json

"What tasks are there?"

bash

# All tasks, projected (add --spec fn-1-add-oauth for one spec)
$FLOWCTL tasks --json | jq -c '[.tasks[] | {id, title, status, spec}]'

# Ready tasks for a spec
$FLOWCTL ready --spec fn-1-add-oauth --json

"What's next?"

bash

$FLOWCTL brief

brief is orientation only: it omits blocked and dependency-waiting tasks, so never answer a task listing from it.

"Show me task X"

bash

$FLOWCTL show fn-1-add-oauth.2 --json   # Metadata
$FLOWCTL cat fn-1-add-oauth.2           # Full spec

(Legacy fn-1.2 / fn-1-xxx.2 still works.)

Create new spec (rare - usually via /flow-next:plan)

bash

$FLOWCTL spec create --title "Spec title" --json
# Returns: {"success": true, "id": "fn-N-spec-title", ...}

Close a spec as won't-do

bash

$FLOWCTL spec close fn-1-add-oauth --retire superseded --by fn-2-sso --json

Pick the reason that is true: superseded (another spec replaced it), delivered-elsewhere (it shipped under another spec or pull request) or moot (it is no longer needed, including a decision not to build it). Name each successor with --by. Its never-run tasks read retired, not done.

Before closing any spec: read references/declined.md; it decides whether the close earns a .flow/memory/declined/ file.

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

ID Format

Spec: fn-N-slug where slug is derived from title (e.g., fn-1-add-oauth, fn-2-fix-login-bug)
Task: fn-N-slug.M (e.g., fn-1-add-oauth.1, fn-2-fix-login-bug.2)

Legacy formats fn-N and fn-N-xxx (random 3-char suffix) are still supported.

Notes

Run $FLOWCTL --help to discover all commands and options
Every write goes through a flowctl subcommand, except the .flow/memory/declined/*.md file above, which has no flowctl verb. A session that edits .flow/ JSON or task markdown by hand has broken this.
Every read comes from .flow/ state, via --json (detect, list, specs, tasks, show, ready) or cat for markdown. An answer assembled from files skimmed by hand has broken this.
A task marked complete is closed with flowctl done carrying both --summary-file and --evidence-json. A bare status flip has broken this.
Requests that need real planning or execution are handed off, to flow-next:flow-next-plan and flow-next:flow-next-work. Improvising them here has broken this.

Files

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

SKILL.md
references/declined.md

Open the folder on GitHubat commit 09e291e

Compare with similar skills

Flow Next 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 compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Flow Next this skillgmickel/flow-next	707	—	~1.6k	Automated safety check: Pass	MIT	today
Fortify Developmentcoollabsio/coolify	63k	4 repos	~1.9k	Automated safety check: Pass	MIT	today
Antipattern Preventiondoorkeeper-gem/doorkeeper	5.5k	—	~1.1k	Automated safety check: Pass	MIT	yesterday
OmniRoute Provider Managementdiegosouzapw/OmniRoute	74k	—	~2.4k	Automated safety check: Pass	MIT	today
Stripe Best Practiceskanchengw/cnllm	175	3 repos	~925	Automated safety check: Pass	Apache-2.0	3 mo ago
Notion Worker Third-Party Auth Guidemakenotion/workers-template	439	1 repos	~3.5k	Automated safety check: Notes	MIT	27 days ago

Similar skills

Fortify Development
coollabsio/coolify
ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.
63k GitHub starsUsed in 4 repos~1.9k tokens
Backend & APIsAuto-check passed
Antipattern Prevention
doorkeeper-gem/doorkeeper
Avoid common Ruby and Rails antipatterns that degrade maintainability and performance.
5.5k GitHub stars~1.1k tokensUpdated yesterday
Backend & APIsAuto-check passed
OmniRoute Provider Management
diegosouzapw/OmniRoute
Manages AI provider connections, API keys, OAuth flows and connection tests through OmniRoute's REST API across its 327-provider catalog.
74k GitHub stars~2.4k tokensUpdated today
Backend & APIsAuto-check passed
Stripe Best Practices
kanchengw/cnllm
Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial…
175 GitHub starsUsed in 3 repos~925 tokens
Backend & APIsAuto-check passed
Notion Worker Third-Party Auth Guide
makenotion/workers-template
Official
Decides whether a Notion Worker should use a brokered credential, a plaintext environment secret, or OAuth to authenticate against a non-Notion service.
439 GitHub starsUsed in 1 repo~3.5k tokens
Backend & APIsAuto-check: notes
Dependency Safety
doorkeeper-gem/doorkeeper
Ensure gems are safe, necessary, and properly constrained when adding, updating, or reviewing dependencies in Doorkeeper.
5.5k GitHub stars~931 tokensUpdated yesterday
Backend & APIsAuto-check passed

Questions about Flow Next

What does Flow Next do?

Manage .flow/ tasks and specs. An agent skill from gmickel/flow-next. Flow Next is an agent skill from gmickel/flow-next.flow/ tasks and specs.

When should I use Flow Next?

Flow Next fits situations like: tasks that involve OAuth and OpenID Connect.

How do I install Flow Next in Claude Code?

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

How do I install Flow Next in Codex?

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

Can I use Flow Next 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 -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, .gemini/skills/flow-next, .github/skills/flow-next and .opencode/skills/flow-next in your project.

What does Flow Next need to run?

Going by SKILL.md and its folder, Flow Next needs the command-line tools its instructions call (jq).

Does Flow Next 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 safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Flow Next use?

Flow Next 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 use?

About 1.6k tokens (SKILL.md is roughly 6.3k 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 266 tokens, read only when the agent opens those files.

What are the alternatives to Flow Next?

Skills that share tags, products or a category with Flow Next: Fortify Development (coollabsio/coolify, 63k stars), Antipattern Prevention (doorkeeper-gem/doorkeeper, 5.5k stars), OmniRoute Provider Management (diegosouzapw/OmniRoute, 74k stars) and Stripe Best Practices (kanchengw/cnllm, 175 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Flow Next?

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.

Install Flow Next

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Flow-Next Task Management

Preamble

Quick Reference

Common Patterns

"Add a task for X"

"What tasks are there?"

"What's next?"

"Show me task X"

Create new spec (rare - usually via /flow-next:plan)

Close a spec as won't-do

ID Format

Notes

Files

Compare with similar skills

Similar skills

More from gmickel/flow-next

Related

Questions about Flow Next