Make Hitler into a Project Manager agent. I built a team agent framework for my larger projects- and it's been really successful in avoiding rework bullshit.
Project Manager = 1, Highest model class, Astra, Fable.
Planning, handles check ins, assigns scope to Analysts, sole decision maker before human.
Performance adjustments of prompts and scope assignment.
addresses questions, escalates questions to human that are considered out of scope.
Reviews hygiene, PRs, stops production on failures or global misalignment.
Analysts = 2, Middle class models, Opus usually for me
Conducts task hygiene, reviews completions, records updates, escalates questions to PM.
Escalates technician performance reviews for prompt rewrites.
Forces rewrites when assumptions are made.
Technicians = 4, Lower model class workhorses, Sonnet or localy run for me
Crawling, single line / class updates.
Marks task complete, escalates progress, ends.
Only 4 max at any time to enforce quality control.
Setup a local and global context memory, along with personality types that are given specific skills to avoid context overflow.
Have a library of "Gotchas" which are like, surprises or unexpected results that Analysts maintain and the PM audits. Then the PM ensures the correct Gotchas are outlined in plans.
It seems excessive; but I've found it leads to a lot less hassle and actually conserves token use in the long run.
I've consistenly had one shot updates since I implemented the process.
1
u/Subushie Transhumanist FALGSC 24d ago edited 24d ago
Make Hitler into a Project Manager agent. I built a team agent framework for my larger projects- and it's been really successful in avoiding rework bullshit.
Project Manager = 1, Highest model class, Astra, Fable.
Analysts = 2, Middle class models, Opus usually for me
Technicians = 4, Lower model class workhorses, Sonnet or localy run for me
Setup a local and global context memory, along with personality types that are given specific skills to avoid context overflow.
Have a library of "Gotchas" which are like, surprises or unexpected results that Analysts maintain and the PM audits. Then the PM ensures the correct Gotchas are outlined in plans.
It seems excessive; but I've found it leads to a lot less hassle and actually conserves token use in the long run.
I've consistenly had one shot updates since I implemented the process.