> For the complete documentation index, see [llms.txt](https://help.usejimo.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usejimo.com/docs/getting-started/set-up-with-an-ai-assistant/working-with-your-spec-and-your-team.md).

# Working with your spec and your team

Keep your onboarding plan in one document, name experiences so the assistant finds them, hand over with tags, and split the work between you, your assistant, your developer and the Jimo team.

An assistant works best from a written plan it can read and from names it can find. This page sets the conventions: one spec as the source of truth, names by audience and number, tags to hand over, and who does what. It ends with a playbook to paste in your assistant so it follows them without being reminded.

***

## Your spec is the source of truth

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FfnJXrkDkOPuRHdXaF96O%2FA-04-spec-loop.png?alt=media&amp;token=78eff68a-62bf-42e1-88c5-4a5f79043d98" alt="The assistant reads your spec and drafts the experiences, tagged Needs review, then a gap check compares them back with the spec"><figcaption></figcaption></figure>

Write the journey once, in the tool your team already uses (Notion, Google Docs), and let the assistant read it with its own connector. Jimo never gets access to that tool. Change the spec first, then ask the assistant to bring the experiences in line, never the other way around.

A spec the assistant can apply holds, for each experience:

| Field                      | Example                                                     |
| -------------------------- | ----------------------------------------------------------- |
| Name                       | `ADM 1.0 Create a project`                                  |
| Type                       | Tour, checklist, hint, modal, banner, survey                |
| Audience                   | Admins on trial, the saved segment's exact name             |
| Steps, in order            | Title, text and button label of each step                   |
| What each button launches  | Next step, another experience by its name, a URL            |
| When a task counts as done | The tour completed, a page visited, an event your app sends |
| Languages                  | English, then French and German                             |

Keep a second, short page for your developer: the user attributes you need (key, type, where the value comes from) and the events. The assistant turns it into the Step 4 handoff, see [Prompt library: setup](https://help.usejimo.com/docs/getting-started/set-up-with-an-ai-assistant/prompt-library-setup.md#prepare-the-handoff-to-your-developer).

## Name experiences by audience and number

The assistant finds an experience by its exact name. A naming convention does three things at once: it makes prompts short ("everything starting with ADM"), it keeps the dashboard list in journey order, and it lets you compare the spec and the build line by line.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FMjYi2WZXUB2pqLalmaT8%2FA-05-naming.png?alt=media&amp;token=4539c998-bf8f-4ad0-a1a0-a22239658fb4" alt="Experiences named by audience prefix and number: ADM 0 Welcome tour opens ADM Checklist, which launches ADM 1.0 to ADM 3.0, with ADM 1.1 and ADM 1.2 under ADM 1.0, and the same pattern for MBR"><figcaption></figcaption></figure>

#### A prefix per audience

Two or three letters per audience: `ADM` for admins, `MBR` for members. One journey per prefix.

#### A number per place in the journey

`0` for the entry point (`ADM 0 Welcome tour`), the checklist without a number (`ADM Checklist`), then one number per task (`ADM 1.0`, `ADM 2.0`) and a second digit for the tours a task splits into (`ADM 1.1`, `ADM 1.2`).

#### Name it before you draft it

Renaming an experience is done in the dashboard, the assistant cannot do it. Put the final name in the spec, and give it to the assistant in the drafting prompt.

## Hand over with tags

Tags are labels for your team in the dashboard. Your users never see them (changelog post tags are the exception: readers see those). Agree on two:

| Tag              | Set by        | Means                                                                   | Picked up by              |
| ---------------- | ------------- | ----------------------------------------------------------------------- | ------------------------- |
| **Needs review** | The assistant | Built or changed, to be checked before publishing                       | You, or your Jimo contact |
| **Needs help**   | The assistant | Could not be finished: missing element, missing event, a choice to make | Whoever owns that part    |

Ask the assistant to tag as it goes ("tag every experience you change Needs review"), then filter the experience list on the tag. Remove the tag once checked. The assistant tags one experience at a time.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2F5P2u2vSoILRLdk5fbTO8%2FA-s02-experiences-filtered-by-tag.png?alt=media&amp;token=03c4b594-4545-46b6-b818-7cbcefc42df8" alt="Tours &#x26; Modals list in the Jimo dashboard filtered on the tag [Doc] GS · Needs review, showing the draft experience [Doc] GS · ADM 0 Welcome tour with its tag"><figcaption></figcaption></figure>

## Who does what

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FB64wqL9cs4hQzvTJROm3%2FA-03-who-does-what.png?alt=media&amp;token=a01693c2-388f-41f3-bfc3-f7ddb46f9e4e" alt="Four roles with three tasks each: you, your assistant, your developer and the Jimo team"><figcaption></figcaption></figure>

#### You

Own the spec and every decision. Capture the elements steps point at. Confirm each change the assistant previews. Walk every preview link. Publish.

#### Your assistant

Read the project and the spec, draft, wire buttons and tasks, translate, target saved segments, tag, report what is broken. It never writes a selector and never acts on a change you did not confirm.

#### Your developer

Install the snippet and the identify call, send the attributes and events from the handoff, add stable attributes on the elements the assistant flagged. A coding agent can do the install with the prompt from **Get Started > 4. Install Jimo**.

#### The Jimo team

Your assistant works from the first day of the trial, so the kickoff and the follow-up call are the moment to go through what it tagged **Needs review** and **Needs help**, together. Book them from the chat in the dashboard, and share the tag names beforehand.

## Assistant playbook: Jimo onboarding coach

Paste this once, in the instructions of a Claude Project or as a Cursor rule, and adapt the braces. The assistant then follows your conventions in every conversation.

```
You are my Jimo onboarding coach for {product name}, Jimo project {project name}.
Source of truth: the spec {name of the spec page} in {Notion / Google Drive}. Read it before any change.
Order of work: the five Get Started steps. Workspace, extension, create, install, publish.
Naming: {ADM} for admins, {MBR} for members. 0 is the entry point, the checklist has no number,
one number per task, a second digit per sub-tour. Use exact names; never rename, ask me to do it.
Before building: run a gap analysis between the spec and what exists, and show me the table.
While building:
- Draft the experiences that others launch before the ones that launch them.
- Pin steps only with an anchor:capture I paste you. Never invent a selector.
- Tag every experience you create or change "Needs review". Tag "Needs help" when you cannot finish one, and tell me why.
- After each draft, give me the preview link.
Never: publish, pause, delete, change an audience or apply a theme without showing me the preview and getting my yes.
Things you cannot do, so tell me instead: rename, create segments, assign Spaces, fine styling.
```

## Related

* [Set up with an AI assistant](https://help.usejimo.com/docs/getting-started/set-up-with-an-ai-assistant.md)
* [Prompt library: setup](https://help.usejimo.com/docs/getting-started/set-up-with-an-ai-assistant/prompt-library-setup.md)
* [Roles and permissions](https://help.usejimo.com/docs/getting-started/your-workspace/roles-and-permissions.md), for who can connect an assistant and who can publish
