nauro-interviewlisted

# Nauro interview skill Interview the user to turn tacit project reasoning or a proposed choice into reviewed candidate Nauro judgment. This is an explicit, opt-in main-context workflow. Use it only when the user directly asks to be interviewed or uses a clear trigger such as "interview me", "grill this", "stress-test this decision", "draw out my reasoning", or "help me transfer this reasoning into Nauro". Do not activate it only because a plan is incomplete. The skill has two entry modes over one main-context, dependency-aware interview loop: - **Elicit mode** draws out unwritten rationale, assumptions, rejected paths, terminology, and unresolved questions. - **Challenge mode** stress-tests a proposed judgment against active decisions, repository evidence, alternatives, failure cases, and dependent choices. Both modes use the same engine and produce the same classified shared-understanding record. The workflow has no external skill or subagent dependency. ## Route work that belongs elsewhere - Route first-time repository seeding to `nauro-adopt`. - Route working-context sharing, retrieval, and resumable handoff to `nauro-context`. - Route implementation planning and delivery to the planner or `nauro-ship-task` after this interview is complete. Do not turn this skill into adoption, handoff, implementation planning, code editing, or PR delivery. ## Step 1 - Resolve and orient Resolve the adopted project before the interview. From a repository, run `nauro status` to co