Readme Driven Development
Noun · Hacker Culture
Definitions
A practice of writing the README or top-level documentation for a tool, library, or product before or during implementation so the intended interface and user experience become explicit early. It is used to force clarity about how something should be understood and adopted.
In plain English: Designing something by writing its user-facing documentation early.
Example: "The CLI got simpler once we tried readme driven development and saw how awkward the usage examples looked."