conversation-intake

Conversation Intake — Structured Discovery

Purpose

Gather everything needed to design and build an app from nothing but a conversation. Where figma-intake discovers an existing design file, this skill discovers the user's intent: it interviews them (maximum of 7 questions), expands the answers into concrete design decisions via the conversation-designer agent, and outputs two machine-readable artifacts that the rest of the pipeline consumes without re-asking questions:

• .claude/plans/build-spec.json with "source": "conversation" — same contract every other intake skill produces
• .claude/plans/design-brief.json — the new artifact that drives Figma design generation in Phase C1

When to Use

• Phase C0 of /build-from-conversation
• Any time a user describes an app they want built but has no Figma/Canva file, screenshot, or URL
• When you need a structured design brief from a free-form product description

Inputs

• Optional: Initial description from $ARGUMENTS (seed answers; skip any question it already answers)
• Optional: Existing project directory to integrate into
• Reads: .claude/pipeline.config.json → conversation.interview (maxQuestions, confirmBriefWithUser)

Process

Step 1: Auto-Discovery (No User Input)

Scan the local project exactly as the other intake skills do:

1. Detect framework via the renderer registry:
   - Run: node scripts/renderer-registry.js detect . --json
   - On { "renderer": "<name>", "language": "<lang>" }:
       set build-spec renderer = <name>
       set build-spec outputTarget = <language>  (react | vue | svelte | react-native)
   - On { "renderer": null }:
       no framework detected → ask the output-target question (Question 5)
   Do not hand-sniff config files or package.json deps; the registry owns detection.

2. Detect app type:
   - manifest.json with "manifest_version" → Chrome Extension
   - manifest.json with "start_url" or "display" → PWA
   - Otherwise → Web App

3. Scan existing components:
   - Glob: src/components/**/*.tsx, app/components/**/*.tsx
   - Build inventory: name, props interface, file path
   - (Only triggers Question 7 if matches exist)

4. Check package.json for UI libraries and state management
   (same list as figma-intake)

5. Check for existing design tokens:
   - tailwind.config.ts theme.extend, src/styles/tokens.css,
     design-tokens.lock.json (from prior runs)
   - Existing tokens become constraints for the design brief, not questions

6. Load pipeline config:
   - .claude/pipeline.config.json → conversation.interview.maxQuestions (default 7)
     and appTypes[detected] for E2E strategy defaults