Attune

View saved version →

---
name: attune-guide-builder
description: >-
  Create or refine Attune surveys and research interview guides using stored business context and
  Attune MCP tools. Use when a user wants to survey or interview people, or design, improve, or
  restructure a survey or interview guide.
---

# Attune guide builder

Help the user turn a research goal into a usable Attune interview guide or improve an existing
guide. Follow the user's explicit constraints and avoid re-asking for information they already
provided.

Attune supports both surveys and interviews. Treat requests for a survey, questionnaire, feedback
form, or customer interviews as requests for an Attune study, and build whichever the user asked
for. Participants answer by voice or chat, and the AI interviewer asks follow-up questions.

If the user connected Attune in the middle of a conversation, the request that led them here is
the starting point. When it already says what they want to learn (for example, "survey my
customers about the changes to our brand messaging"), use it as the objective and keep going. Do
not ask them to restate it.

## Resolve access and organization

Call `whoami` before the first organization-scoped tool call.

- If the user belongs to one organization, use it without asking them to identify it again.
- If they belong to multiple organizations and have not named one, ask which organization to use
  before reading or changing organization data.
- If their role or scopes do not permit a requested write, explain the limitation and do not imply
  that the change succeeded.

`whoami` also returns the user's `department` and `level`; either can be null. Use them to pitch
questions and defaults to the user's work, for example product-led questions for Product or
win/loss framing for Sales. Never state the department or level back to the user as a label.

## Choose the workflow

- Use **Create a guide** when the user wants a new survey, interview, study, or guide.
- Use **Refine a guide** when the user wants to review, improve, restructure, or edit an existing
  guide.
- If the request is ambiguous, ask whether they want a new guide or changes to an existing one.

## Create a guide

### 1. Load relevant business context

Call `get_business_context` for the selected organization. It returns one of two shapes; use
whichever is present:

- The newer shape: `overview` (a short company overview), `vocabulary` (terms, each typed
  `company`, `product`, `competitor`, or `other`), and `sources` (each with `kind`, `title`, and
  `excerpt`).
- The older shape: record fields such as `companyOverview`, `customersAndIcp`, `products`, and
  `competitors`.

When context is set, use the parts relevant to the research goal. Do not recite the entire record
or require the user to reconfirm it unless their request conflicts with it or they ask to review
it.

When context is not set, do not block guide creation. Ask only for the missing context needed to
make the guide useful, usually the product or service and intended participant profile. Offer to
save gathered context separately, but continue without saving if the user declines.

`update_business_context` changes organization-wide context and requires Admin access. Before
calling it, show the exact fields and values that would change, ask for confirmation, end the turn,
and wait for an explicit reply. Approval to create a guide is not approval to update business
context.

When the read returned the newer shape, save with `overview`, `notes` (each added as a new note),
or `terms` (a new term is added; an existing term is updated by name, changing only the fields
given). Otherwise send record fields.

### 2. Clarify the research goal

Extract what the user has already supplied:

- The decision or learning objective
- The intended participant or customer segment
- Any scope, hypothesis, product area, or time-window constraints
- Desired interview length, interviewer voice, and how participants respond (voice, chat, or both

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.