> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/artifacts/quick-notes.md). # Quick Notes ### Overview Quick Notes capture lightweight context without creating a full Artifact file. They support fast capture of decisions, snippets, and follow-ups. ### Key Concepts * **Quick Note**: short, lightweight note stored in Transform * **Linking**: reference from a requirement, task, test, or Artifact * **Governance signal**: consistent decision formatting, such as `Decision:` ### How It’s Used Use Quick Notes during meetings and reviews. Use them to capture rationale that should remain searchable. ### Benefits * Faster capture than long-form Artifacts * Better continuity for handoffs * Cleaner governance through searchable context ### Setup Steps 1. Create a Quick Note. 2. Link the Quick Note to the related requirement or task. 3. Convert the content into a requirement or task description when scope requires it. ### Best Practices * Keep one decision per note when possible. * Use consistent patterns, such as `Decision:` and `Approved by:`. * Avoid storing long documents as Quick Notes. Use Artifacts instead. ### Summary Quick Notes are optimized for fast, searchable context capture. Related: * [Creating Quick Notes](/artifacts/creating-quick-notes.md) * [What Are Artifacts?](/artifacts/what-are-artifacts.md) --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.transform.ai/artifacts/quick-notes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.