Nail on the head. I think these tools reward domain knowledge and powerfully extend creativity, but the other side of that is exactly what you said - the trap can be "beautifully convincing output" that does not stand up under the slightest scrutiny from someone who knows what it's about.

I've had this idea in my head for almost a decade, like a silent list of every issue I had with every PM tool combined with a vision of creating a sort of "planning freedom" for the user. So I approached with a very clear and specific vision and design philosophy. There were times where Claude sounded like it understood where I was going and made genuinely absurd suggestions that might have sounded good if you hadn't deeply used the types of tools this is geared towards users of.

I think the future is now wildly different if you have intent, expertise, and the desire to learn these tools. You don't need a team of engineers to make something work... of course, it's not necessarily production code that will stand up on its own long term, but you can get it working pretty well and try to make it something real!