# Things to ask Prompts that work well with the Entz connector, grouped by what you want done, with the tools the agent reaches for and a tip where one helps. These prompts work with any agent connected to Entz. The connector tells the agent to make a document only when you ask for one, so say "in Entz" or "an Entz document" when you want it written there. For a document the agent did not make, give it the link: choose **Copy link** from the document's menu and paste it into your prompt. A link with `?tab=` in it, as your browser's address bar shows while a tab is open, takes the agent straight to that tab. The agent is told to keep its chat replies short and put what it writes in the document; ask in the chat when you also want a summary there. The tools named below are described in [The eight tools](/docs/mcp/tools/). ## Start a document ```text Write a one-page launch plan for the new billing page in Entz: goals, owners, risks and a timeline. ``` The agent calls `create` with the title and one placeholder per section, and the document opens in your browser. It then calls `update` once per section, replacing each placeholder with its heading and text, in reading order. The connector's guide asks it to draw a plan's milestones as a Gantt chart, which Entz draws from Mermaid. It helps to name the sections you want and who will read the document. The agent may still change the outline as it writes when the material has a better shape. ```text Make an Entz tracker for our hiring: a row per open role with the hiring manager, a target date and a status of Open, Interviewing, Offer or Filled. ``` The agent writes a table with a date chip in each target date cell and a status dropdown in each status cell, the statuses you named as its options. People then change a status by picking from the chip, and a date by pressing it. ```text Draft our onboarding guide in Entz: an overview, then a tab each for Design, Engineering and Sales. ``` The agent makes the document and its tabs in one `create` call, each tab with its own outline, then fills them in reading order, the overview first. ## Work in a document you already have ```text Here is our spec: https://entz.app/doc/… Tighten the Overview and add a Rollout section after Scope. ``` The agent reads the outline, reads the blocks it needs in full, then calls `update`: quoted words for small changes, a guarded replace for a rewritten paragraph, and an insert at the end of the Scope section for the new one. The link must let the agent edit: under **Access…**, **Anyone with the link** on, with **Edit**. [Connect an agent](/docs/mcp/connect/#who-the-agent-is-in-entz) explains why. ```text Fix the typos in the Pricing section of https://entz.app/doc/… and change nothing else. ``` The agent searches or views the section and changes only the misspelt words, each quoted exactly, so nothing around them moves. ```text Tick off the release checklist items we finished: the module publish and the integration run. ``` The agent sets the two task items as checked. ```text What changed in the plan since you last looked? Update the summary to match. ``` The agent reads only what changed since its last read or write, then rewrites the summary. This works within one working session: after the connector restarts, or after the agent has left the document alone for 10 minutes, it starts again from the outline. ## Review and comment ```text Read https://entz.app/doc/… and comment where the argument is thin. Don't change the text. ``` The agent reads the document and calls `comments` with `add` for each point, hanging each thread on 3 to 6 words quoted from the text. The document itself does not change, and people answer in the threads. The agent needs at least **Comment** permission from the link. ## Answer comments ```text Go through the open comments on https://entz.app/doc/… and deal with them. ``` The agent lists the threads, then for each one: answers a question in its thread without editing; makes a requested change with `update` and replies with one sentence saying what changed; and, on a point nobody has settled, replies that it needs the owner's answer. The agent does not see new comments by itself: ask it to look. Say so if you want it to resolve the threads it has handled. ## Reorganise into tabs ```text Move the appendix of the plan into its own tab called Sources. ``` The agent adds a tab holding the appendix, then deletes the appendix from the main tab. The words are copied into new blocks, so comment threads on them stay behind: the agent cannot delete words that open threads hang on, so resolve those threads first or tell it that it may leave them detached. ```text Rename the Notes tab to "Working notes" and put it last. ``` The agent calls `tabs` with `rename` and then `move`. The tab strip in the app adds tabs; renaming, moving and removing them goes through an agent for now. The main tab is the document itself and cannot be removed. See [Tabs](/docs/tabs/). ## Tables, diagrams and formulas ```text Turn the vendor list into a table with the price per seat, the contract end date and a status. ``` The agent replaces the list with a table, the end dates as date chips and the status as a dropdown chip per row. ```text Shade the header row of the vendor table grey. ``` The agent sets the background of each header cell, naming the cells by their position in the table. ```text Draw the signup flow as a diagram, and chart weekly signups from the table under it. ``` The agent writes Mermaid code blocks, a flowchart and a bar or line chart, and Entz draws each as it lands. Anyone can change a diagram by editing its source, which shows over the picture while the caret is inside. The connector's guide asks the agent to title a picture with its finding, such as "Signups rose to 420 a week", rather than its topic. [Diagrams, math and code](/docs/diagrams/) lists what Entz draws. ```text Add the formula for compound growth under Assumptions. ``` The agent inserts a LaTeX block, which Entz sets as a formula. ## Export ```text Save the plan as Markdown in docs/plan.md. ``` The agent calls `export` for the main tab, then writes the file, if your client lets it write files, as coding agents do. `export` gives one tab at a time, as Markdown, HTML or plain text; placeholders the agent has not filled are left out. For Typst or an `.ent` file, export from the app ([Import and export](/docs/import-export/)). ## Out of reach The tools cannot list or search your library, delete a document, change who has access to one, add an image from your computer, or show versions from before the agent's session: for those, use the app, and **History…** for older versions ([History](/docs/history/)).