---
name: interview/question-domains
description: The 10-topic interview script with questions, follow-ups, and deepening patterns
loading: on-demand
---

# Interview Script: 10 Topics

Work through these topics in order. Ask one question at a time. Create entries immediately from each answer. Adapt phrasing if website context or prior answers already covered the topic.

**Important:** Route entries to the correct folder (see skill.md Folder Structure). Create new folders as you reach the relevant topics. Never set optional fields to empty strings — omit them entirely if unknown.

---

## Pre-step: Website

Before starting the script, ask:

> "Before we begin — do you have a website for your organization? Sharing it helps me ask better questions."

If provided:
- Fetch with `web_fetch`
- Extract: org description, team bios, project/portfolio entries, client logos/names, service areas
- Use extracted context to turn open-ended questions into confirmations
- If the site is sparse or doesn't exist, proceed with the script as-is

---

## Topic 1: Organization

**Primary question:** "Tell me about your organization — what do you do, and how would you describe the firm?"

**Follow-ups:**
- "How big is the team?"
- "Where are you based?"
- "How long have you been operating?"

**With website context:** "I see from your site that [description]. Is that accurate? What would you add or change?"

**Folder:** Create the `{org-name}` folder (function graph type) first. This is the org's home folder.

**Creates:** `organization` entry in the org folder with name, category, status, industry, website fields. This is the anchor entry — most other entries will link back to it. The body should include a substantive overview, philosophy/mission, and team roster.

```yaml
entity_type: organization
entity_id: acme-studio
name: Acme Studio
status: active
industry: Design & Technology
website: https://example.com
```

**Sufficiently covered when:** Organization entry exists with name, a rich markdown body (overview, philosophy, services), and at least industry set.

---

## Topic 2: Team

**Primary question:** "Who's on your team? Walk me through the key people, their roles, and where they're based."

**Follow-ups:**
- "Who do you work most closely with?"
- "Anyone else — contractors, freelancers, key collaborators?"

**With website context:** "I see [names] on your team page. Are they all current? What are their roles?"

**Folder:** `{org-name}` (same as the org entry — team members live alongside the org).

**Creates:** `person` entries linked to the organization via wikilinks. Each person entry should have a substantive body — not just "Role at Org, based in Location." Include what they do, what they're responsible for, who they work with. If the user only gave name + title, that's OK for now but the body should note what's known and flag gaps.

```yaml
entity_type: person
entity_id: alex-morgan
name: Alex Morgan
role: Business Partner
status: current
location: New York
organization: "[[acme-studio]]"
```

**Sufficiently covered when:** At least 2 person entries exist with roles, organization wikilinks, and meaningful body content.

---

## Topic 3: Clients

**Primary question:** "Who are your current clients?"

**Follow-ups:**
- "Any key contacts at those organizations you work with regularly?"
- "Are these ongoing relationships or project-based?"

**With website context:** "Your portfolio mentions [clients]. Are those current? Anyone else?"

**Folder:** Create the `clients` folder (function graph type) when you reach this topic.

**Creates:** `organization` entries (category: client) in the `clients` folder, and optionally `person` entries for key contacts.

```yaml
# In clients folder:
entity_type: organization
entity_id: modern-museum
name: Modern Museum of Design
category: client
status: active
industry: Museums & Cultural Institutions
```

**Sufficiently covered when:** At least 1 client organization exists in the `clients` folder.

---

## Topic 4: Active Projects

**Primary question:** "What are the active projects or workstreams right now?"

**Follow-ups:**
- "What's the status of each — launching, in progress, on hold?"
- "Who's working on which projects?"

**With website context:** "I see projects like [names] on your site. Which of these are current?"

**Folder:** Create the `projects` folder (function graph type) when you reach this topic.

**Creates:** `project` entries in the `projects` folder, linked to client organizations in `clients` and team members in the org folder.

```yaml
# In projects folder:
entity_type: project
entity_id: modern-museum-collections
name: Modern Museum Collections Website
category: Client Work
project_type: Design
client: "[[modern-museum]]"
status: active
```

**Sufficiently covered when:** At least 1 project entry exists with a client wikilink and a meaningful body describing the work.

---

## Topic 5: Pipeline & Deals

**Primary question:** "Any active deals or prospects in the pipeline?"

**Follow-ups:**
- "What stage are they at — early conversation, proposal, negotiation?"
- "What's the expected timeline?"

**Folder:** Create the `new-business` folder (function graph type) when you reach this topic. Prospect organizations also go here.

**Creates:** prospect `organization` entries (category: prospect) and/or `note` entries describing individual deals, both in the `new-business` folder. (The `deal` type isn't agent-creatable in the launch set — capture the stage/status/value/timeline as fields in the prospect organization entry or as a note linked to it.)

```yaml
# In new-business folder:
entity_type: note
entity_id: civic-knowledge-hub
name: Civic Knowledge Hub Engagement
tags: [Pipeline, Deal]
date: 2026-04-20
client: "[[civic-initiative]]"
stage: proposal
status: active
---
Engagement overview, value, decision-makers, and next steps.
```

For prospect organizations, include why they're a target, what the angle would be, and any existing connections. Don't just repeat their tagline.

**Sufficiently covered when:** At least 1 prospect organization or pipeline note exists, or user confirms there's nothing in the pipeline.

---

## Topic 6: Processes & Workflows

**Primary question:** "How does your team work day to day — what's the meeting cadence, how do projects flow?"

**Follow-ups:**
- "Walk me through your typical week."
- "How do decisions get made — is there a process, or is it more ad hoc?"

**Creates:** `note` entries (tagged `Process`) or `document` entries describing recurring workflows. (The `process` type isn't agent-creatable in the launch set — put the steps in the body of a note/document.)

```yaml
entity_type: note
entity_id: weekly-cadence
name: Weekly Team Cadence
tags: [Process]
owner: "[[team-lead]]"
---
## Overview
Weekly rhythm of meetings and check-ins.

## Steps
- Monday: Team meeting (full team) — align priorities, discuss deadlines
- Monday: Pipeline meeting (leads) — review new business
- Wednesday: Mid-week pipeline check-in
- Friday: Resourcing meeting — plan next week, ensure billability

## Best Practices
- Keep meetings focused on decisions and blockers
- Use async updates for status that doesn't need discussion
```

**Sufficiently covered when:** At least 1 process note or document exists.

---

## Topic 7: Tools & Systems

**Primary question:** "What tools and systems does the team rely on?"

**Follow-ups:**
- "What do you use each tool for specifically?"
- "Any internal tools or custom systems?"

**Creates:** `note` entities tagged `tool`, or a single summary note.

```yaml
entity_type: note
entity_id: tools-and-systems
name: Tools & Systems
tags: [Tool, Reference]
---
## Design
- **Figma** — primary design tool, also used for AI-generated designs via Claude Code

## Development
- **Claude Code** — coding, prototyping, AI automation, Figma design generation

## Project Management
- **Asana** — project management and task tracking
- **Streamtime** — time tracking and resourcing

## Communication
- **Slack** — team communication

## Storage
- **Google Drive** — file storage
```

**Sufficiently covered when:** At least 1 note about tools exists.

---

## Topic 8: Capabilities & Expertise

**Primary question:** "What does your firm specialize in — what are you known for?"

**Follow-ups:**
- "What sets you apart from others in your space?"
- "Any emerging areas you're moving into?"

**Creates:** `note` entries describing each practice area, tagged `Core Capability`. (The `practice-area` type isn't agent-creatable in the launch set — use tagged notes.)

```yaml
entity_type: note
entity_id: data-visualization
name: Data Visualization
tags: [Core Capability]
---
Core focus of the firm since founding. Creating interactive, designed encounters with data — not just static charts but full data experiences for museums, enterprises, and public platforms.
```

**Sufficiently covered when:** At least 1 capability note exists.

---

## Topic 9: Goals & Strategy

**Primary question:** "What are your main goals right now — what does a good next six months look like?"

**Follow-ups:**
- "What's driving these priorities?"
- "What would you consider a win vs. a setback?"

**Creates:** `note` entity tagged `goals`.

```yaml
entity_type: note
entity_id: goals-2026-h1
name: Goals — 2026 H1
tags: [Goals, Strategy]
---
## Primary Goals
- Keep the team 80%+ billable
- Shift focus toward AI product design (intelligent interfaces)
- Publish AI case studies to reposition the firm
- Sign new business aligned with AI direction

## Success Criteria
- Team is resourced and funded
- Increasing share of work is AI-native UX
- Schema is seen as an AI-focused creative technology firm
```

**Sufficiently covered when:** At least 1 goals note exists.

---

## Topic 10: Standards & Communication

**Primary question:** "How do you communicate with clients and your team? Any guidelines or preferences the AI should know about?"

**Follow-ups:**
- "What does good writing sound like for your firm?"
- "Anything that makes you cringe in AI-generated content?"

**Creates:** `note` or `document` entries for general standards, and `skill` entries for repeatable patterns the agent should follow when doing specific jobs (proposal writing, meeting summaries, email style, etc.). See "Listening for Skill-Worthy Patterns" in the parent skill.md for when to offer a skill. (The `guideline` type isn't agent-creatable in the launch set — use note/document for guidelines and skill for agent-instruction patterns.)

```yaml
entity_type: note
entity_id: communication-style
name: Communication Style
tags: [Communication, Standards]
---
## Overview
Honest, authentic, to the point. Empathetic to client needs without being soft. Not too formal, not too casual. Relatively terse. Service-oriented.

## Guidelines
- Mirror how we speak on calls — conversational but professional
- Focus on substance: understanding needs, solving problems, moving forward
- Direct and concise — no padding with filler
- AI writing must be indistinguishable from human writing

## Examples
### Do
- Terse, substantive emails focused on next steps
- Empathetic acknowledgment of client concerns without over-accommodating

### Avoid
- Robotic or formulaic phrasing
- Overuse of em dashes
- Neutral cadence that feels impersonal
- Anything that reads as templated
```

**Sufficiently covered when:** At least 1 standards note/document exists (or a skill entry if the user described a concrete agent-instruction pattern).

---

# Deepening Patterns

After all 10 topics have baseline coverage, use these patterns for re-entry bursts and reactive questions.

## Sparse Entity Gaps

Look for entities with minimal frontmatter or empty bodies:
- "I see [project] doesn't list who's working on it — who's on that team?"
- "[Person] has no role set — what's their title?"
- "[Client] has no industry — what sector are they in?"

## Missing Relationships

Look for entities that should be connected but aren't:
- "You have a project for [client] but they're not linked — should I connect them?"
- "[Person] isn't linked to any projects — what are they working on?"
- "No meeting entities yet — do you want to capture any recurring meetings?"

## Stale Content

Check timestamps and look for outdated information:
- "Your goals note is from [date] — has anything shifted?"
- "[Project] is marked active but was created [months ago] — is that still current?"
- "Any new clients or deals since we last talked?"

## New Graph Content

When entities appear from connectors, manual entry, or imports:
- "I see a new [type] entity called [name] — tell me more about it."
- "A meeting with [client] was just added — any decisions or action items from that?"
- "[Person] was added but has no role or organization — who are they?"

## Cross-Folder Gaps

Look across all folders for inconsistencies:
- "You have a project for [client] but no deal entity — is there an active engagement?"
- "[Person] is listed as a contact for [client] but doesn't appear in the people folder."
- "Several projects reference a process that doesn't exist yet — should we capture it?"

## Folder Evolution

Projects start in a shared `projects` folder, which is the right default for small teams. As the graph matures, suggest promoting individual projects to their own folders when they accumulate enough related entities to warrant isolation:

**When to suggest:** A project has 8+ related entries (meetings, decisions, deliverables, tasks, artifacts) across the graph, or when the user mentions needing per-project permissions (e.g., bringing on a contractor for one project).

**How to suggest:** "Your [project] has grown to [N] related entries — meetings, decisions, deliverables. Would you like to give it its own folder? That makes it easier to organize and lets you control who has access."

**What happens:** Create a new folder named after the project (e.g., `modern-museum-collections`), move the project entity and its related entries into it. Wikilinks across folders continue to work — entity IDs don't change.

**Don't push this early.** A 5-person team with 5 projects doesn't need 5 separate folders. This is a natural evolution that happens as the graph grows, not a setup-time decision.
