Frameworks solve some problems and add others. The simple test we use before reaching for one.
A thought to take with youStart with plain code. Add a framework when you need branching, pausing for approval or rolling back, not before.
The hidden cost of a framework
Agent frameworks make demos quick. They also add layers between you and what is actually happening, which makes problems slower to find. For a straight sequence of steps, a few well-named functions are easier to read, test and change.
The test we use
We reach for a graph-style framework when the work genuinely needs it: steps that loop or branch, work that must pause for a person and resume later, or the ability to roll back to an earlier point. If none of those apply, we keep it in plain code.
Either way, we keep the business rules outside the framework so they can be moved later.