I recently used this approach to reinvigorate the development of an existing project that has flattened out. Writing out how stuff worked then gave indications of where we needed to improve our API and document our corner cases.

In the end the README didn't represent the status quo but instead became what we were aiming for. For the most part this succeeded, the main challenge I had was persuading my collaborator to actually review what i'd written.