Przejdź do treści
Biblioteka skilli
Programowanie · Budowanie i kod

flow-next-work

/flow-next-work

Wykonuje specyfikację lub zadanie Flow krok po kroku: git, śledzenie zadań, kontrolę jakości i commity.

Licencja
MIT
Ostatnia zmiana repozytorium
13.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
32
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Wykonuje specyfikację lub zadanie Flow krok po kroku: git, śledzenie zadań, kontrolę jakości i commity.

Oryginalny opis (EN)

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).

Jak działa

  1. Preamble
  2. Autonomous Mode (questions off, no receipt obligations)
  3. Input
  4. FIRST: Parse Options
  5. Workflow
  6. Guardrails
Sekcje z nagłówków SKILL.md, w oryginale · 114 linii, 972 słów
Podgląd SKILL.md
---
name: flow-next-work
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).
user-invocable: false
---

# 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>

Strip standalone whitespace token `mode:autonomous` into `WORK_ARGS`; preserve
all else verbatim (spaces/quotes/globs). Set/export `AUTONOMOUS=1` if found or
`FLOW_AUTONOMOUS=1`; otherwise set/export `AUTONOMOUS=0`.

Continue with `WORK_ARGS`; carry the exported marker into later shell fragments.
If `AUTONOMOUS=1`: read [references/autonomous-defaults.md](references/autonomous-defaults.md)
before any question, and:

- **Branch defaults deterministically to `--branch=new`** when no explicit branch option is present — under autonomy "the user's answer" never exists, and defaulting to the current branch could commit straight to main. A chained spec (`flowctl spec chain` names a parent) forks from the parent's remote tip instead of main (phases.md Phase 2). **Name the new branch exactly the spec's `branch_name` field** (`$FLOWCTL show <spec-id> --json | jq -r '.branch_name'`) — the branch matrix of `flow --auto`, its all-done PR probe, and make-pr's branch-match spec detection all key on that name; an ad-hoc name breaks continuity across hops and invocations.

## Input

Full request after mode parsing: `$WORK_ARGS`

Accepts:
- Flow spec ID `fn-N-slug` (e.g., `fn-1-add-oauth`) or legacy `fn-N`/`fn-N-xxx` to work through all tasks
- Flow task ID `fn-N-slug.M` (e.g., `fn-1-add-oauth.2`) or legacy `fn-N.M`/`fn-N-xxx.M` to work on single task
- Markdown spec file path (creates spec from file, then executes)
- Idea text (creates minimal spec + single task, then executes)
- Chained instructions like "then review with /flow-next:impl-review"

If no input provided, ask for it.

## FIRST: Parse Options

### Option Parsing (skip questions if found in arguments)

Parse `WORK_ARGS` 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 worktree

**Base**: `--base=<branch>` or `--base <branch>` → `DEFAULT_BASE=origin/<branch>` (a leading
`origin/` is kept once), the branch a new spec branch starts from and the run is compared against
(phases.md Phase 2); an unfetchable branch, or a spec with a chain parent, stops `BLOCKED` there,
before any branch is created.

**Review mode**:
- `--review=<codex|copilot|cursor|claude|host|none>`, or the same backend named in words
  ("review with codex", "host review", "skip review"); `--no-review` = `none`

(All non-`none` review modes route through `flow-next:flow-next-impl-review`, which resolves the
configured/overridden backend — codex, copilot, cursor, claude, or host — itself.)

**No-plan (direct spec execution)**:
- `--no-plan` or "no plan" or "skip planning" or "work directly without planning" → set `NO_PLAN=1`; it pre-answers Phase 1's zero-task fork so the fork's ask never fires when intent is stated
- Implementation review, coverage, completion policy and opt-in QA remain unchanged on this route.
- The fork's semantics (ask, autonomous refusal, durable choice, implicit-task mint) live in phases.md Phase 1's gated [references/no-plan-route.md](references/no-plan-route.md), read only when the fork fires

**Autonomous mode**:
- `AUTONOMOUS=1` → use the defaults above.

### If the options are absent from the arguments

**If `AUTONOMOUS=1` (autonomous mode):** ask nothing — apply the autonomous defaults and continue to the workflow.

**Otherwise (interactive)**: do not ask about the branch. Stay on the current branch when it is
not the default branch, otherwise create a new one (named for the spec's `branch_name`), and say
which in one line. Never ask about review either: the review step resolves the backend per task
(phases.md Phase 3).

Done when: the branch and review modes are resolved from arguments, these defaults, or the
autonomous defaults.

## Workflow

Read [working-rules.md](../../references/working-rules.md) first unless you already have this run; it holds on every phase and in every worker dispatch.

Once the modes are resolved, read [phases.md](phases.md) and execute each phase in order.

## Guardrails

- **The branch is chosen before the run starts.** A run that began on an unresolved branch choice has broken this.
- **A plan or spec exists before implementation starts.** A run that began with no `.flow/` spec has broken this.
- **Tests run.** A task marked done before the focused tests for the code it changed ran has broken this.
- **No task is left half-done.** A run that ends with a task still `in_progress` and no `NEEDS_HUMAN`/blocked report has broken this.
- **Task tracking lives in `.flow/` via `flowctl`.** A run tracking tasks in TodoWrite, or writing a plan file outside `.flow/`, has broken this.
Pliki w paczce (32)
  • SKILL.md 7 KB
  • phases.md 23 KB
  • references/autonomous-defaults.md 1 KB
  • references/chained-spec.md 1 KB
  • references/defect-bisect.md 1 KB
  • references/defect-live-surface.md 1 KB
  • references/defect-route.md 7 KB
  • references/direct-owner-resume.md 1 KB
  • references/feature-map-prove.md 3 KB
  • references/feature-map-update.md 2 KB
  • references/full-gate-receipts.md 1 KB
  • references/hill-climb.md 8 KB
  • references/host-deferred-review.md 5 KB
  • references/judge-tier.md 4 KB
  • references/minted-task-dispatch.md 3 KB
  • references/multi-repo-base.md 1 KB
  • references/multi-task.md 33 KB
  • references/no-plan-ask.md 3 KB
  • references/no-plan-route.md 4 KB
  • references/plan-sync-dispatch.md 3 KB
  • references/quality-auditor.md 2 KB
  • references/rolling-scheduler.md 25 KB
  • references/spec-id-mint.md 3 KB
  • references/spec-less-start.md 1 KB
  • references/tracker-retro-fire.md 2 KB
  • references/tracker-touchpoints.md 11 KB
  • references/wave-join.md 8 KB
  • references/worker-baseline-reuse.md 1 KB
  • references/worker-bridge.md 7 KB
  • references/worker-design-context.md 1 KB
  • references/worker-handover.md 6 KB
  • references/worker-memory-capture.md 4 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · gmickel/gmickel-claude-marketplace100MIT
gmickel/flow-next100MIT

Migawka bazy z 13.11.2026 · wersja paczki ecea3b9cb01f (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100flux-work
    Realizuje epik lub zadanie Flow krok po kroku: konfiguruje git, śledzi zadania, uruchamia kontrole jakości i prowadzi proces commitów.
  • 95flow-next-plan
    Rozbija specyfikację lub pomysł na przejrzane zadania i uruchamia się na prośbę o plan lub podział zadań.
  • 95flow-next-plan
    Tworzy ustrukturyzowany plan budowy z opisu funkcji lub identyfikatora Flow, gdy planuje się nową funkcjonalność.
  • 100flux-plan
    Tworzy uporządkowane plany implementacji na podstawie opisu funkcji, poprawki błędu, aktualizacji lub refaktoryzacji albo identyfikatorów Flow.
  • 95flow-next-plan
    Rozpisuje funkcję na specyfikację i zadania w katalogu .flow, gdy trzeba zaplanować lub rozbić pracę na identyfikatory fn-N.
  • 100flow-next-spec-completion-review
    Sprawdza, czy wszystkie zadania specyfikacji Flow realizują wymagania ze specyfikacji.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.