> For the complete documentation index, see [llms.txt](https://handbook.chaoss.community/community-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.chaoss.community/community-handbook/contributing/design/design-worklfow.md). # Design Workflow ## Our Process We follow a 4-query procedure to solve the design issues. Each question is a step toward the completion of the product. * **What do we want?** We need to initiate the requirement goals that define - what are we trying to achieve? How will it impact the CHAOSS community? * **What do we have?** We need to take into consideration the information we have - Do we have any set of design guidelines or information for the specific new goal that we are trying to achieve? * **How do we get what we want?** We need solid ideation in order to achieve any goal - Does the community agree to follow the new goal? Do we have any plans or processes to achieve the new design goal? * **What will happen when we do?** We need to understand the future impact for any specific design goal - Is the problem solved? Is this what you were looking forward to having? Will it create a better impact on the CHAOSS community? ## Ways of Achieving ![Design created by Jaskirat SIngh ](/files/-MHrYuUZNSHlnZkunU4e) \*\*\*\*๐Ÿ’ก **Plan** - You should be good to commence your design with planning as design inquires into the nature of a problem to conceive a framework for solving that problem. In general, planning is problem-solving, while the design is putting problems into actions. \*\*\*\*๐Ÿง **Research** - Make generative research together with the CHAOSS community members the requirements and assets that are needed. Check what impedes their productivity. \*\*\*\*โœ **Document** - Documentation stands out as one of the most important parts of any implementation design goal. After making fair research you should write down all the requirements you need with the available resources. \*\*\*\*๐Ÿ–Œ **Design** - High time! Once all the objectives and requirements are defined, draft your thoughts into the canvas that will help in solving the critical design problem that you are trying to achieve. \*\*\*\*๐Ÿงช **Test** - Testing is the stage in the design process that enables you to evaluate your design problem or service with real users and enables you to create more community-oriented design solutions. --- # 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://handbook.chaoss.community/community-handbook/contributing/design/design-worklfow.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.