Engineering Requirements Doc - ERD

Backlinks

a PRD-ERD hybrid

^ a Product Requirements Doc - PRD and Engineering Requirements Doc - ERD hybrid

see in context
implementation is a learning process

You learn stuff while implementing. You get much deeper into the problem. You don't just stick to the Engineering Requirements Doc - ERD, if you find a better way.

see in context
not every detail is described in an ERD

^ not every detail is described in an Engineering Requirements Doc - ERD

see in context
what is the 'spec' in spec-driven development?

I think that question gets at the heart of the matter. It's just not clear what specification actually is. So far, in my experience doing agentic coding, a reasonable specification has been, essentially, durable and persistent Engineering Requirements Doc - ERD-level artifacts that are decomposed into a documentation context graph. Or, more specifically the 'spec' part of a documentation context graph should be at a PRD and light ERD hybrid level

see in context