# Agency Client Interview

> Client discovery interview framework for AI Agency projects covering business objectives, audience analysis, brand context gathering, and structured question flows that adapt to user patterns over time.

- Skill: `modu-ai/agency-client-interview` (Agent Skill)
- Install (CLI): `npx skillmds@latest add modu-ai/agency-client-interview`
- Raw SKILL.md: https://api.skillmd.com/api/skills/modu-ai/agency-client-interview/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- License: Apache-2.0
- Author: modu-ai (https://skillmd.com/u/modu-ai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/modu-ai/agency-client-interview

---


# Agency Client Interview Skill

Governs the client discovery process for AI Agency projects. Provides structured question flows, progressive disclosure of interview depth, and context file generation for `.agency/context/`.

---

## Static Zone

### Identity

**Purpose**: Define interview question frameworks, context gathering strategies, and structured output formats for populating `.agency/context/` files during project onboarding.

**Input Contract**:
- User request (natural language description of desired project)
- Existing `.agency/context/` files (may be empty on first run)

**Output Contract**:
- Populated `.agency/context/` files:
  - `brand-voice.md` — tone, style, language preferences
  - `target-audience.md` — customer personas, pain points
  - `visual-identity.md` — colors, fonts, imagery preferences
  - `tech-preferences.md` — framework, hosting, integrations
  - `quality-standards.md` — performance targets, accessibility level

**Owner**: `.agency/context/target-audience.md`

### Core Principles

> Derived from Brand Context. Never auto-modified. Manual editing only.

1. Empathetic questioning — understand the WHY before the WHAT
2. Progressive disclosure — start broad, drill down based on answers
3. Business-first — always connect technical decisions to business outcomes
4. No assumptions — ask, don't guess (especially for brand voice and audience)
5. Respect user's time — skip questions already answered in context files

### Default Interview Flow

**Phase 1: Business Context (3 questions)**
1. What is the primary business objective for this project?
2. Who is your target customer? (age, role, pain points)
3. What does success look like? (specific KPIs if possible)

**Phase 2: Brand Identity (3 questions)**
4. How would you describe your brand voice? (3-5 adjectives)
5. Are there reference sites or brands you admire?
6. Any design preferences or constraints? (colors, style, existing brand guidelines)

**Phase 3: Technical Scope (2 questions)**
7. What pages/sections do you need?
8. Any technical requirements? (framework, hosting, integrations)

**Phase 4: Quality Expectations (1 question)**
9. What matters most to you? (speed, design quality, mobile experience, SEO)

### Adaptive Behavior

- If `.agency/context/` files already have content, skip covered questions
- If user has completed 5+ projects, reduce to 3 key questions only
- Learn which questions users skip or answer briefly → reduce priority

---

## Dynamic Zone

> Interview questions, order, and depth evolve via user feedback.

### Rules

(No rules yet. Rules will be added as the system learns from user feedback.)

### Anti-Patterns

(No anti-patterns yet.)

### Heuristics

(No heuristics yet.)

---

## Evolution Log

- v1.0.0: Initial creation (Static Zone with default interview flow, empty Dynamic Zone)