What Routines Solve
Anyone who works with agents knows the feeling: many tasks require re-explaining the process every time—updating dependencies, running tests, tidying up the changelog—and saying it three times is worse than saving it once. Routines are exactly that: writing such processes as named routines, defining the steps, constraints, and acceptance criteria, then invoking them with a single sentence. The benefit isn't just saving typing: a solidified process means predictable behavior, and it can be shared among team members—effectively distilling the implicit knowledge scattered across each person's prompts into explicit assets in the repo.
The Engineering Trend of Agent Workflows
Put this post into the bigger trend: agent usage is moving from "chatting" to "configuring"—skills, hooks, routines, and every tool is growing similar mechanisms, all essentially wrapping deterministic scaffolding around a non-deterministic model. This follows the same logic as the evolution of shell scripts and CI pipelines back in the day—first manual repetition, then automated encapsulation. The next step is likely version control, testing, and marketplace distribution for routines. Whoever distills their team's workflow into assets like this earliest will reap an extra layer of dividend with every step up in agent capability.
via: Hacker News