# Documentation Document everything - decisions, milestones, feature requests, change requests, etc. ### Product Backlog Write user stories. Think about the feature from the user's perspective, draw out the actions to be performed and write them down. Involve the customer in making decisions related to the actions, workflow, copy, and wireframes. ### Change Requests If you're working on a turn-key project keep a track of all change requests. Each change request needs to be raised in writing and should be documented. ### Meetings After each meeting with the customer write down the minutes and track the decisions taken. ### Release Notes Prepare release notes for each build and share these with the customer. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://playbook.wednesday.is/project-management-playbook/our-approach/stakeholder-management/documentation.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.