In an Agile team, people value a working software over comprehensive documentation. As mentioned previously, it doesn't mean there should be no documentation in an Agile team. In fact, you need vision and scope documentation to guide you through the project, user stories to bring up the conversations of requirement discussions, wireframes and UI design works for the implementation, documents of business rules and system requirements to specify the constraints of the system, and technical design documents to help the team understand the logic of the system. These documents don't need to be comprehensive. They should only contain sufficient detail to accurately guide the team. For example, in the technical design documents, you don't need to write every detail regarding the logic, just the important parts. These documents only serve as guidance. For the actual logic, you keep them in the code, and, even better, write automation tests to verify those logics, because a working software brings actual value to the customer, not those comprehensive documents.