How does your team deal with product documentation/user story mapping?

For context:

I arrived at a company in which we're developing a product without any documentation. There's a third-party platform we're supposed to replace, and a lot of info in boss' head but nothing written down. Before I got here there wasn't even a document stating what the general goal of our app is.

Dev team, especially backend, was having lots of issues with implementing a a feature and just the next sprint discovering business rules are something completely different from what they built. I took up the task to document the product somewhat, try to extract as much info from my boss as I can so that we get a document that reduces these sort of issues.

Problem is: I've never really done this. I'm a frontend dev with little experience in project management or designing a whole product. I got a pretty OK functional requirements document with user stories and many features described, but nobody really reads or consults it lol. The same backend devs that complained about having no docs aren't consulting the docs.

The times we did work on documenting together before building a feature, we caught some mistakes before starting to code (which was the whole goal of the doc, and tells me this process is actually valuable). I'd like to make this to happen more often.

Browsing the project management subreddit I saw many people stating devs just don't read functional requirements too often, and it's better to just deliver user stories and have the devs document the features as they develop. I'm imagining that a good workflow would be as follows:

1. Product people create user stories
2. Product people/designer create wireframes
3. Dev team documents how they plan to implement feature (designer is creating figma file at this stage, likely)
4. Dev team implements feature after documenting

Does this sound like something you've seen work well?

Bottom line is: I've never really worked at a company that had an organized process for taking an idea, documenting it, and turning the document into code. I want to know how people are doing this in an organized manner. I know I should have some sort of adaptable backlog that we can alter when needed (because agile). Any courses you recommend? Books I should read?

Tl;dr: How does your team take an idea for a product, turn it into documentation, and then turn it into code? Does this process work well? Recommend learning resources please.