Agile vs waterfall workflows

[jakedee]

I've noticed that the workflow follows a mostly waterfall rather than agile path.
Planning is done up-front and there doesn't seem to be a fully-defined flow for how to change direction mid implementation, or updating the plan as you go.

Whilst spec-driven development naturally lends itself more to waterfall than agile, hopefully we can mostly agree that waterfall doesn't work well for projects over a certain size, or with more than one stakeholder.

Either way it'd be great to have more emphasis on updating the plan/direction/specs on the fly, as you would with the agile methodology.

[mikelittle]

I have successfully told Claude to update both the product description and specs to change things part way through a project.

When I first started I ignored the fluff about target audiences and all the "product for the public" stuff. But I was building an internal tool that really didn't need half that stuff. I just told it to remove features and descriptions from those files, and it stopped trying to plan and build things I didn't want.