# All Skills

Source: https://flow-next.dev/skills/

Every flow-next skill in one grid, grouped by pipeline stage - shape, plan, build, ship, autonomy, teams, maintenance, workspace.

Every flow-next skill, grouped by where it sits in the [pipeline](https://flow-next.dev/understand/pipeline/). Use the smallest sufficient workflow: each skill runs standalone, and the stages compose in any order the work needs.

**The `Invocation` column shows the canonical form. You do not have to type it** - every skill is triggered by describing what you want, and every flag has a plain-language equivalent (the [cookbook](https://flow-next.dev/guides/cookbook/#say-it-in-plain-language) shows the pairs). Say “make a spec from what we discussed” and capture runs; the command is just the precise version.

## Shape the work

| Skill                                                | Invocation             | What it does                                                                                                      |
| ---------------------------------------------------- | ---------------------- | ----------------------------------------------------------------------------------------------------------------- |
| [Strategy](https://flow-next.dev/skills/strategy/)   | `/flow-next:strategy`  | Create and maintain `STRATEGY.md` - the product anchor downstream skills read for grounding.                      |
| [Guide](https://flow-next.dev/skills/guide/)         | `/flow-next:guide`     | Stateless router - recommends the smallest sufficient next workflow from your starting state.                     |
| [Prospect](https://flow-next.dev/skills/prospect/)   | `/flow-next:prospect`  | Generate ranked candidate ideas grounded in the repo, upstream of planning.                                       |
| [Chart](https://flow-next.dev/skills/chart/)         | `/flow-next:chart`     | Optional decision-map discovery for one oversized unclear idea before capture - one D-ID at a time, briefing out. |
| [Capture](https://flow-next.dev/skills/capture/)     | `/flow-next:capture`   | Synthesize a conversation into a spec with source-tagged R-IDs and mandatory read-back.                           |
| [Interview](https://flow-next.dev/skills/interview/) | `/flow-next:interview` | Refine a spec via symmetric Q\&A - business and technical passes, append-only R-IDs.                              |

## Plan

| Skill                                                    | Invocation               | What it does                                                                                                |
| -------------------------------------------------------- | ------------------------ | ----------------------------------------------------------------------------------------------------------- |
| [Plan](https://flow-next.dev/skills/plan/)               | `/flow-next:plan`        | Research scouts in parallel; a structured plan with R-ID coverage; tasks sized for one work-loop iteration. |
| [Plan Review](https://flow-next.dev/skills/plan-review/) | `/flow-next:plan-review` | Carmack-level adversarial review of a spec before any work starts.                                          |
| [Deps](https://flow-next.dev/skills/deps/)               | `/flow-next:deps`        | Show the spec dependency graph, execution order, and parallelizable phases.                                 |
| [Sync](https://flow-next.dev/skills/sync/)               | `/flow-next:sync`        | Manually trigger plan-sync to update downstream task specs after implementation drift.                      |

## Build

| Skill                                                    | Invocation               | What it does                                                                                |
| -------------------------------------------------------- | ------------------------ | ------------------------------------------------------------------------------------------- |
| [Work](https://flow-next.dev/skills/work/)               | `/flow-next:work`        | Execute a spec - worker subagent per task, re-anchor every iteration, plan-sync after each. |
| [Impl Review](https://flow-next.dev/skills/impl-review/) | `/flow-next:impl-review` | Carmack-level cross-model review of the implementation diff, with a fix loop until SHIP.    |
| [QA](https://flow-next.dev/skills/qa/)                   | `/flow-next:qa`          | Live-app QA pass that drives the running app and derives its scenarios from the spec.       |

## Ship

| Skill                                                                          | Invocation                          | What it does                                                                                   |
| ------------------------------------------------------------------------------ | ----------------------------------- | ---------------------------------------------------------------------------------------------- |
| [Make PR](https://flow-next.dev/skills/make-pr/)                               | `/flow-next:make-pr`                | Render a cognitive-aid PR body - R-ID coverage table, critical changes, decision context.      |
| [Resolve PR](https://flow-next.dev/skills/resolve-pr/)                         | `/flow-next:resolve-pr`             | Resolve PR review feedback - fetch threads, triage, dispatch resolver agents, reply + resolve. |
| [Spec Completion Review](https://flow-next.dev/skills/spec-completion-review/) | `/flow-next:spec-completion-review` | Verify the combined implementation of all tasks satisfies the spec requirements.               |

## Autonomy loops

| Skill                                               | Invocation              | What it does                                                                                            |
| --------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------- |
| [Pilot](https://flow-next.dev/skills/pilot/)        | `/flow-next:pilot`      | The build loop - one ready spec, one pipeline stage per tick, driven by your host’s `/loop` or `/goal`. |
| [Land](https://flow-next.dev/autonomy/land/)        | `/flow-next:land`       | The ship loop - babysits the build loop’s draft PRs through CI, review convergence, merge, and release. |
| [Ralph Init](https://flow-next.dev/autonomy/ralph/) | `/flow-next:ralph-init` | Scaffold the hardened Ralph harness - fresh session per iteration, hook-enforced guardrails.            |

## Teams & trackers

| Skill                                                            | Invocation                | What it does                                                                                                  |
| ---------------------------------------------------------------- | ------------------------- | ------------------------------------------------------------------------------------------------------------- |
| [Tracker Sync](https://flow-next.dev/integrations/tracker-sync/) | `/flow-next:tracker-sync` | Project a spec to Linear, GitHub, GitLab, or Jira and reconcile two-way - the spec stays the source of truth. |

## Repo & memory maintenance

| Skill                                                          | Invocation                  | What it does                                                                                                                             |
| -------------------------------------------------------------- | --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| [Setup](https://flow-next.dev/skills/setup/)                   | `/flow-next:setup`          | Optional local install of flowctl plus `CLAUDE.md` / `AGENTS.md` instructions.                                                           |
| [Prime](https://flow-next.dev/skills/prime/)                   | `/flow-next:prime`          | Opinionated agent-readiness assessment - verdict first, ranked next-actions.                                                             |
| [Audit](https://flow-next.dev/skills/audit/)                   | `/flow-next:audit`          | Review `.flow/memory/` against the current codebase - Keep / Update / Consolidate / Replace / Delete / Harden per entry.                 |
| [Features](https://flow-next.dev/skills/features/)             | `/flow-next:features`       | Seed and maintain the committed user-POV feature map - how a user reaches each feature, how an agent drives it, which traps waste a run. |
| [Map](https://flow-next.dev/skills/map/)                       | `/flow-next:map`            | Semantic feature index of the repo (wraps clawpatch) - opt-in convenience consumed by scouts.                                            |
| [Memory Migrate](https://flow-next.dev/skills/memory-migrate/) | `/flow-next:memory-migrate` | Lift legacy flat memory files into the categorized YAML schema.                                                                          |

## Workspace & utilities

| Skill                                                          | Invocation           | What it does                                                                                                                                                 |
| -------------------------------------------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| [Visual](https://flow-next.dev/skills/visual/)                 | `/flow-next:visual`  | Restate a spec, task, diff, or the current topic as a compact markdown digest - the light register below the HTML lenses.                                    |
| [Prose](https://flow-next.dev/skills/prose/)                   | `/flow-next:prose`   | Apply the shipped artifact prose contract to a substantial reply or draft - the same ten rules PR bodies, specs, and tracker comments already draft against. |
| [Worktree Kit](https://flow-next.dev/skills/worktree-kit/)     | dispatched on demand | Manage git worktrees for parallel feature work, isolated review, and clean workspaces.                                                                       |
| [Export Context](https://flow-next.dev/skills/export-context/) | dispatched on demand | Export a review prompt for external LLMs (ChatGPT Pro, Claude web, Gemini).                                                                                  |
| [Tasks & Inventory](https://flow-next.dev/skills/flow-next/)   | conversational       | ”Show me my tasks” - conversational access to specs and tasks in `.flow/`.                                                                                   |
| [Drive](https://flow-next.dev/skills/flow-next-drive/)         | dispatched by QA     | Surface-aware UI automation - picks the best available driver per surface, degrading gracefully.                                                             |

## Spec ids in commands

Every command that takes a spec or task id accepts **either** id scheme. The default form is `fn-NN` (`/flow-next:work fn-1`, `/flow-next:plan fn-1.2`). A spec linked to a tracker is referenced by its tracker key instead: `/flow-next:work wor-17`, `/flow-next:plan wor-17`, tasks as `wor-17.1`, resolution case-insensitive. See [Spec and task ids](https://flow-next.dev/reference/spec-schema/#spec-and-task-ids).

## How the stages connect

```mermaid
flowchart LR
  Strategy["strategy/prospect"] --> Guide{"clear enough?"}
  Guide -->|yes| Capture["capture/interview"]
  Guide -->|optional chart| Chart["chart → briefing"]
  Chart --> Capture
  Capture --> Plan["plan"]
  Plan --> PlanReview["plan-review (optional)"]
  PlanReview --> Work["work"]
  Work --> Impl["impl-review (optional)"]
  Impl --> Completion["spec-completion-review"]
  Completion --> PR["make-pr"]
  PR --> Resolve["resolve-pr"]
```

`plan` produces both the spec (with R-IDs) and the task breakdown, and `plan-review` reviews both before any code is written. `impl-review` checks the resulting diff. `spec-completion-review` is the final gate that confirms every R-ID has evidence in the combined implementation. Those are the three review scopes, and they do not substitute for each other.

Most people should not start with `flowctl`. Slash commands are the product workflow; `flowctl` is the deterministic state layer those commands call.

Skills are the judgment layer; the mechanical substrate is the [flowctl CLI](https://flow-next.dev/flowctl/cli-reference/), which every skill calls for state, receipts, and validation.
