Every flow-next skill, grouped by where it sits in the 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 shows the pairs). Say “make a spec from what we discussed” and capture runs; the command is just the precise version.
| Skill | Invocation | What it does |
|---|
| Strategy | /flow-next:strategy | Create and maintain STRATEGY.md - the product anchor downstream skills read for grounding. |
| Guide | /flow-next:guide | Stateless router - recommends the smallest sufficient next workflow from your starting state. |
| Prospect | /flow-next:prospect | Generate ranked candidate ideas grounded in the repo, upstream of planning. |
| Chart | /flow-next:chart | Optional decision-map discovery for one oversized unclear idea before capture - one D-ID at a time, briefing out. |
| Capture | /flow-next:capture | Synthesize a conversation into a spec with source-tagged R-IDs and mandatory read-back. |
| Interview | /flow-next:interview | Refine a spec via symmetric Q&A - business and technical passes, append-only R-IDs. |
| Skill | Invocation | What it does |
|---|
| Plan | /flow-next:plan | Research scouts in parallel; a structured plan with R-ID coverage; tasks sized for one work-loop iteration. |
| Plan Review | /flow-next:plan-review | Carmack-level adversarial review of a spec before any work starts. |
| Deps | /flow-next:deps | Show the spec dependency graph, execution order, and parallelizable phases. |
| Sync | /flow-next:sync | Manually trigger plan-sync to update downstream task specs after implementation drift. |
| Skill | Invocation | What it does |
|---|
| Work | /flow-next:work | Execute a spec - worker subagent per task, re-anchor every iteration, plan-sync after each. |
| Impl Review | /flow-next:impl-review | Carmack-level cross-model review of the implementation diff, with a fix loop until SHIP. |
| QA | /flow-next:qa | Live-app QA pass that drives the running app and derives its scenarios from the spec. |
| Skill | Invocation | What it does |
|---|
| Make PR | /flow-next:make-pr | Render a cognitive-aid PR body - R-ID coverage table, critical changes, decision context. |
| Resolve PR | /flow-next:resolve-pr | Resolve PR review feedback - fetch threads, triage, dispatch resolver agents, reply + resolve. |
| Spec Completion Review | /flow-next:spec-completion-review | Verify the combined implementation of all tasks satisfies the spec requirements. |
| Skill | Invocation | What it does |
|---|
| Pilot | /flow-next:pilot | The build loop - one ready spec, one pipeline stage per tick, driven by your host’s /loop or /goal. |
| Land | /flow-next:land | The ship loop - babysits the build loop’s draft PRs through CI, review convergence, merge, and release. |
| Ralph Init | /flow-next:ralph-init | Scaffold the hardened Ralph harness - fresh session per iteration, hook-enforced guardrails. |
| Skill | Invocation | What it does |
|---|
| 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. |
| Skill | Invocation | What it does |
|---|
| Setup | /flow-next:setup | Optional local install of flowctl plus CLAUDE.md / AGENTS.md instructions. |
| Prime | /flow-next:prime | Opinionated agent-readiness assessment - verdict first, ranked next-actions. |
| Audit | /flow-next:audit | Review .flow/memory/ against the current codebase - Keep / Update / Consolidate / Replace / Delete / Harden per entry. |
| 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 | /flow-next:map | Semantic feature index of the repo (wraps clawpatch) - opt-in convenience consumed by scouts. |
| Memory Migrate | /flow-next:memory-migrate | Lift legacy flat memory files into the categorized YAML schema. |
| Skill | Invocation | What it does |
|---|
| 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 | /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 | dispatched on demand | Manage git worktrees for parallel feature work, isolated review, and clean workspaces. |
| Export Context | dispatched on demand | Export a review prompt for external LLMs (ChatGPT Pro, Claude web, Gemini). |
| Tasks & Inventory | conversational | ”Show me my tasks” - conversational access to specs and tasks in .flow/. |
| Drive | dispatched by QA | Surface-aware UI automation - picks the best available driver per surface, degrading gracefully. |
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.
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, which every skill calls for state, receipts, and validation.