> For the complete documentation index, see [llms.txt](https://docs.mozark.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mozark.ai/agent-workspace-documentation/common-workflows.md). # Common workflows Common ways teams use Author Agent, Cleaner Agent, and Planner Agent together. ## Common workflows Use these workflows to get consistent results from the agent workspace. ### Build a release test plan Use [Planner Agent](/agent-workspace-documentation/planner-agent/overview.md) to search one feature, flow, or release area at a time. Review the returned test cases, then add them to a new plan or an existing plan. Because search always runs inside your current project, plan one project at a time. ### Clean up duplicate coverage Use [Cleaner Agent](/agent-workspace-documentation/cleaner-agent/overview.md) to reduce duplicate or overlapping test cases. For large repositories, start with one journey at a time. Review each result group carefully. Merge useful details first, then delete only the cases that are truly redundant. ### Fill coverage gaps If [Planner Agent](/agent-workspace-documentation/planner-agent/overview.md) does not return enough relevant coverage, switch to [Author Agent](/agent-workspace-documentation/author-agent/overview.md) to generate new test cases. Review the generated cases, save the ones you want, then return to planning if needed. ### Resume earlier work Use **Past Sessions** to reopen earlier work in **Author Agent**, **Cleaner Agent**, or **Planner Agent**. Use **New Session** when you want to start a separate task with a clean conversation. ### Move between agents Each agent works independently. Results do not move automatically from one agent to another. If you switch drawers, rerun the search or restate the context for that agent. --- # 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://docs.mozark.ai/agent-workspace-documentation/common-workflows.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.