New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Flow Next Plan

by gmickel in gmickel/flow-next

Create structured build plans from feature requests or Flow IDs.

MITAuto-check passedBackend & APIs

Install Flow Next Plan

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

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

GitHub CLI
$ gh skill install gmickel/flow-next flow-next-plan --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-plan .claude/skills/flow-next-plan && 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-plan
GitHub stars
707
Token cost
~1.5k tokens
SKILL.md length
660 words
Files
12 (incl. references)
Skills in repo
43
Repo updated
First seen
Licence
MIT

At a glance

Create structured build plans from feature requests or Flow IDs.

  • Planning features
  • SKILL.md covers Preamble, No implementation code, Input and Options, plus 2 more sections
  • Calls cursor and claude
  • Designing implementation

What it does

Flow Next Plan is an agent skill from gmickel/flow-next. Create structured build plans from feature requests or Flow IDs. Use when planning features or designing implementation. Triggers on /flow-next:plan with text descriptions or Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2).

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including reference files (for example `references/examples.md`, `references/existing-id.md` and `references/judge-memory.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

  • Planning features
  • Designing implementation
  • /flow-next:plan with text descriptions
  • Flow IDs (fn-1-add-oauth

Example prompts

  • “/flow-next-plan”

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:

    • cursor
    • claude

    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 Plan loads about 1.5k tokens when it runs, and up to ~8.5k if it reads all its reference files. Until then it costs about 70 tokens; SKILL.md has 660 words of instructions outside code blocks.

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

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). 660 words, ~1,497 tokens.

Download SKILL.mdSave it as .claude/skills/flow-next-plan/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.
name
flow-next-plan
description
Create structured build plans from feature requests or Flow IDs. Use when planning features or designing implementation. Triggers on /flow-next:plan with text descriptions or Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2).
user-invocable
false

Flow plan

Turn an idea or an existing spec into a spec with right-sized tasks in .flow/, grounded in repo research. Plan writes no code.

Read working-rules.md first unless you already have this run; it holds for every step of this skill.

.flow/ is the only task tracker. Every spec and task is created or changed through flowctl. A markdown TODO list, a TodoWrite call, or a plan file kept outside .flow/ as the record has broken this.

Preamble

flowctl is bundled, not installed globally (which flowctl fails). Define it once; later blocks here and in steps.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"

Check once for flowctl copies left by an older install layout:

bash
LEFTOVERS=""
for p in .flow/bin/flowctl .flow/bin/flowctl.cmd .flow/bin/flowctl.py \
         .flow/bin/flowctl_bootstrap.py .flow/bin/flowctl-help.txt \
         .flow/bin/flowctl_tracker .flow/templates/spec.md .flow/usage.md; do
  [ -e "$p" ] && LEFTOVERS="${LEFTOVERS}${p}"$'\n' || true
done   # || true: an empty LEFTOVERS (the normal case) must read as success

None present: say nothing. Any present: print one line saying nothing reads them and they can be deleted by hand or by /flow-next:setup, then continue. Never ask, stop, or delete here.

No implementation code

The spec states what and why as contracts; each task states how: named files, the repo pattern to follow (file:line), ordering, and non-obvious gotchas. Code in a plan is limited to signatures and interfaces, pointers to existing patterns, a recent or surprising API from docs-scout, and a gotcha from practice-scout. A full function or module body, or a copy-paste block over about 10 lines, has broken this: implementation happens in /flow-next:work with fresh context, and code written here is paid for again there and drifts.

Input

Full request: $ARGUMENTS

Accepts a freeform idea; a spec id fn-N-slug (legacy fn-N, fn-N-xxx); a task id fn-N-slug.M (legacy fn-N.M, fn-N-xxx.M); a tracker handle such as wor-17 that flowctl show resolves (always the existing spec or task, never a new idea; see Step 1); and chained instructions such as "then review with /flow-next:plan-review".

Empty input: ask "What should I plan? Give me the feature or bug in 1-5 sentences." Under autonomy, report NEEDS_HUMAN: no planning input provided and stop.

A ready or captured spec is plan input. An unshaped, oversized idea with several consequential unknowns is not: recommend /flow-next:chart (or /flow-next:flow --explain when unsure) and stop. Plan decomposes understood work; it does not replace discovery.

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

Options

Autonomy. The literal token mode:autonomous in $ARGUMENTS (strip it) or FLOW_AUTONOMOUS=1 sets AUTONOMOUS=1. Then no question is ever asked: explicit flags win, and anything unset takes its default (depth below, research repo-scout, review the configured backend, none when it is ASK). A genuinely unanswerable ambiguity stops with a one-line NEEDS_HUMAN: <reason>.

Depth. --depth=short ("quick", "minimal"), --depth=standard ("normal"), --depth=deep ("comprehensive", "detailed"). Default SHORT. Depth picks the scout set (Step 1) and the spec sections (Step 4).

Research. Always repo-scout; --research=grep is a no-op and any other value is ignored.

Review. --review=codex ("review with codex", "codex review", "use codex"), --review=host ("host review", "use host": the host-native fresh-context reviewer), --review=none or --no-review ("no review", "skip review"). --review=rp and --review=export were removed: say "RepoPrompt review (rp, export) was removed in flow-next 8.0.0; review backends: claude, codex, copilot, cursor, host." once and treat review as nothing configured (ASK, below).

Initialize and capture one preflight snapshot before routing or scouting (also under autonomy), from the repository root (never this skill's directory, where flowctl finds no config). Every later config read uses this literal path:

bash
$FLOWCTL init --json
PLAN_CFG="${TMPDIR:-/tmp}/flow-plan-config-<suffix>.json"
$FLOWCTL preflight --json > "$PLAN_CFG" || printf '{"key":null,"value":{}}' > "$PLAN_CFG"

Plan asks no setup question: flags win, depth takes its default, and review uses the configured backend from the snapshot (.probes.review_backend.value.backend). When that reads ASK (nothing configured), review is none and the handoff says once "no review backend set; run setup or set review.backend". Show the hint:

(Tip: --depth=short|standard|deep, --review=codex|copilot|cursor|claude|host|none)

Workflow

Read steps.md and follow each step in order. Its optional paths (readiness warning, Route A, tracker-first mint, tracker projection, review, next-steps menu) load their references only when the step's condition holds.

Step 1 launches every scout in the depth-appropriate set, in ONE parallel Task call. A plan whose research skipped a scout in its tier, or ran the set sequentially, has broken this.

Output

  • Spec: .flow/specs/<spec-id>.json + .md; tasks: .flow/tasks/<spec-id>.M.json + .md.
  • No code changes. Specs and tasks live in .flow/; temporary drafts (the /tmp bodies steps.md writes) are fine.

© 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 11 other files (references) in plugins/flow-next/skills/flow-next-plan of gmickel/flow-next.

  • SKILL.md
  • references/examples.md
  • references/existing-id.md
  • references/judge-memory.md
  • references/next-steps-menu.md
  • references/readiness-warn.md
  • references/route-a-refine.md
  • references/selected-review.md
  • references/strategy-alignment.md
  • references/tracker-first-mint.md
  • references/tracker-projection.md
  • steps.md

Open the folder on GitHubat commit 09e291e

Compare with similar skills

Flow Next Plan 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 Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Flow Next Plan this skillgmickel/flow-next707—~1.5kAutomated safety check: PassMIT
Fortify Developmentcoollabsio/coolify63k4 repos~1.9kAutomated safety check: PassMIT
Antipattern Preventiondoorkeeper-gem/doorkeeper5.5k—~1.1kAutomated safety check: PassMIT
OmniRoute Provider Managementdiegosouzapw/OmniRoute74k—~2.4kAutomated safety check: PassMIT
Stripe Best Practiceskanchengw/cnllm1753 repos~925Automated safety check: PassApache-2.0
Notion Worker Third-Party Auth Guidemakenotion/workers-template4391 repos~3.5kAutomated safety check: NotesMIT

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 yesterday
    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

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 Plan

What does Flow Next Plan do?

Create structured build plans from feature requests or Flow IDs. Flow Next Plan is an agent skill from gmickel/flow-next. Create structured build plans from feature requests or Flow IDs.

When should I use Flow Next Plan?

Flow Next Plan fits situations like: planning features; designing implementation; /flow-next:plan with text descriptions; flow IDs (fn-1-add-oauth.

How do I install Flow Next Plan in Claude Code?

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

How do I install Flow Next Plan in Codex?

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

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

What does Flow Next Plan need to run?

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

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

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

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

What are the alternatives to Flow Next Plan?

Skills that share tags, products or a category with Flow Next Plan: 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 Plan?

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.