Execute a Flow epic or task systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan or working through a spec. Triggers on /flow-next:work with Flow IDs (fn-1, fn-1.2).
/plugin marketplace add gmickel/gmickel-claude-marketplace/plugin install flow-next@gmickel-claude-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
phases.mdExecute a plan systematically. Focus on finishing.
Follow this skill and linked workflows exactly. Deviations cause drift, bad gates, retries, and user frustration.
IMPORTANT: This plugin uses .flow/ for ALL task tracking. Do NOT use markdown TODOs, plan files, TodoWrite, or other tracking methods. All task state must be read and written via flowctl.
CRITICAL: flowctl is BUNDLED — NOT installed globally. which flowctl will fail (expected). Always use:
FLOWCTL="${CLAUDE_PLUGIN_ROOT}/scripts/flowctl"
$FLOWCTL <command>
Hard requirements (non-negotiable):
flowctl done for each completed task and verify the task status is done.git add -A (never list files). This ensures .flow/ and scripts/ralph/ (if present) are included.flowctl show <task> reports status: done./flow-next:impl-review until tests/Quick commands are green.Role: execution lead, plan fidelity first. Goal: complete every task in order with tests.
If REVIEW_RECEIPT_PATH is set or FLOW_RALPH=1:
flowctl done and verify task status is done before committing.git add -A (never list files).Full request: $ARGUMENTS
Accepts:
fn-N to work through all tasksfn-N.M to work on single taskExamples:
/flow-next:work fn-1/flow-next:work fn-1.3/flow-next:work Add rate limiting/flow-next:work fn-1 then review via /flow-next:impl-reviewIf no input provided, ask for it.
Check if rp-cli available: which rp-cli >/dev/null 2>&1
Parse the arguments for these patterns. If found, use them and skip corresponding questions:
Branch mode:
--branch=current or --current or "current branch" or "stay on this branch" → current branch--branch=new or --new-branch or "new branch" or "create branch" → new branch--branch=worktree or --worktree or "isolated worktree" or "worktree" → isolated worktreeReview mode (only if rp-cli available):
--review=rp or "review with rp" or "rp chat" or "repoprompt review" → RepoPrompt chat (via flowctl rp chat-send)--review=export or "export review" or "external llm" → export for external LLM--review=none or --no-review or "no review" or "skip review" → no reviewIf rp-cli available, output these questions as text (do NOT use AskUserQuestion tool):
Quick setup before starting:
1. **Branch** — Where to work?
a) Current branch
b) New branch
c) Isolated worktree
2. **Review** — Run Carmack-level review after?
a) Yes, RepoPrompt chat (`flowctl rp chat-send`)
b) Yes, export for external LLM (ChatGPT, Claude web)
c) No
(Reply: "1a 2a", "current branch, export review", or just tell me naturally)
If rp-cli NOT available, ask only branch:
Quick setup: Where to work?
a) Current branch b) New branch c) Isolated worktree
(Reply: "a", "current", or just tell me)
Wait for response. Parse naturally — user may reply terse or ramble via voice.
Defaults when empty/ambiguous (rp-cli available):
newrpDefaults when rp-cli NOT available:
newnoneDo NOT read files or write code until user responds.
After setup questions answered, read phases.md and execute each phase in order. If user chose review:
/flow-next:impl-review after Phase 6, fix issues until it passes/flow-next:impl-review with export mode after Phase 6.flow/Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.