No followers and 1 star, so, I'm assuming that you mean that process is what people are merging on, not necessarily this particular repo?
There are some similarities between this and what we've built (as described in the article I posted). One thing I noticed is that this workflow is based largely on agent skills, which are guidance/advisory. Sometimes agents follow them. Sometimes they don't.
We prefer deterministic runners for the process overall. We've also found that passing instructions to agents in their initial task context just prior to spawning them makes them much more likely to adhere to those instructions.
Deterministic everywhere possible. Firmly bounded everywhere else. The design conformance contract should be frozen before starting code generation and the evaluator must exist independent of the build loop.
No followers and 1 star, so, I'm assuming that you mean that process is what people are merging on, not necessarily this particular repo?
There are some similarities between this and what we've built (as described in the article I posted). One thing I noticed is that this workflow is based largely on agent skills, which are guidance/advisory. Sometimes agents follow them. Sometimes they don't.
We prefer deterministic runners for the process overall. We've also found that passing instructions to agents in their initial task context just prior to spawning them makes them much more likely to adhere to those instructions.
Deterministic everywhere possible. Firmly bounded everywhere else. The design conformance contract should be frozen before starting code generation and the evaluator must exist independent of the build loop.
Brad