Workflow optimizations
Highlight text on any card (body, plan, or an event) to anchor a comment, or leave a whole-task comment here. Mention @claude to summon a reply.
No comments yet.
If you have many seeds to run in parallel, each on one GPU - create one multi GPU pod, not many single GPU pods (this is just cleaner)
Can/should we use agent teams
Should we be using different kinds/levels of abstraction of critics at each stage in parallel -> search the web for how people do this
Add a weekly code cleanup:
- Just a normal refactor and consolidating things together Add a weekly workflow improvement:
- Looks at transcripts of past week, identifies optimizations that could be made
- Plans to make them
Currently I need to approve so that Claude can write to .claude/plans/issue-x.md. This is bad because I want the entire adversarial planner loop to run and only then I approve. Is there any way to fix this?
Can Happy Coder change the chat name to be more informative?
Clean results should give more context so that it is understandable even for someone who is not up to date with the project
At every stage if something is genuinely not clear, it should stop and ask the user for clarification But or else -> after the plan, everything should run smoothly until the final clean result is generated, but there should be a status/column for a clean result generated by Claude vs approved by me
The pod(s) used shoudl be PAUSED until I approve the final clean result -> then they should be deleted