# Write it out

After looking at other tools and thinking about your user, putting what you've learned and what your goals are for your design into writing is important. A short summary will help you:

* cement what you've observed and learned
* remind yourself of the ultimate goal for the tool
* remind PIs, coworkers, etc of the ultimate goal for the tool
* guide development
* help you to define core features and the minimum viable product (MVP)

In addition to writing up a short summary, it can be surprisingly helpful to write up the most plausible actions/stories that someone would take while using your tool. This is called a user story and will help you make sure that you meet the needs of your most common use case.

{% embed url="<https://www.uxpin.com/studio/ux-design/how-to-write-a-painless-user-story-for-agile-ux-teams/>" %}


---

# 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://ucsc-xena.gitbook.io/ux-resource-for-ucsc-genomics-institute/before-starting/write-it-out.md?ask=<question>
```

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.