Built-in workflow patterns
pi-dynamic-workflows ships 5 curated, tested workflow patterns. Each is also a
slash command (/deep-research, /adversarial-review, /code-review,
/multi-perspective, /codebase-audit), but they are equally reachable from
the workflow tool directly: call it with name set to the pattern name
below and args matching its shape, instead of writing an equivalent script
from scratch. Prefer this over authoring a new script whenever the request
fits one of these shapes — the curated version is already reviewed and tested.
A project or user saved workflow of the same name always takes precedence
over a built-in of that name — on the slash command, too.
These 5 names are reachable only at the workflow tool's top-level name
input, not via the in-script await workflow(savedName, childArgs) helper —
that helper resolves saved workflows only. Calling workflow('deep-research')
from inside a script fails as an unknown saved workflow; use the top-level
name input instead.
Patterns
name |
When to reach for it |
args |
deep-research |
Research a question across the web with cross-checked sources |
{ question: string, angles?: number, minSupport?: number } — angles (default 4) is the number of distinct search queries; minSupport (default 2) is the minimum distinct sources required for a claim to survive cross-checking |
adversarial-review |
Investigate a task/claim, then cross-check each finding with skeptical reviewers |
{ task: string, reviewers?: number, threshold?: number } |
code-review |
Multi-angle review of a diff (correctness, reuse, simplification, efficiency, altitude) |
{ diff: string, diffSource?: string } — get diff yourself first (e.g. git diff, gh pr diff <n>); this path does not fetch it for you |
multi-perspective |
Analyze a topic from several independent perspectives in parallel, then synthesize |
{ topic: string, perspectives?: string[] } — omit or give fewer than 2 to use the default set (technical, product, security, user experience, maintainability) |
codebase-audit |
Run parallel checks against a codebase scope, then cross-validate and report |
{ scope: string, checks: string[] } |
Example
{ "name": "deep-research", "args": { "question": "What are the tradeoffs of X vs Y?" } }
This is a workflow tool call, not a script — omit script entirely. The run
starts in the background exactly like the slash-command form; background,
maxAgents, concurrency, agentRetries, agentTimeoutMs, and tokenBudget
all still apply.
Writing a new workflow instead
If the request doesn't fit one of these 5 shapes, author a script with
script as usual — see the workflow-authoring skill.
1---2name: workflow-patterns3description: Argument shapes for the 5 built-in workflow patterns — deep-research, adversarial-review, code-review, multi-perspective, codebase-audit — runnable via the `workflow` tool's `name` input, without slash-command syntax. Use for requests like "research X", "fact-check/adversarially review this", "review this diff/PR", "analyze from multiple perspectives", or "audit the codebase for Y". Not for authoring a new workflow script — see workflow-authoring.4---56# Built-in workflow patterns78pi-dynamic-workflows ships 5 curated, tested workflow patterns. Each is also a9slash command (`/deep-research`, `/adversarial-review`, `/code-review`,10`/multi-perspective`, `/codebase-audit`), but they are equally reachable from11the `workflow` tool directly: call it with `name` set to the pattern name12below and `args` matching its shape, instead of writing an equivalent script13from scratch. Prefer this over authoring a new script whenever the request14fits one of these shapes — the curated version is already reviewed and tested.1516A project or user saved workflow of the same name always takes precedence17over a built-in of that name — on the slash command, too.1819These 5 names are reachable only at the `workflow` tool's top-level `name`20input, not via the in-script `await workflow(savedName, childArgs)` helper —21that helper resolves saved workflows only. Calling `workflow('deep-research')`22from inside a script fails as an unknown saved workflow; use the top-level23`name` input instead.2425## Patterns2627| `name` | When to reach for it | `args` |28| --- | --- | --- |29| `deep-research` | Research a question across the web with cross-checked sources | `{ question: string, angles?: number, minSupport?: number }` — `angles` (default 4) is the number of distinct search queries; `minSupport` (default 2) is the minimum distinct sources required for a claim to survive cross-checking |30| `adversarial-review` | Investigate a task/claim, then cross-check each finding with skeptical reviewers | `{ task: string, reviewers?: number, threshold?: number }` |31| `code-review` | Multi-angle review of a diff (correctness, reuse, simplification, efficiency, altitude) | `{ diff: string, diffSource?: string }` — get `diff` yourself first (e.g. `git diff`, `gh pr diff <n>`); this path does not fetch it for you |32| `multi-perspective` | Analyze a topic from several independent perspectives in parallel, then synthesize | `{ topic: string, perspectives?: string[] }` — omit or give fewer than 2 to use the default set (technical, product, security, user experience, maintainability) |33| `codebase-audit` | Run parallel checks against a codebase scope, then cross-validate and report | `{ scope: string, checks: string[] }` |3435## Example3637```json38{ "name": "deep-research", "args": { "question": "What are the tradeoffs of X vs Y?" } }39```4041This is a `workflow` tool call, not a script — omit `script` entirely. The run42starts in the background exactly like the slash-command form; `background`,43`maxAgents`, `concurrency`, `agentRetries`, `agentTimeoutMs`, and `tokenBudget`44all still apply.4546## Writing a new workflow instead4748If the request doesn't fit one of these 5 shapes, author a script with49`script` as usual — see the workflow-authoring skill.
zerx-lab