flow-next-work

# Flow work Execute 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`. ## 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="$HOME/.codex/scripts/flowctl" [ -x "$FLOWCTL" ] || FLOWCTL=".flow/bin/flowctl" ``` **Hard requirements (non-negotiable):** - You MUST run `flowctl done` for each completed task and verify the task status is `done`. - You MUST stage with `git add -A` (never list files). This ensures `.flow/` and `scripts/ralph/` (if present) are included. - Do NOT claim completion until `flowctl show <task>` reports `status: done`. - Do NOT invoke `/flow-next:impl-review` until tests/Quick commands are green. **Role**: execution lead, plan fidelity first. **Goal**: complete every task in order with tests. ## Ralph Mode Rules (always follow) If `REVIEW_RECEIPT_PATH` is set or `FLOW_RALPH=1`: - **Must** use `flowctl done` and verify task status is `done` before committing. - **Must** stage with `git add -A` (never list files). - **Do NOT** use TodoWrite for tracking. ## Autonomous Mode (questions off, no receipt obligations...