A proper PM should be moving towards owning design and marketing pieces - not production of software. Software is a means to package an experience captured by the design and communicated via marketing. It's that simple.
Most PMs don't match this description. So I understand the frustration's of engineers who have had to work with PMs.
A well constructed BRD is a very large chunk of the context needed for more successful use of an LLM. You're welcome to disagree, but I've found increasingly that the work artifacts from PMs are becoming even more essential to the actual development.
If you understand the design and user experience end to end and can express that effectively in writing, that's...your agent context. Why do a context hand-off to another human, or at least why remain as silo'd as we have historically been?
A proper PM should be moving towards owning design and marketing pieces - not production of software. Software is a means to package an experience captured by the design and communicated via marketing. It's that simple.
Most PMs don't match this description. So I understand the frustration's of engineers who have had to work with PMs.