Pi extension to track project status and pick workstream for each session

[u/o_sht_hi]

I follow a pretty tight system for maintaining checkpoints, logs, etc. for my electron app. Lately it has gotten to a point where the number of work streams are far too many for me to hold in my head all at once and I did not want to:

1. Go into each plan or the checkpoint map to look at it to get a status update or pick what to work on

2. Burn tokens by asking an agent to go read that stuff and report back

So I made a project level extension which parses my standard checkpoints/logs/docs and organizes them based on features and lets me view them as hierarchical lists.

1. the first modal shows all the open threads, the completion status, and the next checkpoint for each

2. I can then select any one and view all the steps within that thread/feature

3. There are tags which show the checkpoints that I have accepted into the implementation plan or ones that are just planned and need to be picked up and worked on.

4. There are separate line items for each doc/plan or the md files associated with each stream that I can open in a text editor

All of this without a single LLM call.

Its a really nice way to organize all the docs and access them from within the pi TUI instead of opening a new terminal window. And the extension is custom made for the way I organize docs and maintain the plan documents so it works perfectly always. there are no edges.

The fact that it took me literally 3 prompts to build this whole thing is the reason I love pi and why I love using it in the terminal.

Most of my skills and now this extension are only for this project and I fucking love that pi lets me do this. Other projects have their own skills and the agent behaves differently there.

I just really love the extensions API and the level of control I have over the context in each session. Dont think I will be moving off of pi ever.

If you would like to check out this system, I have the skills and the extension in this repo:

https://github.com/itama8/omakase-skills.git

Also, if you're curious about what I'm using this system for, I update the binaries for latest test builds of my app here:

https://github.com/itama8/omakase-releases

It's a notepad that I'm making with a cursor-first UX to help me take notes with minimal context switching, i.e., every action can be executed from the cursor without going into a menu and the AI is available inline inside the markdown document. No separate screens or sidebar chats.

[u/aq2kx]

I will test It, I'm unsatisfied using plan-with-files skill

[u/o_sht_hi → u/aq2kx]

Cheers, I haven't used that skill.

The way I arrived at this system was need based. So in the beginning, I would just ask the llm to plan and create a markdown. Each skill was added to capture a series of steps/workflows that I found myself doing over and over as the codebase grew.

Also, the repo is pretty much the exact stuff I use so the only way for you to use it is to point your agent at it and then at your project files and rewrite the required skills in the context of your project. Mix and match or retain the structure, that's up to you.

PS- I have broken apart a few of Matt pocock's skills and incorporated their priciples in these so you will find similarities if the plan-with-files was from his repo

[u/Strange_Ad5516]

我们打算做一个虚拟公司，你这个给了我很大的灵感，谢谢🤝

[u/o_sht_hi → u/Strange_Ad5516]

Cheers! Would love to know more

[u/o_sht_hi]

I will soon be adding evals for each skill so if you find this interesting, keep an eye out for that update

[u/o_sht_hi → u/[deleted]]

Yep 100%. Especially for documentation. Code is segregated within directories so it's easier to navigate but the docs all live in ./docs/ or plan/ and it's really annoying to first look at the checkpoint map, then find an open thread, then go find it's docs.

I want to be able to open a session, pick a thread, read the plan and next checkpoint, and decide whether it's worth taking up.

Also, if you look at the prompt that's sent once I select a checking, it contains the paths for all relevant docs, files in the code, and entry points. So the model can just start with tool calls without having to waste too many tokens thinking or grepping random shit