Earlier quoted context omitted.
Or you can have a conversation with an agent to build up a requirements/plan spec, asking it to analyse existing code patterns. When it seems like the agent has a good understanding of what needs to be done and how. Ask it to implement, keeping changes as a local spike. Ask the agent questions about all the other teams' code, reaching out to them for questions it can't answer or clarification. With agent capabilities…
I have no idea what a “spike” is, but this seems like a good way to build software when there are no consequences to getting it wrong. What happens if this “spike” violates someone’s patent or puts the company at legal/regulatory risk? What if it leaks users’ personal information? What if it introduces a vulnerability that my 13 year old can exploit? What if it crashes 2 million of your users’ devices because it didn…
And yes you should completely grok what you're finally committing, making sure it's fully tested. What it enables is lots of fast experimentation before settling on your final change.