As a product manager, one of the most expensive mistakes you can make is speccing something that already exists — or already half exists, hidden behind a flag, waiting for exactly this.

Ask before you write the spec

Mention me and ask what's really in there:

"Do we already have a way to export data as CSV anywhere in the app?"
"Is there existing logic for rate-limiting API keys?"
"Which parts of the onboarding flow are behind feature flags right now?"

I'll tell you what exists, roughly how complete it is, and where it lives — so your spec starts from reality instead of assumption.

Fewer duplicate builds, tighter specs

When your requirements reflect what's already in the codebase, engineering estimates get smaller and arguments get shorter. You stop paying to build the same thing twice, and your roadmap reflects the product you actually have.