I've been reading our own codebase to write the specs, not the other way round. Dashboard through left-nav, seven markdown files, each one describing what the screen is today and what it should be — every proposed improvement flagged so a dev can scope it without guessing what's new.
Turns out AI is genuinely good at the archaeology: crawl the code, tell me every nav item, every route, every existing state. That frees me to do the part I'm actually for — deciding what's wrong with it. It's a nice inversion. The machine reconstructs the present, I argue for the future.