Agent skill

Flow Next Prospect

by gmickel in gmickel/flow-next

Generate ranked candidate ideas grounded in the repo. An agent skill from gmickel/flow-next.

MITAuto-check: notesAgent Workflows

Install Flow Next Prospect

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

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

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

At a glance

Generate ranked candidate ideas grounded in the repo. An agent skill from gmickel/flow-next.

  • Works in 7 steps: Resume check — list active artifacts… → Ground — scan repo with graceful… → Generate — divergent-convergent +… → …
  • Asked what to build next
  • SKILL.md covers Preamble, Input, Autonomy block and Workflow, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Flow Next Prospect is an agent skill from gmickel/flow-next. Generate ranked candidate ideas grounded in the repo. Use when asked what to build next.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `agents/openai.yaml`, `personas.md` and `references/failure-branches.md`).

It sits in Agent Workflows. 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

  • Asked what to build next

Example prompts

  • “/flow-next-prospect”

Requirements

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

Workflow steps

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

  1. Resume check — list active artifacts <30d; ask fresh / open via plain-text numbered prompt. Corrupt artifacts surfaced but never offered.
  2. Ground — scan repo with graceful degradation: git log (30d), open specs, CHANGELOG top, memory matches, memory audit (if present)…
  3. Generate — divergent-convergent + persona seeding (≥2 of senior-maintainer / first-time-user / adversarial-reviewer, picked by focus hint…
  4. Critique — separate prompt pass that does NOT see the focus hint or persona texts; rejection floor ≥40% (≥60% under raise the bar); fixed…
  5. Rank — bucketed: high leverage 1-3, worth-considering 4-7, if-you-have-the-time 8+. Forced-format leverage sentence per survivor…
  6. Write artifact — atomic write-then-rename to .flow/prospects/-.md via flowctl prospect write --from-json. Same-day collisions suffix with…
  7. Handoff - plain-text numbered prompt for promote / chart (only if still singular+oversized+unclear) / interview / skip via the plain-text…

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:

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

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

Always · name and description, kept in context so the agent knows when to use it
~27
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
~3.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: 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: Read, Bash, Grep, Glob, Write, Edit, Task

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). 700 words, ~1,607 tokens.

Download SKILL.mdSave it as .claude/skills/flow-next-prospect/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
flow-next-prospect
description
Generate ranked candidate ideas grounded in the repo. Use when asked what to build next.
allowed-tools
Read, Bash, Grep, Glob, Write, Edit, Task
user-invocable
false

Prospect — upstream-of-plan idea generation

Read workflow.md for full phase-by-phase execution.

Generate many candidate ideas grounded in the repo, critique every one with explicit rejection reasons, and surface only the survivors bucketed by leverage. Output is a ranked artifact under .flow/prospects/<slug>-<date>.md that feeds promote / capture / chart / interview - never a fixed conveyor.

Chart boundary

Prospect is plural ("what should we do?"). Chart is singular ("how do we get this one idea to something specifiable?"). A selected survivor routes to /flow-next:chart only when it is still singular, oversized, and unclear. Otherwise promote or capture - do not manufacture a chart for a clear candidate. Unsure of the next hop: /flow-next:flow --explain.

Role: idea-prospecting coordinator (sequential single-chat - generate -> critique -> rank -> write -> handoff). Personas are prompt-level scaffolding inside this skill, not parallel subagent dispatch.

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

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="${CODEX_HOME:-$HOME/.codex}/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"

Inline skill (no context: fork) — keeps plain-text numbered prompt available throughout. Subagents can't call plain-text numbered prompts (Claude Code issues #12890, #34592), and Phases 0 + 6 both require user choice.

Input

Arguments: $ARGUMENTS

Format: [focus hint] — freeform single string. Optional. May be:

  • Concept — DX improvements, review-skill polish, test-suite health
  • Path — src/billing/ (ideate inside a subtree)
  • Constraint — quick wins under 200 LOC, minor-bump only, no new deps
  • Volume hint — top 3 (exactly 3 survivors), 50 ideas (generate ≥50), raise the bar (60-70% rejection target)

If empty, the skill picks its own coverage targets (15-25 candidates → 5-8 survivors).

Autonomy block

/flow-next:prospect is exploratory and human-in-the-loop. Autonomous loops have no business deciding what a repo should tackle next — that's a judgement call. Hard-error with exit 2 when running autonomously.

bash
if [[ "${FLOW_AUTONOMOUS:-}" == "1" || "${AUTONOMOUS:-}" == "1" \
   || " ${ARGUMENTS:-} " == *" mode:autonomous "* ]]; then
  echo "Error: /flow-next:prospect requires a user at the terminal; not compatible with autonomous mode." >&2
  exit 2
fi

No env-var opt-in. Autonomous runs never decide direction.

Workflow

Execute the phases in workflow.md in order:

Ask the user via plain text. Render the options below as a numbered list 1. … N., followed by a final option N+1. Other — type your own answer. Print the question, then the numbered list, then stop and wait for the user's next message before continuing. Parse the reply as: a bare number 1–N+1 → that option; the literal text of an option label → that option; free text after Other → custom answer.

  1. Resume check — list active artifacts <30d; ask fresh / open via plain-text numbered prompt. Corrupt artifacts surfaced but never offered.
  2. Ground — scan repo with graceful degradation: git log (30d), open specs, CHANGELOG top, memory matches, memory audit (if present), strategy snapshot (verbatim name / target_problem / approach / tracks / last_updated from flowctl strategy read --json when sections_filled >= 1; husk-vs-presence gate uses sections_filled, NOT [[ -f STRATEGY.md ]]). Emit a structured 30-50 line snapshot — titles + tags only, never raw bodies.
  3. Generate — divergent-convergent + persona seeding (≥2 of senior-maintainer / first-time-user / adversarial-reviewer, picked by focus hint per personas.md). One divergent prompt; no self-judging.
  4. Critique — separate prompt pass that does NOT see the focus hint or persona texts; rejection floor ≥40% (≥60% under raise the bar); fixed taxonomy (duplicates-open-epic | out-of-scope | out-of-scope-vs-strategy | insufficient-signal | too-large | backward-incompat | other); out-of-scope-vs-strategy is advisory only (to pursue a rejected idea anyway, capture it with /flow-next:capture); floor violation surfaces plain-text numbered prompt with frozen options regenerate | loosen-floor | ship-anyway.
  5. Rank — bucketed: high leverage 1-3, worth-considering 4-7, if-you-have-the-time 8+. Forced-format leverage sentence per survivor (Small-diff lever because X; impact lands on Y.); no numeric scores.
  6. Write artifact — atomic write-then-rename to .flow/prospects/<slug>-<date>.md via flowctl prospect write --from-json. Same-day collisions suffix with -2, -3. Optional floor_violation / generation_under_volume flags round-trip when upstream phases set them.
  7. Handoff - plain-text numbered prompt for promote / chart (only if still singular+oversized+unclear) / interview / skip via the plain-text numbered prompt; frozen numbered-options fallback when plain text is the prompt mechanism.
Show full SKILL.md (83 more words)Show less

The artifact verbs are flowctl prospect promote and flowctl prospect archive; there is no list/read verb, so read .flow/prospects/*.md directly.

Forbidden

  • Running autonomously — hard-block via the guard above.
  • Setting context: fork — plain-text numbered prompts must stay reachable.
  • Network calls — grounding is local-filesystem only (git, flowctl, memory, CHANGELOG).
  • Writing to .flow/specs/ directly — only flowctl prospect promote may do that.
  • Auto-archiving artifacts — only the explicit prospect archive subcommand moves files.
  • Dumping raw file bodies into the grounding snapshot — titles + tags only; structured 30-50 lines max.

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

  • SKILL.md
  • agents/openai.yaml
  • personas.md
  • references/failure-branches.md
  • references/resume-artifacts.md
  • workflow.md

Open the folder on GitHubat commit 09e291e

Compare with similar skills

Flow Next Prospect 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 Prospect compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Flow Next Prospect this skillgmickel/flow-next709—~1.6kAutomated safety check: NotesMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79589 repos~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    795 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-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.

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

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

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

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

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

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

Categories

Questions about Flow Next Prospect

What does Flow Next Prospect do?

Generate ranked candidate ideas grounded in the repo. An agent skill from gmickel/flow-next. Flow Next Prospect is an agent skill from gmickel/flow-next. Generate ranked candidate ideas grounded in the repo.

When should I use Flow Next Prospect?

Flow Next Prospect fits situations like: asked what to build next.

How do I install Flow Next Prospect in Claude Code?

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

How do I install Flow Next Prospect in Codex?

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

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

What does Flow Next Prospect need to run?

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

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

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

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

What are the alternatives to Flow Next Prospect?

Skills that share tags, products or a category with Flow Next Prospect: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Flow Next Prospect?

gmickel (a GitHub user) maintains it in gmickel/flow-next, which has 709 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.