This is essentially just setting up an MCP connection to your kanban provider and instructing the agent to plan out an epic. I did this this morning for some data modeling our team needed to do. For the most part it generated a good set of tickets, but there were some hallucinations due to ambiguity. Reviewing the already written out tickets was much better than writing them out myself.
But the standard that will hopefully take over in most mature shops is spec driven development where instead of a team reviewing code, they review a spec which is used to generate tasks and subsequently code to satisfy the spec. Then 2 kanban boards exist. One for writing and submitting specs and another for the agents themselves to implement the approved specs.
These chips are large by fab standards and even with state of the art processes we likely won't see any kind of integration on consumer tech any time soon, but I imagine they will absolutely see instant demand if they can deliver on what they laid out in the post.
> From my own experience, models are at the tipping point for being useful at prototypes in software
You must not have much experience using the new frontier models then. A lot of large tech companies are replacing their SDLC with agentic workflows. The tooling and frameworks are still ramping up, but the models have no problem producing production ready software given proper specifications.
But at one point the model is sufficiently large enough to accomplish any task a human could specify. For software development, I think we're pretty much at that point with the latest Anthropic/Google/OpenAI models. We have no idea where the direction of token pricing is going to go in the future, but the consensus seems to be that it will only get more expensive. If Taalas can offer the same functionality that we have with frontier models today at a 1/10 of the cost and 10x the speed then they're going to take over a large part of the market.
Except they're still not accepting any feedback around AGENTS.md as a standard. You need to explicitly symlink CLAUDE.md to AGENTS.md in a workspace in order to Claude to work like every other agent when it comes to loading context.
It doesn't prove anything. It provides context for why someone would make that statement. Can you prove that things that do not need to eat and drink to survive can suffer?
May be that Python 2 to Python 3 migration was holding it back but it is remarkable that it shows positive strides or was relatively stable even within that transition period.
https://www.tiobe.com/tiobe-index/python/
But the standard that will hopefully take over in most mature shops is spec driven development where instead of a team reviewing code, they review a spec which is used to generate tasks and subsequently code to satisfy the spec. Then 2 kanban boards exist. One for writing and submitting specs and another for the agents themselves to implement the approved specs.
reply