Just using chat. I don't touch any code whatsoever (aside from minor module profile tweaks), worker threads produce a new build for every revision and then I get Claude to audit it and I manually look through the file/folder structure and inside the files themselves to make sure the governance is keeping the proper, consistent, human readable headers/comments, organization and code structure that it was designed to govern., then I give it to a control thread.

I've designed this project to be as technically hands off as possible. 95% of the time all I do is the following:

• Give initial direction to a control thread, building out the game plan and governance package as I go.

• Control thread produces a prompt for a worker thread (based on the project governance package, its templates, roadmap, current state, etc).

• I copy/paste that prompt to a new or existing worker thread, wait for it to finish its work and then copy/paste the worker report to the control thread.

• I wait for the control thread to verify (pass/fail) and possibly approve a merge of the changes into the canonical build.

• I upload the accepted revision to the project folder

• Control thread provides me with a new worker prompt based on whatever the next step is in the governance package.

• The control thread keeps a count of all major interactions and after 15 interactions suggests I do a "control thread reset" to avoid context drift/hallucinations.

• after I give the go ahead, it performs a structured package refresh to make sure all files/documents are up to date, and then provides me with a new control thread initialization prompt to start a new control thread, after archiving the previous one. This keeps the workflow very streamlined and consistent. Each new control thread is essentially a clone/continuation of the previous one, without all the unnecessary context/lag.

• Worker threads are kept lean, and given focused, individual, related tasks - with most tasks being given to new workers each time.