interview-capture

Scope (§13.1)

• User audio only. Do not capture or transcribe the employer’s side without appropriate consent and product scope—that remains out of scope.
• Opt-in: Run this skill only when the user explicitly asks to capture/log from audio or runs /career-navigator:interview-capture.
• Employer policy warning (once): Some employers prohibit any recording of interviews. Before the first capture session, show the warning from spec §13.1 and require acknowledgment. Persist to {user_dir}/CareerNavigator/interview-capture-settings.json:

{
  "employer_warning_acknowledged": true,
  "acknowledged_at": "YYYY-MM-DD",
  "user_opted_in": true
}

If employer_warning_acknowledged is already true, do not repeat the full warning—one line reminder max.

• Retention / jurisdiction: Use profile.md location for GDPR/CCPA framing per spec. If unclear, ask once which retention stance applies and store under interview-capture-settings.json as retention_note.

Workflow

1. Resolve {user_dir} and gate

Application data uses the split layout defined in references/tracker-schema.md — read it before any read or write.

Require CareerNavigator/profile.md and tracker.json. If missing, send user to /career-navigator:launch.

2. Opt-in and warning

• If interview-capture-settings.json does not exist or employer_warning_acknowledged is false: print the employer policy warning; on user acknowledgment, write the settings file.
• If user has not opted in to capture for this session, confirm before processing audio.

3. Match application

Identify application_id (or company + role) for the interview being logged. Match it against tracker.json → applications[] on id, falling back to each row's previous_ids. Hold onto the matched row's detail_file, contacts_file, and application label — the writes in step 5 need all three. If unknown, ask before writing tracker updates.