$ cat ~/map/pi-workflow.md

pi-workflow

Named, repeatable multi-step workflows for Pi: research, code review, spec checks.

extensions✓ Oct 16

Facts

repository: github.com/AgwaB/pi-workflow ↗
GitHub Stars: ★ 364
Forks: 13
license: MIT
npm / mo: —
last push: Oct 14, 2026

install

pi install npm:@agwab/pi-workflow

## TL;DR

Workflow orchestration for pi — named, repeatable multi-step workflows (deep research, code review, spec conformance, impact review) run across pi subagent workers, with a read-only TUI board for inspecting every run.

## Key points

$Built on @agwab/pi-subagent: it coordinates pi subagent workers across workflow steps, passes results between them, and records each run so it can be inspected, stopped, or resumed.
$One install delivers the /workflow extension plus two bundled skills: workflow-guide (create, adapt, or review workflow definitions from validated scaffold bundles) and execution-router (decide whether a task needs a direct pass, a targeted verifier, or a workflow).
$Ask pi in natural language to use a workflow by name, or drive it deterministically with /workflow run <name> "task"; /workflow dynamic runs a one-off adaptive workflow that plans, fans out, and synthesizes without a saved definition.
$Stage patterns: single (one prompt to one subagent), foreach (fan out over a JSON array from an upstream control artifact), reduce (fan-in synthesis), loop (bounded repetition), dag (nested graph container), and dynamic (trusted controller code creates tasks with ctx.agent()).
$Four bundled workflows — deep-research, deep-review, spec-review, and impact-review — serve as runnable defaults and authoring examples, each rendering an audited final-report.md; workflows may also declare named executionProfiles selected with /workflow run --profile <name>.
$The /workflow board is a read-only TUI to browse runs, drill into stages and tasks, and preview task output; an Active workflows widget below the editor tracks progress and survives session reload by rebuilding from .pi/workflows. Requires Node.js >=22.19.0 on macOS or Linux — native Windows is not supported, use WSL2.

## FAQ

Q How do I create my own workflow?

Use the bundled workflow-guide skill, for example /skill:workflow-guide create a workflow for weekly release readiness — it starts from validated scaffold bundles for common graph shapes and can save the result as a reusable project workflow.

Q Does it work on Windows?

Not natively. pi-workflow requires Node.js >=22.19.0 on macOS or Linux; the README directs Windows users to WSL2.

Q How do I update it?

pi update npm:@agwab/pi-workflow. After the initial pi install, reload pi so the /workflow extension and bundled skills load.

pi-workflow

## TL;DR

## Key points

## FAQ

## References

## Related entries

## Guides