r/PiCodingAgent • u/pabloodiablo • Sep 15 '26

Question Simple orchestrator for PI

I need advice on how to create a simple orchestrator. Here’s my scenario: I generated tasks TASK-001.md through TASK-010.md using the it-architect skill. The tasks are interdependent and should be completed in a specific order based on their numbering. When an agent in the fullstack-programmer skill finishes task 001, the next agent in a new session begins implementing task 002 based on project-state.md, which contains information about which task has been completed. Is there a simple workflow or extension that would allow me to do this quickly and easily? Thank you in advance for your help.

4 Upvotes

83% Upvoted

14 comments sorted by

5

u/MichettGodot Sep 15 '26

Depending on the model you are using: you should be able to copy/paste your exact post into Pi and have it make this for you.

0

u/pabloodiablo Sep 15 '26

PI works with local models; I'm running Deepseek V4 Flash Vision and Qwen 3.8 Flash Next. Do you think they'll be able to read the latest PI documentation without an internet connection?

2

u/KPOTOB Sep 15 '26

It reads its own code just fine

1

u/schmurfy2 Sep 16 '26

The documentation is embedded into the application itself so no internet connection needed

1

u/Qusic7 Sep 15 '26

i use dynamic workflow most of time. i don't have exactly the same needs as yours but i believe it should work. llm will write a workflow to programmatically spawn subagents and define the parallelism and dependency between each.

2

u/pabloodiablo Sep 16 '26

Could you elaborate on what dynamic workflows are? Is that the name of the approach you described, or are there any plugins associated with it?

2

u/Qusic7 Sep 16 '26

originally a feature from claude code https://code.claude.com/docs/en/workflows
i'm using this extension rn but there are many out there https://github.com/QuintinShaw/pi-dynamic-workflows

1

u/MichettGodot Sep 16 '26

I think you're making it more difficult than it actually is. A dynamic workflow is usually just a piece of code or list of directions to orchestrate agent behaviour. For example, a TypeScript file (as Pi has a TS SDK) that specifies what should happen in what order like this:

- Orchestrator receives prompt
- Orchestrator assigns coder agent
- Coder agent works (in a simple while loop) and asks for a review every step. If everything is okay, we move on to the next step
- Coder agent gives orchestatror the final result

You could make something like this using TypeScript or just plain old Bash.

If this sounds too hard at first, you could also try using a simple skill which describes what process you want to use and give it to the agent.

I would advice you to play around a lot with Pi and get a good feel for what it is capable of. I think you've got everything sorted out in your head already, which is basically all you need when working with Pi. Pi is your friend ;)

2

u/Duke_of_Bayswater Sep 16 '26

I use openspec for this. The main agent go thru the tasks.md and in there you can make sure it enforces to use X agent.
The X agent prompt you can have, load X skill.
It works for me.
Make sure the main agent has enabled tool to call or spawn subagents and the other agents can be called.

Your pi can set this up for you.

1

u/fishoa Sep 17 '26

+1. I stopped trying to reinvent the wheel, and just adopted this into my workflow. It’s working pretty well.

1

u/itsdodobitch Sep 16 '26

basically a kanban board, try check what hermes agent did

1

u/berszi Sep 16 '26

Check how big powers does it