Every spec-driven dev tool I've researched assumes an engineer writes the spec at the keyboard, as they're about to build. But that feels too late - the intent & delivery processes behind the work mean it likely got hashed out some time earlier in a doc / ticket / meeting, written into Confluence and/or Jira, losing a bit of fidelity each time, so what the engineer writes in the spec is really a copy of a copy. And where I work the non-engineers can't even get into GitHub, so a spec living next to the code isn't accessible to the product folks and designers who were part of deciding what to build. Is spec-at-build-time an actual decision, or just where everyone ends up because that's where the code lives? Has anyone got a setup working where the spec's written earlier?

I work at a big tech company and want to spearhead adopting spec-driven development - but the toolkit doesn't match how I believe software gets made, by a whole product team. Feels like the industry took the easy route and built a closed admin layer with only the LLM in mind.