> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/ux-methods/discovery/project-brief.md). # Project Brief A project brief is a concise document that outlines the key details, objectives, and scope of a project. It provides an overview of the project's purpose, desired outcomes, and constraints. A project brief typically includes information such as project goals, deliverables, timeline, budget, and stakeholders. It serves as a reference point and communication tool for all parties involved, ensuring a shared understanding of the project's scope and requirements. The project brief acts as a foundation for project planning and execution, guiding decision-making, resource allocation, and project management activities. It helps stakeholders and team members stay aligned and focused on achieving the project's objectives. The project brief sets the stage for effective collaboration, enabling stakeholders to provide input and make informed decisions throughout the project lifecycle. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://www.designreference.xyz/ux-methods/discovery/project-brief.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.