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 Chart

by gmickel in gmickel/flow-next

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

MITAuto-check: notes

Install Flow Next Chart

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

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

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

At a glance

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

  • Works in 4 steps: Infer the intended mode and operation… → Ask a blocking question only when two… → Read back any state-changing… → …
  • /flow-next:chart with an unshaped idea
  • SKILL.md covers Preamble, Prompt-first contract, Modes (disambiguate by argument) and Verdict grammar (exact), plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Flow Next Chart is an agent skill from gmickel/flow-next. Decision-map discovery for one oversized/unclear idea before capture. Triggers on /flow-next:chart with an unshaped idea, chart id, decision pin, --status, or stored tracker URL. Prompt-first adaptive loop - ground, chart a frontier, resolve one D-ID per invocation, brief for capture.

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `references/briefing-and-reopen.md`, `references/chart-mode.md` and `references/examples.md`).

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

  • /flow-next:chart with an unshaped idea
  • Stored tracker URL

Example prompts

  • “/flow-next-chart”

Requirements

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

Workflow steps

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

  1. Infer the intended mode and operation from $ARGUMENTS + conversation.
  2. Ask a blocking question only when two interpretations would materially change the chart, cost, or consent boundary.
  3. Read back any state-changing interpretation before persisting.
  4. Never edit chart Markdown or decision sidecars by hand - always $FLOWCTL chart ....

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

    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 Chart loads about 2.6k tokens when it runs, and up to ~14k if it reads all its reference files. Until then it costs about 75 tokens; SKILL.md has 1,191 words of instructions outside code blocks.

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

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

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). 1,191 words, ~2,633 tokens.

Download SKILL.mdSave it as .claude/skills/flow-next-chart/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
flow-next-chart
description
Decision-map discovery for one oversized/unclear idea before capture. Triggers on /flow-next:chart with an unshaped idea, chart id, decision pin, --status, or stored tracker URL. Prompt-first adaptive loop - ground, chart a frontier, resolve one D-ID per invocation, brief for capture.
allowed-tools
AskUserQuestion, Read, Bash, Grep, Glob, Write, Edit, Task
user-invocable
false

Chart - decision-map discovery (pre-capture)

Read workflow.md for routing and the mode dispatch table. It routes to exactly one mode reference per invocation (chart / work / briefing-reopen / re-entry); status mode and the safety recap stay inline there. Native prompts, adaptive traces, and the full flag tables: references/examples.md.

Takes one unshaped idea that is too big for a single capture session and wrapped in unknowns, and finds the route by resolving one decision at a time until the effort can be captured as one or more specs. Unit of work is a decision (D-ID), not a build task. Chart never writes a spec and never sets ready; output is a briefing handed to /flow-next:capture.

Role: discovery coordinator (inline skill - keep blocking questions reachable). Host agent owns grounding, interpretation, frontier judgment, evidence-route dispatch, prototype presentation, attended consent, re-charting, and the terminal verdict. flowctl owns atomic create/claim/resolve/scope/briefing/store mutations.

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="${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"

Inline skill (no context: fork) - keeps AskUserQuestion available for read-back consent and attended routes. Subagents cannot call blocking question tools. For read-only scouts use Task with subagent_type: Explore (or the host's generic read-only dispatch with Edit/Write disallowed when Explore is unavailable). On portable hosts without AskUserQuestion, fall back to a plain-text numbered prompt with a final Other - type your own answer option.

Prompt-first contract

Natural language is the primary control surface. Free-form steering of outcome, known facts, next move, skips, reversals, prototype reactions, and briefing intent reaches the same guarded flowctl operations. Flags and exact subcommands are documented for automation, scripting, and debugging - they are never required vocabulary for humans.

On every invocation:

  1. Infer the intended mode and operation from $ARGUMENTS + conversation.
  2. Ask a blocking question only when two interpretations would materially change the chart, cost, or consent boundary.
  3. Read back any state-changing interpretation before persisting.
  4. Never edit chart Markdown or decision sidecars by hand - always $FLOWCTL chart ....

Modes (disambiguate by argument)

Invocation shapeModeBehavior
free-form idea / "chart out ..."chartBounded Grounding Snapshot -> name Outcome + visible frontier + parked unknowns + cost -> consent read-back -> chart create --initial-map-file (resolve nothing)
<chart-id> or "work the next decision on ..."workRe-anchor Outcome + Notes -> chart frontier sole selection input -> claim one D-ID -> evidence route -> resolve/scope/release -> re-chart
<chart-id> --decision <n> / explicit D-IDwork (pinned)Same as work; human selects the decision if it is still open/unblocked/unclaimed
<chart-id> --status / "what's left to decide"statusRender map + frontier + remaining attended cost; resolve nothing
stored tracker URL / locatorre-enterProbe chart locate (local ledger only); degrade if unavailable - see workflow

Plain-language equivalents reach the same modes.

Verdict grammar (exact)

Every work invocation ends with exactly one greppable line and nothing after it:

CHART_VERDICT=<RESOLVED|BLOCKED|NEEDS_HUMAN|COMPLETE|NO_WORK> chart=<id> decision=<D> reason="<one line>"
VerdictWhen
RESOLVEDOne D-ID closed via resolve or out-of-scope; frontier recomputed
BLOCKEDClaim conflict, graph/store refusal, or no actionable path without human repair
NEEDS_HUMANStored attendance:attended decision reached by an unattended driver - no answer write
COMPLETEChart briefable (no open decisions, no parked questions) after this tick, or briefing emitted
NO_WORKEmpty frontier, skip-chart (no consequential unknowns), status-only, or chart mode finished without resolving

Chart mode and status mode also print one terminal line so host /loop//goal drivers can parse uniformly (decision=- when no D-ID was claimed).

Unattended driver signals (any one): non-empty FLOW_AUTONOMOUS, or the host is driving without a human present. Interactive terminal sessions are attended.

Decision types = evidence routes

TypeAttendanceResolves by
researchunattendedScout reads docs / primary sources / knowledge bases; returns a fact
probeunattendedMeasure or reproduce against the real system
evalunattendedBake-off / benchmark on real fixtures; winner + why
prototypeattendedThrowaway artefact + human reaction (hard gate)
interviewattendedConversation (default for product judgment)
taskexplicit at createManual work that only unblocks a decision (not implementation smuggling)

Attendance is stored and validated by flowctl for five types; task requires --attendance attended|unattended. Cost estimates and unattended gates read the stored field, never prose.

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

Invariants (hard)

  • One invocation = one D-ID = one claim = one verdict. Independent unattended frontier decisions fan out only as separate invocations. No batch or mixed-result grammar.
  • Charting resolves nothing. Chart mode ends after map + first decision records + cost exist.
  • flowctl chart frontier is the sole selection input for work mode (optional human pin still must appear on that frontier).
  • Claim before any work. Refuse double-claim; release with note on stop; crash leaves claim visible.
  • Attended hard gate. Unattended driver + attendance:attended -> persist no answer, release or leave claim per workflow, terminate NEEDS_HUMAN.
  • Prototype lifecycle. Create/import one scoped throwaway artefact -> chart attach-asset while open -> present exact safe reference/revision -> record human reaction -> resolve/supersede. Interruption leaves asset + open D-ID resumable. Never rebuild, never infer approval, never promote prototype code into implementation.
  • No nameable destination -> STOP. Chart's premise is destination known, route unknown. A theme or direction ("make X more Y") has no end state to state as an Outcome and no boundary to rule anything out of scope. Offer narrowing to one effort with a stateable end state, or /flow-next:prospect when the real ask is which effort to pick; create nothing.
  • No consequential unknowns -> STOP. Recommend /flow-next:capture or the smaller direct route; create nothing.
  • Over chart.maxDecisions (default 12). Offer narrow Outcome or split first. Pass --force-size --reason only after explicit warning + consent read-back.
  • Provenance lanes stay separate. Grounding facts get citations under ## Notes and never become D-IDs or acceptance-criterion trailing tags ([user] / [paraphrase] / [inferred] / [strategy:*]). Include NO verified/inferred fact grammar.
  • Unsafe evidence by reference. Never embed secrets or literal destructive shell command strings in chart artefacts; store a safe redacted summary + approved path/HTTPS reference. Describe such operations in prose only.
  • Context discipline. Status/frontier navigation loads compact metadata only. Full decision bodies and assets load only for the selected D-ID or briefing.
  • Skill never edits Open Questions, edges, or sharpened decisions directly. Use park/remove/wire/resolve --sharpen-file / create --initial-map-file.

Flags (automation only - not required vocabulary)

Documented for scripting; the full flag table, the human-intent -> flowctl map, and conversational equivalents live in references/examples.md. Only --status (status mode) and --decision <n> (pin a D-ID for work mode) affect routing; --json is available on every flowctl chart subcommand.

Workflow

Execute workflow.md:

  1. Route - parse args, probe locator for URL-like selectors, choose mode.
  2. Mode dispatch - read only the routed mode's reference:
    • Chart mode - Grounding Snapshot (ordered) -> read-back Outcome/frontier/cost -> create or stop.
    • Work mode - re-anchor -> frontier -> claim -> evidence route -> resolve/scope/release -> sharpen -> re-chart -> one verdict; supersession when steering says the direction changed.
    • Briefing handoff / reopen - when briefable, propose clusters, confirm, briefing --proposal-file, hand to capture.
  3. Status mode - compact show + frontier + cost; no mutations (inline in workflow.md).

Forbidden

  • Writing under .flow/specs/ or mutating a spec's ready flag.
  • Answering attended decisions without the human side of the exchange.
  • Turning imported background into fabricated resolved D-IDs or acceptance-criterion tags.
  • Shipping verified/inferred fact grammar (not a shipped feature).
  • Precomputing a complete discovery route or treating adaptive traces as mandatory phases.
  • Embedding literal destructive shell command strings or realistic secrets in chart bodies, answers, briefings, or this skill's examples.
  • Silent claim expiry, silent supersession cascade, or silent prototype-to-implementation promotion.
  • Setting context: fork (blocking questions must stay reachable).

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

  • SKILL.md
  • references/briefing-and-reopen.md
  • references/chart-mode.md
  • references/examples.md
  • references/re-entry.md
  • references/tracker-projection.md
  • references/work-mode.md
  • workflow.md

Open the folder on GitHubat commit 09e291e

Compare with similar skills

Flow Next Chart 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 Chart compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Flow Next Chart this skillgmickel/flow-next709—~2.6kAutomated safety check: NotesMIT
Chart Visualizationbytedance/deer-flow84k2 repos~840Automated safety check: PassMIT
Idea Ossickn33/agentic-awesome-skills47k1 repos~1.5kAutomated safety check: PassMIT
Token Mapnexu-io/open-design100k—~1.4kAutomated safety check: PassApache-2.0
Maps Geographyasgeirtj/system_prompts_leaks69k—~717Automated safety check: PassCC0-1.0
Idea Darwinsickn33/agentic-awesome-skills47k2 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Chart Visualization

    bytedance/deer-flow

    Picks a suitable chart type from 26 options for your data, maps the data to that chart's parameters and generates a chart image through a JavaScript script.

    84k GitHub starsUsed in 2 repos~840 tokens
    Data & AnalyticsAuto-check passed

  • Idea Os

    sickn33/agentic-awesome-skills

    Five-phase pipeline (triage → clarify → research → PRD → plan) that turns a raw idea into four linked files: clarifying questions, deep research, a PRD with non-goals and metrics, and a phased…

    47k GitHub starsUsed in 1 repo~1.5k tokens
    Product & Project ManagementAuto-check passed

  • Token Map

    nexu-io/open-design

    Map an extracted Figma / source-code token bag onto the active OD design system, producing a deterministic mapping the generate stage can consume.

    100k GitHub stars~1.4k tokensUpdated today
    Frontend & DesignAuto-check passed

  • Maps Geography

    asgeirtj/system_prompts_leaks

    Accurate maps from real geo data — use for any map, or whenever geography would make a good graphic for a deliverable

    69k GitHub stars~717 tokensUpdated yesterday
    Auto-check passed

  • Idea Darwin

    sickn33/agentic-awesome-skills

    Darwinian idea evolution engine — toss rough ideas onto an evolution island, let them compete, crossbreed, and mutate through structured rounds to surface your strongest concepts.

    47k GitHub starsUsed in 2 repos~1.1k tokens
    Auto-check passed

  • Working With Charts

    PostHog/posthog

    Official

    Guides consumers of @posthog/quill-charts through chart selection, data, themes, sizing, and composition.

    40k GitHub stars~948 tokensUpdated today
    Data & AnalyticsAuto-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

Questions about Flow Next Chart

What does Flow Next Chart do?

Decision-map discovery for one oversized/unclear idea before capture. Flow Next Chart is an agent skill from gmickel/flow-next. Decision-map discovery for one oversized/unclear idea before capture.

When should I use Flow Next Chart?

Flow Next Chart fits situations like: /flow-next:chart with an unshaped idea; stored tracker URL.

How do I install Flow Next Chart in Claude Code?

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

How do I install Flow Next Chart in Codex?

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

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

What does Flow Next Chart need to run?

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

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

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

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

What are the alternatives to Flow Next Chart?

Skills that share tags, products or a category with Flow Next Chart: Chart Visualization (bytedance/deer-flow, 84k stars), Idea Os (sickn33/agentic-awesome-skills, 47k stars), Token Map (nexu-io/open-design, 100k stars) and Maps Geography (asgeirtj/system_prompts_leaks, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Flow Next Chart?

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.