![\"pi-dynamic-workflows](\"https://raw.githubusercontent.com/QuintinShaw/pi-dynamic-workflows/main/assets/readme/hero.png\")
\n\n \n
\n ![\"npm](\"https://img.shields.io/npm/v/@quintinshaw/pi-dynamic-workflows?color=cb3837&logo=npm\")
![\"MIT](\"https://img.shields.io/badge/license-MIT-blue\"){kind=icon}
![\"Built](\"https://img.shields.io/badge/for-Pi-7c3aed\"){kind=icon}
\n Documentation ·\n npm ·\n Pi package\n
\n\nTurn one request into a JavaScript orchestration script that fans work out across isolated subagents, routes each task to the right model, cross-checks the results, and returns one synthesized answer. Intermediate work stays in script variables instead of filling your chat context.\n\nBuilt for **codebase-wide audits, multi-perspective review, large refactors, and source-checked research**—the jobs that are too broad for one agent and one context window.\n\n\n\n## Start in 30 seconds\n\n```bash\npi install npm:@quintinshaw/pi-dynamic-workflows\n```\n\nRun `/reload` in Pi, then ask naturally:\n\n```text\nRun a workflow to audit every route under src/routes/ for missing auth checks.\n```\n\nPi writes and starts the workflow in the background. A live panel tracks progress while you keep working, and the final result is delivered back into the conversation automatically.\n\nKeyword triggering is on by default: use the bounded word **workflow** or **workflows** in an idle interactive editor submission to arm workflow mode — the assistant then handles a request by fanning it out across agents, but still answers plainly if you're only asking *about* workflows (the trigger authorizes the tool, it doesn't force it). The directive applies only to that request; the original user message stays unchanged. Print/JSON/RPC inputs and queued steering/follow-up inputs do not keyword-arm. Or run `/workflows run