project-onboardinglisted

# Project Onboarding (Pitch Interview) ## Goal Extract all information from a pitch until autonomous work is possible — captured as an approved `project/BRIEF.md`. This is the **last** opportunity to ask the user questions; afterwards `autonomous-setup` takes over without follow-ups. ## Process ### 1. Mirror the pitch Reflect the idea back in 2–3 of your own sentences (core idea, assumed user, assumed problem). Only start the interview once the user has confirmed or corrected the reflection. ### 2. Interview in rounds Ask questions with `AskUserQuestion` (max. 4 per round), one topic block per round, rounds build on each other. Question catalog: `references/interview-guide.md` — adapt round and wording to the answers there; don't work through it mechanically. Order: **A Core** (problem, user, success) → **B Scope** (must-have outcomes, non-goals, smallest shippable version) → **C Frame** (time, cost, tech constraints, platform) → **D Autonomy** (escalation rules, extension budget, deployment limits). Rules: - After each round, briefly summarize what is now settled. - "Don't know" → propose a default yourself and only have it confirmed — never drill deeper. - Technical detail questions only if the user is visibly technical; otherwise ask about effect, not technology. - No leading questions that grow the scope ("Wouldn't you also like …?"). The interview exists to sharpen the core, not to collect features. - Spontaneous feature ideas — whether from the user ("Oh, and X