The AI approach smells of waterfall and that has been deemed a bad approach to software projects. Not only because of the time cost (which some would argue it c

The AI approach smells of waterfall and that has been deemed a bad approach to software projects. Not only because of the time cost (which some would argue it can be reduced by agents), but because the only real product is the one in use. Every product solve some needs, and there are risks associated to the implementations of features. Trying to map every risk is not productive as the feature is not yet proven. Experience is needed to map the path ahead, but only if one has chosen to walk it. So writing specs is not hated. It’s just that they’re not that different than a SF novels, as their foundation are just hypotheses. If you have a mountain to climb, you do it step by step, not by tracing paths with maps drawn from reports narrating hearsay. So the most productive is to have an overall roadmap, plan the next months a bit according to your resources, and then fully focus on the next few tasks. Do periodic reviews to assess your progress.