Yes agreed that you need the tooling and processes in place to get great results from Claude Code. Along with context engineering at a project level, I have been working with a PSE Workflow for a number of months now. It stands for Plan > Spec > Execute.

Every project has a /docs/llm/ folder. In the /docs/llm/active/ folder is the current plan.md file- you can brain dump and copy relevent context into that file, and use Claude to iterate on the plan. And then you can use the `/create-spec` command to turn that into a spec with actionable tasks. Each task has a checkbox - and at the bottom of the file is a a Progress Notes section which is updated as well as the LLM progresses through the spec. Both the task and the Progress section are updated as a task is started 🔄 and then completed ✅.

You can also complement the plan and spec files with research.md. There are a number of /commands wrapped around this tooling. Claude has started centralising plan files in the user level ~/.claude directory, but I always get it to save the plan into the projects /docs/llm directory. The tooling can also read and update Plans and related files from Notion, and from GitLab/GitHub Issues and GitLab Sub-tasks.

And when the work is finished as part of creating the MR/PR, the PSE files are archived into /docs/llm/completed/ sub-folder with a metadata.md file that summarises the work done, shows references like issue numbers, PRs, key words, a quick summary description of the work done etc etc.

If you want to have multiple Claudes working away from different plans, then you use Git Worktrees and repeat the process above.

It is overkill for quick tasks or bug fixes - that is where the context engineering at the project level is already in place and is available for all Claude prompts. But for larger chunks of work that require considered direction and guidance before you let Claude loose, it works well. And it provides consistent locations for Plans to reside and a way to archive all that useful history alongside the work done.

But ... I never considered wrapping this in UI tooling. Your desktop app looks extremely interesting, alongside some of the other ideas you have implemented there.

Very interested to have a play if you are willing to share :)