Agent Flow

Deep code-audit recipe: discover files in a target → review each (LLM, cached) → partition by component → executive digest with hotspots and recurring patterns. A layer-3 recipe over /agentflow:pipe (the 6-stage pipeline and caching are detailed in the body). USE when the user asks to "review / audit / find bugs across" a folder, repo, or glob and wants a persisted, structured report — and the target is large enough (≥ ~10 files) that per-file parallelism plus a digest beats reading inline. DON'T use for a few named files (read them inline), exploratory questions ("what does this do?"), or generic per-item work that isn't a code review (→ /agentflow:foreach). Not a `/`-menu command — it's the shipped `workflows/audit/` recipe: reach it by asking ("audit src for bugs"), or run it directly with `/agentflow:run-workflow workflows/audit/WORKFLOW.md`.

Workspace dashboard: lists every active framework run across all primitives, highlights blockers (stuck items, exhausted auto-continue caps), shows cumulative cost, and suggests the next action. The natural command to run after re-opening Claude Code in a workspace with in-flight runs, or whenever the user wants a one-shot overview of "what's going on". USE this skill when: - the user has just (re)opened the workspace and wants to know what is in flight; - the user says "what's going on", "show me everything", "any active runs", "where are we", "any pipelines running"; - the user wants a one-shot health check + suggested next action. DON'T use this to inspect a specific run in depth (use `/agentflow:inspect show <id>` or `tree <id>`), or to modify state (board is read-only). Explicit: `/agentflow:board` or `/agentflow:board --json`.

Run a **repeatable checklist / to-do list** from a markdown file of `- [ ]` items — execute the open items, tick them `[x]`, and write the file back. Re-running resumes only the still-open items, so the file IS the durable, repeatable state. USE for a generic user to-do that should be runnable again and again: "run my TODO.md", "esegui la checklist", "go through CHECKLIST.md", "do the open items in release-steps.md". Each `- [ ]` line is itself the instruction for that item (optionally refined by --prompt). This is thin sugar over /agentflow:foreach with `--checkbox`: same engine, same durability and cross-turn resume, friendlier defaults. For "apply one operation to a JSON list / folder / glob" use /agentflow:foreach directly; to first GENERATE the list use /agentflow:enumerate; for one combined output use /agentflow:reduce.

Author a reusable workflow-file by composing the Agent Flow primitives (enumerate, foreach, group, reduce, iterate) and bash/json stages into a declarative JSON `WorkflowSpec`, then validate it — ready to run with `/agentflow:run-workflow`. The builder counterpart to `/agentflow:run-workflow`. USE when the user wants to design / create / scaffold a multi-step workflow ("build a workflow that…", "create a pipeline for…", "compose a flow that does X then Y"), especially one to save and reuse. DO NOT use for a one-off single step — call the primitive directly. `create-workflow` is for durable, reusable multi-stage flows.

Do a multi-step DETERMINISTIC operation ONCE, ad-hoc — without saving a workflow file. You describe the outcome; `do` designs an inline pipeline (code/bash stages where possible, an LLM step only where real judgment is needed — the determinism boundary), names the run, runs it to completion, then offers to PROMOTE it to a reusable `workflows/<name>/WORKFLOW.md`. The fast path: throwaway now, keep it later if it earned its place. USE for "just do X", "i want to <multi-step thing>", a quick one-off pipeline over files/data, a transform you will probably run once. Trigger on a multi-step / deterministic-operation intent. DON'T use for: a single trivial action (just do it inline, no machinery); a reusable, parameterized workflow you will run repeatedly or share (→ /agentflow:create-workflow, which saves a folder); running an existing workflow file (→ /agentflow:run-workflow); applying one operation to each item of a list (→ /agentflow:foreach). `do` is the *ephemeral* sibling of create-workflow.

3 hooks across 3 events