workflows

List the reusable workflows authored in this workspace — every `workflows/<name>/` folder, with its format (WORKFLOW.md / workflow.json), stage count, declared params, and description (read from either format). The "what workflows do I have to run" catalog. Read-only, never mutates state. USE when the user asks "what workflows do I have", "list my workflows", "which flows can I run", "show available workflows", or before running one and they don't remember the name/params. To run one use `/agentflow:run-workflow <path>`; to author a new one use `/agentflow:create-workflow`.

インストールへ移動

リポジトリ: AleSaiani/agentflow
ソースの最終更新活動: 2026年5月26日 07:58
検出された SKILL.md の言語: 英語
スター: 5
フォーク: 0

インストール方法

デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。

npx skills add https://github.com/AleSaiani/agentflow --skill workflows

コマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。

ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。

ソースファイルを確認

インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。

SKILL.md

ソースの指示 · 読み取り専用プレビュー

検索に戻るインストールに戻る

foreach

Apply ONE operation to EVERY item of a list — the **map** (N→N). The operation is a prompt; items come from a JSON list, a markdown checklist, or another run's output. Runs in parallel subagents or inline in the main thread, with persistent state and cross-turn auto-continue. USE on any "do the same thing to each of these" intent — formal OR casual: "for each X…", "per ogni…", "go through these one by one", "do every item in TODO.md", "review each of these files", "handle all of them", a glob, a folder. Trigger on the INTENT, then judge by count (the count gate, Step 2.5): - 1–2 items → just do it inline, no machinery; - a borderline handful (~3–10) → ask whether to use the durable/parallel mechanism or handle inline; - genuinely many, or heavy/independent items → use foreach. DON'T use when the list must first be generated from a spec (→ /agentflow:enumerate, then foreach), or you need one combined output (→ /agentflow:reduce). For the prebuilt "review every file → digest", use /agentflow:audit. Explicit

2026-05-27

run-workflow

Run a declarative workflow-file end to end: init a `/agentflow:pipe` from a JSON `WorkflowSpec`, then drive it to completion — auto-running every bash/json/deterministic stage and dispatching agents only where genuinely needed. Use `--dry-run` to preview the resolved plan without executing anything. The one-command way to execute a reusable, versioned workflow. USE when the user points at a workflow file ("run this workflow", "run workflows/audit/WORKFLOW.md", "run my pipeline") or wants to run a saved `WorkflowSpec`. Workflows are normally self-contained folders (`workflows/<name>/WORKFLOW.md` + sibling scripts), but a bare `.json` path also works.

2026-05-27

audit

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

2026-05-26

このリポジトリのすべてを見る

name	workflows
description	List the reusable workflows authored in this workspace — every `workflows/<name>/` folder, with its format (WORKFLOW.md / workflow.json), stage count, declared params, and description (read from either format). The "what workflows do I have to run" catalog. Read-only, never mutates state. USE when the user asks "what workflows do I have", "list my workflows", "which flows can I run", "show available workflows", or before running one and they don't remember the name/params. To run one use `/agentflow:run-workflow <path>`; to author a new one use `/agentflow:create-workflow`.
allowed-tools	Bash, Read
argument-hint	["--json"]
disable-model-invocation	false

/agentflow:workflows

Make it visible: this is read-only; just run it and surface the list.

Lists every workflow under <workspace>/workflows/ — a folder with a WORKFLOW.md (human-authored) and/or a workflow.json (compiled spec), or a bare workflows/<name>.json.

node "${CLAUDE_PLUGIN_ROOT}/dist/inspect.js" workflows [--json]

For each: name, format, stage count, declared params, the path, and a one-line description — read from WORKFLOW.md or workflow.json alike. Use it to find the right workflow + its params, then run it:

/agentflow:run-workflow workflows/<name>/WORKFLOW.md --param <name>=<value> …

Related: /agentflow:create-workflow (author a new workflow), /agentflow:run-workflow (execute one), /agentflow:board (active runs).

workflows

ソース情報

インストール方法

ソースファイルを確認

このリポジトリの他の Skills

/agentflow:workflows

このリポジトリの他の Skills

/agentflow:workflows