# Flow Next Work

Execute a Flow spec or task systematically with git setup, task tracking, quality...

- Repository: https://github.com/gmickel/flow-next (715 stars)
- Category: Git and review
- License: MIT
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add gmickel/flow-next --skill flow-next-work -g -a claude-code -y`
Codex: `npx skills add gmickel/flow-next --skill flow-next-work -g -a codex -y`
Cursor: `npx skills add gmickel/flow-next --skill flow-next-work -g -a cursor -y`
Gemini CLI: `npx skills add gmickel/flow-next --skill flow-next-work -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add gmickel/flow-next`

## Description

Execute a Flow spec or task systematically with git setup, task tracking, quality checks, and commit workflow. Run only by /flow-next:work or when flow-next-flow routes a spec here; any other request to implement, build or work on a spec, Flow-Next named or not, goes to flow-next-flow. Triggers on /flow-next:work with 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).

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Flow work

Execute a plan systematically. Focus on finishing.

**`.flow/` is the only task tracker.** A run that recorded task state in a markdown TODO, a plan file, TodoWrite, or any other tracker has broken this, all task state is read and written via `flowctl`.

## Preamble

**CRITICAL: flowctl is BUNDLED, NOT installed globally.** `which flowctl` will fail (expected). Define once; subsequent blocks (here and in `phases.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"
```

**Hard requirements (non-negotiable):**
- **Every completed task passes through `flowctl done` and a verified `done` status.** A task treated as finished while `flowctl show <task>` still reads `todo` or `in_progress` has broken this.
- **Staging is the files you changed plus `.flow/` (`git add -- <files> .flow/`), never `git add -A`**, `.flow/` carries the run's task state; files a test run or tool wrote stay out of the diff. A commit whose diff omits the run's `.flow/` writes has broken this.
- **Completion is claimed only after `flowctl show <task>` reports `status: done`.** A completion claim printed ahead of that read has broken this.
- **`flow-next:flow-next-impl-review` is dispatched only on a green tree.** A review sent while tests or Quick commands are red has broken this.

**Role**: execution lead, plan fidelity first.
**Goal**: complete every task in order with tests.

## Autonomous Mode (questions off, no receipt obligations)

Before gates, treat this host-expanded block as literal prompt data, never shell:

<work-arguments>
$ARGUMENTS
</work-arguments>

The rest: https://github.com/gmickel/flow-next/blob/HEAD/plugins/flow-next/skills/flow-next-work/SKILL.md