That same thing applies to the employees at your company. And you should be talking to it like it's a real employee, with the power to critique and improve your process and designs.
It can simulate a decent project or product manager, a requirements analyst, a test planner, a junior implementer, debugger, automation engineer, etc
If you can't make your engineering pipeline nicer with those kinds of roles, I think you would either struggle to direct a team of those same people IRL, or you're just not being candid and effective enough with your prompting. Read papers on promoting ideas like reflection, critique, tool use, etc. Really treat it like a valuable team member, and it will boost your product requirements, write great tests right out the gate, and many other things you will WISH you could get your human colleagues to do! And all for a tiny fraction of the cost of human specialists!
How do you know? Well that requires verification, which is probably more costly than doing the legwork yourself in the first place.
That applies to all LLM generated output. It is worthless until the reasoning is validated. Which is costly.