On point 1, it depends, and I think it is a UX issue. There might be a little bit of friction in nailing things down, but the coding part is 100% solved. On po

On point 1, it depends, and I think it is a UX issue. There might be a little bit of friction in nailing things down, but the coding part is 100% solved. On point 2, yes, again, there is a bit of friction. I would divide this into two cases based on what I have seen. Let’s say you don’t know coding and you are building a product for a decent number of users. Most people who don’t know coding get things wrong. I have seen that. But I have also observed that if they had asked better questions, much better questions, they would have gotten most things right. The other case is when you are dealing with a large enterprise. That is a different game altogether, but not everyone faces that kind of problem. Point 3 is completely solved. Most companies have integrated agents into the development cycle itself. If something goes wrong, you review it and merge it. The only bottleneck is when it is connected to external factors. Point 4: an environment with proper `SKILLS.md` and `AGENTS.md` files writes better code than most senior engineers . Trust me, I am not even lying here.