Skip to main content
command CX Codex

chart — Claude Code command: decision map before capture

chart turns one oversized or fuzzy idea into a decision map. Each run settles a single decision and leaves a brief you can capture as a task.

MIT ★ 730 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add gmickel/flow-next
/plugin install flow-next@flow-next
Open on GitHub

What chart does

The command is thin on purpose. All it does is pass your arguments to the flow-next-chart skill, which then picks the mode: charting, working the chart, reporting status, or re-entering from a tracker link.

One decision per invocation. Grounding against project context comes first, chart edits go through flowctl, and the skill stops at the gates that need a person. The run ends with a CHART_VERDICT= line. Arguments take a plain idea, a <chart-id> with --decision <n> or --status, or a <tracker-url>.

Because the frontmatter sets disable-model-invocation: true, the model cannot start this by itself — you do. On Claude the command file sits at .claude/commands/chart.md; on Codex it goes to ~/.codex/prompts/chart.md.

What it helps with

  • split a vague idea into decisions before writing a task
  • settle one decision per run instead of drowning in a backlog
  • resume a chart by <chart-id> where you stopped
  • check chart status without opening the tracker
  • get a brief that turns into a captured task

Example prompts for the agent

  • /chart Take the “live in-app notifications” idea and map the decisions it hides.
  • /chart chart-3 --decision 2 — show that decision and record the call.
  • /chart chart-3 --status — where did we leave off?

How to install chart

1Plugin marketplace

/plugin marketplace add gmickel/flow-next
/plugin install flow-next@flow-next

2Manually: put the files in place

.claude/commands/chart.md

Call it with /chart. For all projects use ~/.claude/commands/

Questions about chart

How do I install chart in Claude Code?

Run /plugin marketplace add gmickel/flow-next, then /plugin install flow-next@flow-next. The command file lands at .claude/commands/chart.md.

What does chart do?

It maps one large or unclear idea into decisions and settles a single decision per run. The run ends with a brief you can turn into a captured task.

Can the agent invoke chart on its own?

No. disable-model-invocation: true is set in the frontmatter, so the command is started by hand.

Source text

chart.md · MIT
---
name: chart
description: Decision-map discovery for one oversized/unclear idea before capture - ground, chart a frontier, resolve one decision per invocation, brief for capture
argument-hint: "[idea | <chart-id> [--decision <n>] [--status] | <tracker-url>]"
disable-model-invocation: true
---

# IMPORTANT: This command MUST invoke the skill `flow-next-chart`

The ONLY purpose of this command is to call the `flow-next-chart` skill. You MUST use that skill now.

**Arguments:** $ARGUMENTS

Pass the arguments to the skill. The skill handles mode detection (chart / work / status / locator re-entry), bounded grounding, prompt-first operation inference, flowctl chart mutations, attended gates, and the terminal `CHART_VERDICT=` line.

© Gordon Mickel · MIT · gmickel/flow-next

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

From the same set70

The whole set →
audit The audit command checks .flow/memory/ entries against the current code and assigns an action to each one. Use it when project notes may need revision. CX Codex +1 ★ 730repo stars map A slash command that hands off to the flow-next-map skill to build a semantic feature index of your repository with clawpatch, provider-free by default. CX Codex +1 ★ 730repo stars memory-migrate memory-migrate — a command for Claude Code and Codex that converts legacy flat memory files (pitfalls.md, conventions.md, decisions.md) into a structured YAML schema with automatic entry classification. CX Codex +1 ★ 730repo stars make-pr This command hands PR preparation to the flow-next-make-pr skill, which renders a PR body and opens it through gh. Choose a draft, base ref, or dry run with flags. CX Codex +1 ★ 730repo stars capture capture synthesizes the active conversation into a flow-next spec at .flow/specs/<spec-id>.md with review checks and overwrite protection. CX Codex +1 ★ 730repo stars tracker-sync tracker-sync projects a flow spec into Linear, GitHub, GitLab, or Jira, then reconciles issue body, status, and comments in both directions. CX Codex +1 ★ 730repo stars flow-next-setup flow-next-setup links a repo to the flow-next plugin: adds versioned docs and config to CLAUDE.md or AGENTS.md. Other agents, such as Codex or Cursor, can then read the same instructions. CX Codex +1 ★ 730repo stars flow The flow command drives a task from idea or bug to ready PR. Works for unattended runs on a ready spec or step-by-step with stops before decisions. CX Codex +1 ★ 730repo stars

Project sponsors

Companies that keep this analytics open