The current GitHub workflow is very unflexible and error prone. Instead of the strict phases, Clayde should pick up anything that concerns it (and is unblocked by a whitelisted user) and decide for itself how to work on it.
In general:
- plans go in issue comments, clarifying questions are asked and answers reacted to in the same chain.
- work is done as soon as all needed information is gathered (which could be right away if issue is clear) until PR is ready, PR is assigned to owner.
- Reviews on PR are seen and addressed.
No more preliminary/thorogh plan hard split although clayde may still do that if it decides to. It should rather have a prompt that guides it toward a natural conversation in the issue comment chain.
The main loop still checks the GH API periodically to pick up work. However, instead of complicated state management, for each issue and PR there should just be the time of last access persisted so that anything newer can be identified. (Or some other much simplified way of preventing agent calls for unchanged items.)
The current GitHub workflow is very unflexible and error prone. Instead of the strict phases, Clayde should pick up anything that concerns it (and is unblocked by a whitelisted user) and decide for itself how to work on it.
In general:
No more preliminary/thorogh plan hard split although clayde may still do that if it decides to. It should rather have a prompt that guides it toward a natural conversation in the issue comment chain.
The main loop still checks the GH API periodically to pick up work. However, instead of complicated state management, for each issue and PR there should just be the time of last access persisted so that anything newer can be identified. (Or some other much simplified way of preventing agent calls for unchanged items.)